DICE geeft update omtrent Battlefield 4 netcode

Nieuws

4 March 2014

Geschreven door rafbanaan

In een nieuwe blog op de Battlelog-website heeft ontwikkelaar DICE wat meer uitleg verschaft over welk problemen men nu aan het aanpakken is in Battlefield 4. Zo werkt men momenteel aan het bekende probleem dat samengevat wordt als de 'Netcode', met andere woorden de online problemen van het spel. Zo heeft men reeds enkele problemen opgelost die konden leiden tot 'rubber banding' en wist men de 'latency compensation' wat beter te maken, zodat je minder het gevoel krijgt dat je 'one hit kills' te verwerken krijgt. In de voorbije maanden heeft men ook de problemen opgelost met broken collision waar je niet door gebroken objecten kon schieten, Kill Cards die op 0 health stonden, Crosshairs die verdwenen met als gevolg dat ook de hit markers weg waren, de impactgeluiden die niet overeenkwamen met het aantal afgevuurde kogels en als laatste het headshoticoontje.

Hieronder vind je nu een overzicht terug van wat ze nog aangepakt werd onder de noemer 'Netcode'.

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.

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.

Bron battlelog.battlefield.com

» Reacties (0)