Battlefield 4

By blank
in Gamers' Hangout

 Share

Recommended Posts

Grand Master

mattmatik

Posted
Posted

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. 

Grand Master

LOC Veteran

Posted
  • Veteran
Posted

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.

  • Anthony Tosie
  • Like 1
Mentor

Anthony Tosie Veteran

Posted
  • Veteran
Posted

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.

Grand Master

spaceelf

Posted
Posted

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.

Grand Master

mattmatik

Posted
Posted

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!

Mentor

Anthony Tosie Veteran

Posted
  • Veteran
Posted

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

Grand Master

HoochieMamma

Posted
Posted

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.

Grand Master

Boo Berry

Posted
Posted

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.
Grand Master

spaceelf

Posted
Posted

-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.

Veteran

Ficman

Posted
Posted

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

  • HoochieMamma
  • Like 1
Grand Master

ViperAFK

Posted
Posted

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 :/

Grand Master

ViperAFK

Posted
Posted

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.

Grand Master

spaceelf

Posted
Posted

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.

Grand Master

spaceelf

Posted
Posted

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.
 Share
Go to topic listing

  • Posts

    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By Slugsie · Posted

      The machines are starting to fight back any way they can.
    • Linux 7.1 arrives with an NTFS overhaul and major hardware performance boosts

      By Accuphase · Posted

      No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones

      By zikalify · Posted

      Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • Microsoft confirms Recycle Bin bug across all versions of Windows

      By snowy owl · Posted

      I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs

      By hellowalkman · Posted

      Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.

  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post

  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!