Recommended Posts

Yeah, have to agree, enjoying this waaaay more than BF3. Might be because I have some friends playing though and using voice chat in the squad is sooo nice. Finally able to take over some games using vehicles, too. 

 

One thing I've noticed is Battlelog is so finicky with updates, even to Chrome. Yesterday I couldn't get anything to load and decided to check for a Chrome update and lo-and-behold, a pending Chrome update was working. Restarted the browser and everything was good again. I'm assuming this is actually Flash-related? So, while I don't mind Battlelog, this could be leading to people not even getting into game. One of my friends had to move to Firefox even.

 

I don't take anything EA says as fact so I'm not believing their PR stunt; EA has been apologizing a lot lately. Hope I'm wrong though. 

This is all EA's fault. DICE has proven they can produce a good game

 

I don't know how long you've been playing DICE games. But they make good games, but they are usually quite buggy on release (and sometimes with patches, which have to be rolled back). I mean come on, 1942 was pretty solid when it came out (if I remember correctly) but BF2 was borked for alot of people. Same with Vietnam and 2142 etc etc etc. Not to mention the times they've put out patches in the past that had to be totally rolled back because of something horrible being introduced instead of fixed.

 

Sometimes I think DICE's Q/A branch just doesn't have enough people or they are (gasp) bad at finding big bugs. Now sure EA kinda rushed DICE with BF4 because of Ghosts, but that's no excuse at this point with their previous track record on PC releases. Which is poor to say the least for most people.

  • Like 1

I don't know how long you've been playing DICE games. But they make good games, but they are usually quite buggy on release (and sometimes with patches, which have to be rolled back). I mean come on, 1942 was pretty solid when it came out (if I remember correctly) but BF2 was borked for alot of people. Same with Vietnam and 2142 etc etc etc. Not to mention the times they've put out patches in the past that had to be totally rolled back because of something horrible being introduced instead of fixed.

 

Sometimes I think DICE's Q/A branch just doesn't have enough people or they are (gasp) bad at finding big bugs. Now sure EA kinda rushed DICE with BF4 because of Ghosts, but that's no excuse at this point with their previous track record on PC releases. Which is poor to say the least for most people.

Yup, pretty much every Battlefield game since 1942 has been fairly buggy upon release.

R15 Server Update Notes

-Various server side crash fixes, including the top seen crashes on R14

-Activated the reservedSlotsList.aggressiveJoin command that enables VIP players and server administrators directly joining full servers

-Client patch compatibility to make servers compatible with the Dec 09 client update

Dec 9 PC Game Update Notes

-Fixed one of the most frequently occurring client crashes

-Fixed broken collision on containers with open doors. The bug previously made grenades bounce back even though the doors were open.

-Fixed a bug in Defuse mode where defenders could win the round by killing all the attackers without disarming the bomb, if the bomb was disarmed in the previous round.

-Miscellaneous stability fixes further reducing the number of client crashes

-Fixed side gunner jitter when aiming in attack boats & transport helicopters

-Fixed some instances of frame rate drops when shooting at large Levolution objects after they have been destroyed (like the radar dish on Rogue Transmission)

-Fixed broken aiming for passengers on the China Rising dirt bike

-Fixed a bug where the sound when capturing a flag was not playing correctly

-Removed a bug that would double save during MP round transition and SP level transition. This fix will reduce the occurrence of corrupted save files.

http://battlelog.battlefield.com/bf4/forum/threadview/2955065670201033581/

Cool.

Good to see the updates. I did get dropped from a game tonight, although there is no way to know WHY (i.e. kicked, server crash, etc). But the sound fix when capturing a flag is most welcome.

 

I'm also starting to warm up to the China Rising maps. Hope Second Assault comes soon to PC, really want to go back to Gulf of Oman!

Whatever DICE did with the update has made it worse for me  :/ Terrible hit detection, constantly getting disconnected.

 

And unrelated to what they do, the increase in Xbox One consoles sold has made it so we get all the K/D junkies who never help the team. Lovely :p

I'll just leave this here

 

http://www.maximumpc.com/lawfirm_may_sue_ea_over_buggy_battlefield_4_rollout2013

 

Hopefully this comes into fruition as EA are useless. Barely touched the game since release, had 100x more enjoyment our of PayDay2.

DICE has screwed up SLI/CrossFire with the latest patch with flickering galore. Also the "netcode" fix totally screwed the game up. Worst. Patch. Ever. Oh, here's the changelog...

 

Dec 16 PC Game Update Notes 
-Fix for a crash that would cause the game to stall, resulting in a sound loop. This should eliminate most of the problems relating to this. 
-Fix for the SUAV (introduced in the China Rising expansion pack) not exploding when hitting enemy soldiers. While these indeed should be deadly, they were never designed for ?roadkilling? opponents. 
-Fixed one of the issues related to the so-called ?Netcode? (see below for details) 
-Fix for player tags not always showing when needed to, resulting in players shooting team members. 
-Fix for graphical flickering appearing on terrain. 
-Fixed the instance where players suddenly would transition into Spectator Mode while playing the Defuse game mode. 
-Fix for a Defuse bug where none of the teams would win a round by letting the timer run out.
-Fix for players getting stuck in the revive screen after being killed. 
-Fix for players getting stuck in the kill camera after being revived. 
-Fix for the game mode specific ribbons being counted twice in the multiplayer progression. 
-Made the NVidia 331.82 driver version mandatory for all players. 
-Disabled DirectX 11.1 on NVidia cards that have outdated drivers. 
-Fixed driver version not being properly detected on NVidia Optimus systems. 
-Fixed a minor crash that could occur when bringing up the scoreboard. 
-Fix for the issue where the game would get stuck in loading screen when players tried to join a Second Assault map without actually owning Second Assault. 
 
