[YT]TCpdDfb6GIw[/YT]
A new video shows proof that the netcode issue could be on the client side as well as on the server side.
We’ve heard plenty of things about the Battlefield 4 netcode — mostly just how bad it is. The recent PC patch seems to have made some improvements to the netcode, but players are still reporting about various issues, such as lag, hitbox registration, and more. You can see a bunch of videos on the bad Battlefield 4 netcode here.
A new video might shed some light on the netcode issue, though. Done by YouTuber PixelTwitch, the video shows that some of the “netcode” problems might actually be on the client-side of things.
He booted up the Battlefield 4 test range, and did some experiments firing at the moving targets. The video clearly shows that there is some issue with the way hits are registered on the hitbox. This could mean that some of the netcode problems could be on the client-side, because, as far as we know, the BF4 test range is run locally.
When he fired directly at the moving target, he would miss, but if he fired shortly after the target, it would register as s hit. He tested the above video with “network smoothing” setting set at 0 and 100, and the results are the same.
DICE has previously said that the Battlefield 4 netcode is “top priority”, and the recent BF4 PC patch included some fixes for it.
This has been happening in the series for a while in the Battlefield series, where players would shoot at a moving target without any of the hits registering. But when they shot slightly behind a horizontally moving target, the hits would register. Take a look at the video below to see how this happens in BF4:
[YT]ayXTC1Vvj00[/YT]
More...
