More than four months after the release of Battlefield 4, the developers at DICE are still hard at work perfecting and polishing their biggest project to date. Although fans have seen plenty of patches over the last few months, more are expected in the weeks to come. Just today, a lengthy post went live on Battlelog which detailed many of the fixes that rolled out, as well as what improvements can be expected going forward.
Check out the full details below.
What we are Fixing or Investigating
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 ticket rate – 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 ticket rate at this moment, we are exploring the possibilities of raising the ticket rate 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.
Network Troubleshooting Icons
With the January 30-31 game updates, we’ve introduced two new icons to the Battlefield 4 HUD (head-up display). These were added to the game as a way for us, and the players, to more easily troubleshoot common network-related issues that may have negative effects on the multiplayer experience.
The first icon, seen at the top in the shape of a clock, indicates that your connection to the server is lagging. There can be several reasons for this. For example, it could mean that someone else is using your connection while you are playing, but it could also mean that there is a network problem that occurred somewhere between you and the server. The effect of such lag is that it will take a bit longer for you to see what is happening in the game world. If this icon is frequently blinking, you might want to try a different server or see if you can decrease the load on your Internet connection.
The second icon, at the bottom, shows four squares that indicate packet loss. When you see this icon, your connection to the server is experiencing lost packets, which means that information is failing to reach its destination, either when your game client sends it to the server or when the server sends the information to you. Please keep in mind that packets always get lost on the Internet and that you should not be alarmed if you’re seeing this icon blinking once or twice. If you have a large amount of packet loss and see the icon often, you will probably experience game “hiccups” sometimes – action will stop for a moment, then speed ahead to catch up.
What We Have Fixed
Kill Card Shows 0 Health
Kill card sometimes incorrectly displays 0 health, despite the enemy being alive. This could happen when a portion of damage dealt was rejected by the server, since the bullets that caused it were fired after the point of death for the firing player – the kill card would show the health as predicted by your game client, rather than the health confirmed by the server. An improvement that decreased the rate at which this happens went live for PC on Feb 13, and will be included in the next game update for all the platforms.
We have fixed instances of broken collision that made it impossible for players to shoot past broken objects, such as the collapsed chimney on Zavod 311.
Crosshair Disappearing, Resulting in Hit Markers Disappearing
In firefights, players on PC could experience their crosshair disappearing, resulting in hit markers also disappearing. This would happen when certain gadgets were deployed by other players. A fix for this is now live.
Hit Impact Sounds
Impact sounds did not match the number of bullet impacts, causing players to feel that they died too quickly. An improvement to this went live for PC on February 13, and will be included in the next update for all the other platforms. The cool down time for letting bullet hits trigger the sound has been decreased considerably, so players will now hear every bullet that hits them.
We have re-introduced the headshot icon to help players understand when they get killed by a headshot, something that usually results in an instant death. The headshot icon went live in the January 30-31 game update for all platforms.
We want to assure you that we are constantly investigating, or already in the process of updating, all these items and several more that you’ve had concerns with – and that we will continue to do so with your help. Please continue to send us your feedback, and thank you for your continued support.