Forum Discussion
I play for 5 minutes and get a crash. My case is waaaay worse. 🙂
The "Sound Loop Crash"
Platform(s): All
Status: Investigating
At least they're working on it, maybe there still is hope
source: http://battlelog.battlefield.com/bf4/forum/threadview/2955065670203355766/
- Anonymous12 years ago
Seriously guys, try setting the compatibility mode to "Run program as administrator". It worked for me and my friend. I haven't had a crash since then. I think this is the most common crash cause. 🙂
- 12 years ago
@showdown53: Thanks for the tip, but I still got crashes even when I "Run program as administrator"
Most of the time I play Operation Locker or the China Rising maps because they seem to crash less, but today I had a sound loop crash on Altai Range CQ Large.
- EA_Nils12 years ago
Community Admin
Update #24 (Dec 16) - R16 Server Update Notes
We will be rolling out a new server update throughout the day.- Fix for some of the more common server crashes
- Overall performance enhancements
- UCAV ammo replenish time was set from 20 to 90 seconds
- Round time limit intervals were added for the different server types
Update #25 (Dec 16) - PC Game Update Notes
We’ve rolled out a new PC game update and will continue to make improvements based on your feedback. The update includes fixes with the aim to increase the general stability of the game, and eliminates bugs that you may have experienced. It also includes an improvement to the so called “Netcode”.
UPDATE: We have noticed that players who have SLI enabled on their graphics card may experience graphical flickering. Also, we're looking into the issue where the revive bar would get stuck on-screen in some instances. Both of these have our attention, and we're investigating them.
- 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 serverNote: As always, you can find the latest info here: www.battlefield.com/bf4controlroom