Hit reg issues, TTK vs TTD inconsistency.
Just left another game for the same reason as i left the last 3 games. you can shoot a whole clip on an enemy, well aimed, only getting 2 or 3 hitmarkers, the enemy turns around, 1 or 2 bullets and i...
Forum Discussion
Yup, 30Hz would have actually been better than 45Hz because it divides evenly into 60fps. Plus, most of the games subsystems also update at 60fps divisible intervals such as animations for player movements.
45Hz isn't the only thing causing all these netcode issues but it's a very obvious one that never should have happened, and it doesn't instill much confidence in DICE's knowledge of netcode in general.
@OskooI_007I don't play at 60fps and I think a lot of players doesn't do that.
Most players probably play at way more than 60 fps (100+) and furthermore the FPS varies to some degree anyway.
My fps are around 140-160 and using 30 or 45 ticks doesn't matter much nothing divides evenly to my fps anyway.
And we still play a simulated version of the game, this is the fundamental problem of online-gaming. Higher ticks will not solve the issue of lag and different pings.
In the end, Dice should do better than what we have now, even with a tickrate of 45.
@cso7777 The rendering and physics subsystems are tuned around a target framerate of 60fps. It's easy to test this using a Gsync or Freesync monitor. At 120fps with Vsync turned off the screen tear line will only jump up a little bit from the bottom of the screen. At 144fps the screen tear line will jump up much higher and take up the bottom 1/4 to 1/3 of the screen. Indeed, the game does run smoother at multiples of 60fps.
Battlefield also uses a dynamic tickrate. Players who are far away in the distance only update at 10Hz, which doesn't sync with 45Hz either.
The best way to visualize what DICE is doing is run 45fps on a 60Hz monitor with Vsync on. It's going to stutter like crazy.After a break from this game i geve it a try today...but nope...game is still broken beyond repair.
A enemy player was behind a concrete block shooting at my team...i approach him from his right side at +- 6 feet. start shooting my clip empty...he threw a granade to my team...turned to me and i met my maker. still so many flaws in this game....unbelievable.
@Mackstan71 wrote:After a break from this game i geve it a try today...but nope...game is still broken beyond repair.
A enemy player was behind a concrete block shooting at my team...i approach him from his right side at +- 6 feet. start shooting my clip empty...he threw a granade to my team...turned to me and i met my maker. still so many flaws in this game....unbelievable.
It really is in a very bad state at the moment, there are way too many such moments happening nearly every round, we need a fix asap.
@Mackstan71I got an email from EA yesterday to take a 30 -40 minute survey about BF 2042. It was very detailed and talked about the cheating issue and the TTK/TTD. I also gave them a few other issues that need attention. I hope that they pay attention to the remarks and input of players that got the survey. I know I have been a thorn in their side ever since this game came out.
So I wonder what will be done to fix it?
@Adamonic: Did the survey have a section where you would select from 5 selections between "Very Satisfied" to "Very Dissatisfied"? I also talked about the TTK / TTD issue in the section you could put comments in. I explain about the amount of conversations on the general forums on HelpEA.com and how no one from EA has answered any player that posted a comment. I hope they listen to the surveys and fix what needs to be fixed. I have also notice a drop in attendance on the servers since the new MW 2 was released, this is on both EA official and the portal.
@RayD_O1There is a video that EA had created from The development team what they are doing about issues, maps and other things.
https://youtu.be/ILzSJehTK7Q
@Chaz63 wrote:@RayD_O1There is a video that EA had created from The development team what they are doing about issues, maps and other things.
https://youtu.be/ILzSJehTK7QI had watched that video on release but I didn't notice any reference to this long standing issue which is why I think an update would be beneficial.
