Posted on March 3, 2014 AT 10:35am
DICE has outlined several fixes that will be coming in future updates that are all related to “netcode” issues.
“Fixing the commonly nicknamed “netcode issues” – problems ranging between faulty networking latency compensation and glitches in the gameplay simulation itself – is one of the top priorities for DICE,” the developer wrote. “We are working on fixing glitches in your immediate interactions with the game world: the way you move and shoot, the feedback when you’re hit, and the way other players’ actions are shown on your screen.”
Apparently most of the issues are connected to “latency compensation,” which makes sure that players move around naturally on your screen in multiplayer. Some of the known issues include rubber banding, a delay in the kill camera triggering, tickrate, damage registering, players dying from sprinting, and more.
A rundown of upcoming fixes and ongoing issues can be found below:
We have made several server optimizations that have decreased rubber banding for some players. To further address the issue, there are upcoming fixes for packet loss and a customize screen bug, both connected to the rubber banding issue. Furthermore, we will continue to collect data to pinpoint exactly when and why rubber banding is occurring.
Kill camera delay / Player death sync
On some occasions, the kill camera would trigger before the game client displayed the last portion of damage being dealt, giving players the impression that they died too early. There were also issues with blood effects, damage indicators, and the health bar in the HUD being out of sync. A fix for this will be included in the next game update.
Players have been asking whether the tickrate – how often the server will update the game world – in Battlefield 4 will be higher in the future. Though we haven’t got any immediate plans to increase the tickrate at this moment, we are exploring the possibilities of raising the tickrate on specific servers.
No registered damage
We are aware of the bug where players have been firing at their opponent and not doing damage. In the February 13 game update for PC, we added a piece of code that enables us to specifically track instances where this would occur. We are currently looking at when this issue is triggered, and what causes it. The data that we receive will help us to further improve the firefights in the future.
Instant death while sprinting
At certain occasions while walking or sprinting, a player could get catapulted at high speed which would cause death if any object was standing in the way. This was caused by a mathematical error in the character physics code, and we have a fix prepared for an upcoming patch.
In addition to these items, there are also fixes coming for issues with Levolution being out of sync, shots appearing to be fired in the wrong direction, and vehicles outside the infantry area not taking damage when fired at. Also, we have introduced new in-game icons that will help you, and us, to troubleshoot network related problems that could cause an inconsistent multiplayer experience.
The developer also went into some of the issues that it has already fixed, including kill cards showing zero health, broken collision detection, the crosshair disappearing, hit impact sounds missing, and the reintroduction of the headshot icon.
Today's Top 10 Stories
Top Partner Stories
Website Interface © 2012 EGM Digital Media, LLC.