Recommended Posts

Viper/DL - are you signed up to the newsletter? Also make sure you have Origin installed too.

Anaron - I got the same email a few days ago. When I checked my EA account was a Origin account anyway. Not sure what's going on there... :/

(sorry for the brief reply I'm on my Desire)

Yep, all of the above actually.

I have been signed up for the newsletter, linked up Origin then installed the client both the first days they were announced, so just not sure what it is at this point.

It figures honestly, I have gotten into almost every other EA alpha/beta they have launched in the past 2 years, get into so many other ones on the PC, PSN, and Live, most of which I could care less, but the one I actually want to be a part of I am not getting into. At this point I am done trying. Hopefully I will eventually get the invite, if not for whatever reason it just was not meant to be.

Thanks for trying to help, I just am not getting into this one apparently.

Viper/DL - are you signed up to the newsletter? Also make sure you have Origin installed too.

Anaron - I got the same email a few days ago. When I checked my EA account was a Origin account anyway. Not sure what's going on there... :/

(sorry for the brief reply I'm on my Desire)

Yes, Signed up for news letter, I have an origin account (and orgin installed on my pc), and updated my veteran status

EDIT **** I GOT IN!

Apparently first time I signed up for news letter it didn't take. Signed up, got news letter confirmation, signed into alpha!

The first thing I did after reading about the alpha is log into my Battlefield veteran account here: http://veteran.battlefield.com/

The second thing I did was activate the email address associated with my EA account. I've had the account since 2009 and oddly enough, it wasn't activated so most of you should have already done this when making your account.

The third thing I did was sign up for the EA newsletter. This can be done by logging into your EA account and changing your contact options (see "Contact me about EA's products & news"). Make sure you receive a confirmation email for this because I didn't get one the first time I signed up. I signed up again and received a confirmation email shortly after.

Everyone with an alpha is dead to me!

:cry:

you can get it too just sign-up for the news letter you may have to press it a couple times for it to register check your e-mail adress for confirmation. make sure your vet status is up to date . go to the alpha site and sign up

I'm in finally as well. It sounds like everyone is. Now when I will get to check it out is a whole other story. Hope tomorrow night at some point.

I wish cry.gif I've been signed up for the newsletter as long as I can remember and still nothing.

I can't even play it long enough to judge it because it runs like trash. I was just playing the indoor portion of the map and I was getting FPS dips to around 30-40FPS, so I quit on the spot. Not to mention it looks horrible too.

System Specs:

Intel Core i5 2500K 3.3GHz

8GB Corsair XMS3 DDR3-1600

MSI GTX 560 Ti Twin Frozr 2 1GB

Turns out it installed the game on my SSD too, and load times are still pretty bad.

I know this is still an Alpha, but if I can't even run this game on low with a modern system, then all thoughts of me putting it through it's paces now can be forgotten. I'm praying the Beta is better than this.

I can't even play it long enough to judge it because it runs like trash. I was just playing the indoor portion of the map and I was getting FPS dips to around 30-40FPS, so I quit on the spot. Not to mention it looks horrible too.

System Specs:

Intel Core i5 2500K 3.3GHz

8GB Corsair XMS3 DDR3-1600

MSI GTX 560 Ti Twin Frozr 2 1GB

Turns out it installed the game on my SSD too, and load times are still pretty bad.

I know this is still an Alpha, but if I can't even run this game on low with a modern system, then all thoughts of me putting it through it's paces now can be forgotten. I'm praying the Beta is better than this.

My specs are worse (2.6ghz amd quad, 4gb ddr2, ati 6850)

runs fine, as good as bc2

Its alpha, as in not even beta yet. very early development. Bound to not run well for everyone.

And IMO while it obviously doesn't look as good as the fault line videos and other demos we've seen yet, it looks good. An overall improvement to bc2. Better lighting, better weapon textures, better animations.

My specs are worse (2.6ghz amd quad, 4gb ddr2, ati 6850)

runs fine, as good as bc2

Its alpha, as in not even beta yet. very early development. Bound to not run well for everyone.

And IMO while it obviously doesn't look as good as the fault line videos and other demos we've seen yet, it looks good. An overall improvement to bc2. Better lighting, better weapon textures, better animations.

I suppose it could be an unlucky combination of hardware. I just find it incredibly frustrating getting an alpha code to a game I've been dying to play since they announced it only to find out I can't even run it decently.

In my opinion even on high the game looks worse than BC2 maxed out in it's current state. Nothing looks better, aside from a handful of textures here and there (mostly the weapons and characters, some map textures). I still think BC2 is still one of the most polished looking games available at this point in time.

I'm going to assume it'll only getting better from the Beta onward, but I just fail to see the point in releasing something like an alpha when assumingly a more polished Beta is on the way a little over a month from now. This has done nothing but leave a bad taste in my mouth.

Apparently the nvidia beta drivers that are being released will support SLi, so maybe it is better I cannot play until tomorrow night anyway. Will see.

As a fellow BF junkie and Vet... I await your impressions.. ;)

I stopped keeping my rig updated for gaming years ago (still on a FX-55);

So the console version is my only hope. Being this game appears to have been catered to the console player, I'm sure I won't be missing anything (I loved playing Commander in the 2nd).

This topic is now closed to further replies.
  • Posts

    • Microsoft finally admits its default Windows 11 25H2, 24H2 action broke key legacy component by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. So far the company has acknowledged two known issues that have popped up after the release which include bugged-out Office apps as well as the Recycle Bin; though there could be more at play too. Speaking of bugs and issues, Microsoft seems to have finally acknowledged a problem that probably has been around for close to a year. That's because back in July of 2025 the company made a default change to the latest Windows 11 versions, wherein it switched to JScript9Legacy on Windows 11 24H2 and later releases. Hence following the release of version 25H2 in October 2025, JScript9Legacy also remained default-enabled. As a result there has been a compatibility issue ever since then. For those wondering, by switching to JScript9Legacy Microsoft intended to improve the security of modern Windows PCs by reducing vulnerabilities tied to legacy scripting like cross-site scripting (XSS), among others. XSS exploits can allow cyber-attackers to attach malicious code onto legitimate websites and use them to execute the code when a potential victim loads such a website. Hence the new JScript9Legacy engine enforced stricter execution policies and improved object handling, which should help mitigate such attacks. Microsoft today has published a new support article detailing the problem. Neowin spotted it while browsing. The company says that JScript global definitions and execution context may fail to persist across scripts, potentially breaking older dependent apps and web-based components that relied on this legacy behavior. In the article Microsoft has confirmed that the issue stems from its move away from the older jscript9.dll engine in favor of jscript9legacy.dll. As mentioned above, while the newer engine was designed to address vulnerabilities and strengthen security it also changes how JScript handles execution context. As a result functions and definitions loaded by one script could no longer remain available to subsequent scripts once execution ended. The company notes that some applications worked correctly on earlier Windows versions because the older JScript engine automatically retained global definitions and execution state between scripts. Under the newer model though that behavior is disabled by default causing certain legacy workloads and polyfill-dependent scripts to fail. Microsoft says it addressed the problem via the KB5077241 update though the fix had not been enabled automatically in the following updates. As such admins must explicitly turn on persistent JScript execution context using a Registry setting that the tech giant shared today. The configuration can be applied to individual processes or system-wide through the FEATURE_ENABLE_PERSISTENCE registry key. The steps have been outlined below: Run the following command to create the feature control registry key: reg add "HKLM\Software\Policies\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PERSISTENCE" Under this key, create a new DWORD (32-bit) value. Configure the value as follows: To enable persistence for specific processes only: Set the value to 1 for each target process name. To enable persistence for all processes: Add * as the key name and set its value to 1. You can find the official support article here on Microsoft's website.
    • The possibility that milk gathers back into a glass implies that gravity can be 'reversed'.
    • VidCoder 12.20 by Razvan Serea  VidCoder is a DVD/Blu-ray ripping and video transcoding application for Windows. It uses HandBrake as its encoding engine. Calling directly into the HandBrake library gives it a more rich UI than the official HandBrake Windows GUI. VidCoder can rip DVDs but does not defeat the CSS encryption found in most commercial DVDs. You’ll need the NET 8 Desktop Runtime. If you don’t have it, VidCoder will prompt you to download and install it. The Portable version is self-contained and does not require any .NET Runtime to be installed. You do not need to install HandBrake for VidCoder to work. Feature list: Multi-threaded MP4, MKV containers Completely integrated encoding pipeline: everything is in one process and no huge intermediate temporary files H.264, H.265, MPEG-4, MPEG-2, VP8, Theora video Hardware-accelerated encoding with AMD VCE, Nvidia NVENC and Intel QuickSync AAC, MP3, Vorbis, AC3, FLAC audio encoding and AAC/AC3/MP3/DTS/DTS-HD passthrough Target bitrate, size or quality for video 2-pass encoding Decomb, detelecine, deinterlace, rotate, reflect, chroma smooth, colorspace filters Powerful batch encoding with simultaneous encodes Customizable Pickers to automatically pick audio and subtitle tracks, destination, titles and more Instant source previews Creates small encoded preview clips Pause, resume encoding VidCoder 12.20 changes: Updated HandBrake core to 1.11.2. Download: VidCoder 12.20 | 47.0 MB (Open Source) Download: Portable VidCoder 12.19 | 89.3 MB Link: VidCoder Home Page | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Too soon, I'm still not over this death!
  • Recent Achievements

    • Week One Done
      Jordan Smith earned a badge
      Week One Done
    • Reacting Well
      BizSAR earned a badge
      Reacting Well
    • First Post
      AndreaB earned a badge
      First Post
    • Week One Done
      Huge Trailer earned a badge
      Week One Done
    • Week One Done
      Classifyskilleducation earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      593
    2. 2
      +Edouard
      185
    3. 3
      PsYcHoKiLLa
      77
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!