?Netcode? improvement 
We?ve addressed the so called ?Kill trading?. This refers to when two players fire at each other and, seemingly, both die at the same time. The time window where a bullet could cause damage from an already dead player is now calculated as intended, decreasing the timeframe when players with high latency could get a kill, even though they should be dead according to the server.

-Made the NVidia 331.82 driver version mandatory for all players.    Is REAL issue with some of us still running NVidia cards and Fermi chip sets

 

Patching continues to make this game worse than it was when it started

If your card doesn't work with newer drivers, that's something to take up with NV.  DICE can only deal with their game not working with older drivers.

If your card doesn't work with newer drivers, that's something to take up with NV.  DICE can only deal with their game not working with older drivers.

 

 

I disagree...  DICE should be working with NV to get a set of drivers that work

 

Making a known bad driver mandatory is not a good move, I have no other issues with any other games including BF3

  • Like 1

DICE needs a patch, to fix a patch, which was intended to fix a game half done, and obviously still in early beta mode. gotcha. 

 

 

EDIT, I spoke too soon :/: Some of the fixes in this patch do indeed introduce new issues. In particular the "texture" flickering fix didn't seem to do anything at all to get rid of the flickering on distant textures that most people get, and instead introduced tons of texture issues for SLI users :/

331.82

 

GREAT ! So if i upgrade and get computer lag problems again, I have to have an unusable computer or no BF4.

 

 

-Made the NVidia 331.82 driver version mandatory for all players.    Is REAL issue with some of us still running NVidia cards and Fermi chip sets

 

 

Patching continues to make this game worse than it was when it started

 

sounds like you should be complaining to nvidia about that issue ;)

 

I'm sure dice had reasons for blacklisting older drivers, they were probably causing game crashes or something.

sounds like you should be complaining to nvidia about that issue ;)

While there may not be a direct line, there are plenty of methods to get support. http://www.nvidia.com/page/support.html

 

You can also typically get ahold of the people that built your card fairly easily.

Don't know why I'm complaining when I'm downloading them at 100mbit, but why are the patches are so ****ing huge for this game?

Can't remember a patch bellow 800mb for this game :huh:

Multiple executables and level data for a huge game and the expansion...BF3 was worse near the end IIRC

This topic is now closed to further replies.
  • Posts

    • BrowserOS 0.46.0 by Razvan Serea BrowserOS is a free, open-source Chromium-based browser that runs AI agents natively, offering a smarter, more productive browsing experience. It supports Chrome extensions and integrates AI agents to automate tasks, fill forms, and streamline workflows. Your data stays on your computer: you can use your own API keys or run local models via Ollama, making it a privacy-first alternative to tools like Perplexity, Comet, or Dia. With built-in productivity tools and app integrations, BrowserOS boosts efficiency while keeping control firmly in your hands. Being Chromium-based, BrowserOS lets you effortlessly import your bookmarks, passwords, and Chrome extensions in just a few clicks. BrowserOS works with OpenAI GPT models, Anthropic Claude, Google Gemini, and local AI models via Ollama or LMStudio. You can use your own API keys and effortlessly switch between providers. BrowserOS Agent Your AI productivity assistant that organizes and manages your browsing effortlessly Quickly list, group, or close tabs Save and resume browsing sessions Search your history and organize bookmarks Switch instantly to the tab you need BrowserOS Navigator – Automate web tasks with ease Navigate websites and search automatically Interact with pages without manual effort Handle repetitive tasks in seconds What makes BrowserOS special Feels like home - same familiar interface as Google Chrome, works with all your extensions AI agents that run on YOUR browser, not in the cloud Privacy first - bring your own keys or use local models with Ollama. Your browsing history stays on your computer Open source and community driven - see exactly what's happening under the hood MCP store to one-click install popular MCPs and use them directly in the browser bar (coming soon) Built-in AI ad blocker that works across more scenarios! BrowserOS 0.46.0 changelog: Run Claude Code & Codex right in your browser — We've extended the agent harness to bring full coding agents into BrowserOS. Claude Code and Codex now come bundled and plug straight into the assistant, so you can drive your browser with the agent — and the subscription — you already use. A brand new experience — A redesigned new tab, a calmer composer, and a rebuilt command center for switching between agents. The whole assistant is cleaner, faster to reach, and easier to live in. New MCP tools — We rebuilt the browser tool surface from the ground up — a tighter, more reliable set of tools for agents to drive the browser. Plus one-click install of BrowserOS as an MCP server into the agents you already run, with automatic URL sync. Chromium 148 — Updated to the latest Chromium base with all recent upstream fixes and security patches. Streamlined — We've pulled back a few features that weren't getting much use — Skills, Soul, and Memory — so we can focus and ship better versions of them soon. Download: BrowserOS 0.46.0 | 181.0 MB (Open Source) Download: BrowserOS for macOS | 485.0 MB Links: BrowserOS Homepage | Github | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • 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'.
  • 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
      590
    2. 2
      +Edouard
      186
    3. 3
      PsYcHoKiLLa
      76
    4. 4
      Michael Scrip
      73
    5. 5
      Steven P.
      66
  • Tell a friend

    Love Neowin? Tell a friend!