DICE are addressing the “Netcode” Problems in Battlefield 4

The Netcode, or Network Code, is the part of Battlefield that deals with the complex management of communications when you’re playing a Multiplayer game. DICE never call it Netcode, but even they recognise that it’s the term being used by its user base.

Many of the problems with BF4 have come down to what’s believed by the users to be flaws in this Netcode. DICE have already made a number of changes in recent updates to address these but a number are still outstanding – however, DICE are aware of them and have now provided an update on their progress.

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

Tickrate

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.

Various Items

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.

In addition, they have also provided some information on a couple of in-game icons that were introduced some time ago.

Connection_HighLatency_64x64This first icon 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.

Connection_PacketLoss_64x64The second icon indicates 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.

Darkstorm40
About Darkstorm40

Relatively recent convert to Battlefield but now hooked. Not the best aim or sharpest reflexes but good team player.

Hates people complaining unnecessarily and believes you should always offer solutions – yes, I’m looking at all the Battlefield 4 haters.

General IT bod during the day and all-round geek at all other times.

Owner of bfmedic.com.

One response to DICE are addressing the “Netcode” Problems in Battlefield 4

  1. ToP ShoTTA said this on March 10, 2014

    With the last patch I was really happy with conquest, I’m really happy to see them addressing these issues and I hope they can continue to fix these major problems that have been ruining a truly great game.

Leave a Reply