Re: Hit reg issues, TTK vs TTD inconsistency.

Nice post with some good tips! @cyej6kkea5u6 

I have a 8,000Hz mouse too (Razer Viper 8k) and noticed Battlefield 1 behaves weirdly with such high polling rates. It causes encounters with enemy players to playback at fast forward speed instead of regular playback speed. Like when fast forwarding through a movie. The end result is I have less reaction time at high mouse polling rates.

To fix this with the Viper 8k, I plug it into a USB 2.0 hub which causes the mouse to fallback to 1,000Hz polling (full speed USB) and I set the optical sensor's polling rate to 125Hz in Razer Synapse. I also cap Battlefield 1's framerate to 125fps because the game engine processes mouse input at a locked 125Hz.

Setting the optical sensor to 125Hz in BF1 results in butter smooth mouse movement because the optical sensor is perfectly synchronized with the game engine's 125Hz mouse input processing. 250Hz, 500Hz and 1,000Hz cause too much of the fast forward effect mentioned above. Not to mention 250Hz, 500Hz and 1,000Hz cause more mouse stutter from being hugely desynchronized with the game engine's 125Hz mouse input processing.

Ever see someone say, "I'm playing Battlefield at 120fps but it feels like the game is only running at 60fps". It's due to the mouse input not being synchronized with the game engine, causing the camera to stutter when you move the mouse. Giving the appearance of a low framerate.

There's so much broken with mouse input in Battlefield games. Supposedly all this is fixed now in Battlefield 2042, but I haven't tested it since I don't play the game.

But yes, working around Battlefield's broken mouse input made the hitreg, playback speed of enemy encounters, and aiming waaaay more consistent for me in Battlefield 1.

I used to think it was the servers causing all these issues but nope, just broken mouse input. And that's not even getting into adjusting analog stick deadzones, analog stick sensitivity, analog stick aim assist, etc.... all of which affects mouse aim in Battlefield too! Every single controller setting affects mouse aim in Battlefield.

I can post the best controller settings to minimize the effect on mouse aim if anyone is interested. You definitely want aim assist turned off so it doesn't slow your mouse cursor down.

I've also noticed Battlefield 1 has trouble processing input from keyboards when the polling rate for keyboards is set higher than 125Hz. Causing the fast forward effect during enemy encounters mentioned above. I haven't heard mention of this being fixed in 2042, so make sure your keyboard is set to 125Hz.

So many weird bugs in this game that can ruin the gameplay experience and put you at a competitive disadvantage without you even realizing it.

@cyej6kkea5u6Low latency mode in Nvidias control-panel is for DirectX 9/11 only, not for DirectX 12. 2042 uses DX12.

Reflex / Boost has an effect on DX12 though (Boost is power-management and disables dynamic lowering of GPU-clocks).

The UI is awful and is a bad console-port. But this should have no effect on the game-engine. The TTK/TTD-problems have been in Frostbite for a long time, they only seems to have gotten worse in 2042 than in previous titles (especially compared to BF1/BFV).

The TTK/TTD-problems have been in Frostbite for a long time, they only seems to have gotten worse in 2042

That's unfortunate because I stopped playing Battlefield 3 (THREE!) because of the terrible TTK/TTD problems. I can't believe they're still happening.

@cso7777 

Man, BF4 really hurt you, didn't it?

You seem to really hate on that game a lot, lol.

@Jubei-Dakuan Battlefield 3 was really bad when it comes to netcode, the lag compensation was very obvious in this game. But the positive about it was that it was pretty consistent and predictable combined with the supressions system it allowed you to adapt your playstyle to take advantage or at least work with the flow of the netcode. In Battlefield 2042 it's just so inconsistent you start to doubt yourself from one play session to the next.

Man that’s really a shame because the Battlefield games are the best looking with the largest maps. I’ve been playing Battlefield V lately but the player count and hackers are making me want to switch to 2042. It sounds like it’s completely broken though. That’s really too bad because there aren’t any other large scale FPS out right now. 

@Jubei-Dakuan2042 is a "bad"/weird BF-game, but it is still a BF-game.

It plays more like BF4 than BFV (faster paced) and the TTK is very fast compared to BFV.

The netcode is pretty bad and the specialist system is weird, but you can still have fun in 2042. The new 'class-system' has made the game feel more like BF than ever.

Many of the issues in 2042 are the same as in older titles with unbalanced vehicle/infantry gameplay, meta-weapons etc.

Cheaters are very rare in 2042, I have only seen very few cheaters (less than 10), during my time with 2042 (nearly 500 hours). EAC works better than any other anti-cheat-system Dice has used before.

If you can get 2042 for cheap, I would say it could be worth trying.

I’ll probably snag it the next time it goes on sale under $20, but my PC is old.

Well I am back to feeling like I am getting killed faster again