Battlefield 4's Most Frustrating Bugs Finally Ironed Out - HotHardware
Battlefield 4's Most Frustrating Bugs Finally Ironed Out

Battlefield 4's Most Frustrating Bugs Finally Ironed Out

Ever since it launched last year, Battlefield 4 has been practically synonymous with how not to launch a major entry to a beloved online franchise. Finally, some of the major flaws are being repaired -- or at least, they've been fixed on the beta Community Test Environment (CTE) server. This is the new server system Dice has set up for PC players that subscribe to Battlefield Premium and they've been rolling out new game changes over the past week.

One of the major changes coming to BF4 is an increase in what's called the "tickrate." The term refers to how often the game updates the location of objects and players. In BF4, the tickrate has been just 10Hz, or 10x per second, compared to 30Hz in games like CoD and as high as 60Hz in games like Counter-Strike. Now, the game will tick as high as 30Hz (30x per second), though the option will be client-side adjustable for older, slower PCs that can't handle the higher sampling rates.

The reason the tickrate adjustments matter so much is that the low tickrate has been contributing to a host of other problems, including kill shots from supposedly dead players, bullets doing double damage (calculated as passing through the player twice due to poor modeling from the low tickrate), and may have contributed to the dreaded rubber band issue. These fixes also solve the ridiculous "shot around corner" issue that has plagued BF4.


This is how slow tickrates contributed to player death. The player has knelt, but the game thinks the player is standing.

Other changes include a reduction in screen shake caused by explosives and a host of additional adjustments large and small to the game's underlying netcode. This is part of Dice's long-term commitment to BF4 and the changes are welcome -- though a substantial group of players continues to ask how these problems could have been allowed to proliferate in the first place. For months, the BF4 devs resisted adjusting the tickrate -- but now it seems that this low 10Hz sampling rate was indeed the cause of many problems.

There's no word yet on how long changes will live on the CTE before they go live, or when Dice will invite more players to play on the test server. 
0
+ -

Jonathan Paez - Should of just made it 100 tick rate like cs and those bugs will go away

0
+ -

I think they were concerned about the tickrate affecting server and client performance. But BF4 really isn't that demanding as far as system requirements.

0
+ -

Yeah .. bugs that should have been fixed before release. .. good fail EA. As usual.

0
+ -

I wouldn't call a 10 tick rate a bug. That's just appalling. Counter-Strike may be one of the very very few games that needs higher than 30. Hell many believe higher than 60 because it's that noticeable for twitch gameplay. Games like Battlefield and COD are a little different where they could get by with much less, but one would figure they'd have a tick rate of at least 30 for a FPS.

Insane mistake.

0
+ -

10Hz tick rate is mainly because of just how much data is being updated every second during some events. Not only would 30hz mean 3x the calculations, but also 3x the data drain on the servers and your own computer. And even then it only helps when you have less than 100ms of lag (and you need about 33ms lag for 30Hz to work at 100%)

0
+ -

they not going to fix the game to late theye have few games they working on

0
+ -

That isnt a bug. A bug is an unforeseen side effect. This was a (bad) decision that led to many bugs. Why would they choose to use a lower tick rate than every other game and assume it would work out?

0
+ -

they still have not worked out the bugs in medal of honor warfighter for pc. mine still crashes to desktop. luckily i bought it for ps3 for $2 at gamestop. so if it stops working. i only lost $2 :)

0
+ -

My grandkids will love this. This is the next game they want. Grandpa does not disappoint !

Login or Register to Comment
Post a Comment
Username:   Password: