Fix the mouse input
I just went to play BFV for the first time in monts and the difference is night and day Is it really impossible to port the code use for BFV? I have never seen a AAA title where the mouse input is ...
Forum Discussion
@DuaneDibbleyI never stated I was overclocking the mouse past it's maximum polling rate. What I'm doing is increasing the polling rate for slow mouse movement.
I explained how mice poll slower when mouse movement is slow. Like 50Hz polling slow. By increasing dpi that slow mouse movement now polls at 1,000Hz. Mice can poll slower than their bInterval value by NAKing polling requests.
I explained how the mouse gets extremely stuttery in BF1 when mouse polling is set to 125Hz and the framerate capped to 125fps. Increasing mouse polling makes this stutter less noticable. The stutter is being caused by dropped mouse polls.
I have a high level understanding of USB protocol. Including USB descriptors such as bInterval. I also understand the Windows OS driver polls the mouse and the mouse responds to those polls.
The game isn't directly polling the mouse. The OS mouse driver is. That's why mice can be polled at 1,000Hz by the driver, with the game's input loop sampling the driver at 250Hz. The 250Hz engine samping is where mouse polls are being dropped. Not at the OS mouse driver level.
All I can say is I've field tested 20,000dpi with high polling rates for small mouse movements in Battlefield 1 and I've noticed a huge difference in how the mouse behaves. Smoother, more steady, and no jitter at high dpi.
@OskooI_007
Not sure why you think I thought that you were "overclocking the mouse past it's maximum polling rate". I did just explain how mouse input works and how it reaches the game. If you are a expert on USB communication as well, then let's say the explanation was aimed at the other people reading the thread that might want to understand how these things work.
And sure, in theory a mouse could have 'no new information' when polled in which case it indeed NAK the poll and add another delay (depending on what is in bInterval, which for my mouse is 1), but this would only happen if no new information is available (read: no button press or no increment in any direction from sensor). You decrease the likelyhood that 'no new information' is available if you increase DPI that might have an effect on very slow mouse movements, but if you have to accumulate over 4 or even 8 poll results anyway, this should not matter. And in any case, even with a slow mouse movement of less than 3 cm / second you will have with 1000 Hz polling rate one increment in every poll.
Sure, if you mouse has a high bInterval and for one poll would decide to NAK as the movement was so slow that there was no new data), then this could have an effect. But then I'd say it is a 'bug' if the USB descriptor has bInterval of >1.
Not sure why you think I thought that you were "overclocking the mouse past it's maximum polling rate". I did just explain how mouse input works and how it reaches the game. If you are a expert on USB communication as well, then let's say the explanation was aimed at the other people reading the thread that might want to understand how these things work.
And sure, in theory a mouse could have 'no new information' when polled in which case it indeed NAK the poll and add another delay (depending on what is in bInterval, which for my mouse is 1), but this would only happen if no new information is available (read: no button press or no increment in any direction from sensor). You decrease the likelyhood that 'no new information' is available if you increase DPI that might have an effect on very slow mouse movements, but if you have to accumulate over 4 or even 8 poll results anyway, this should not matter. And in any case, even with a slow mouse movement of less than 3 cm / second you will have with 1000 Hz polling rate one increment in every poll.
Sure, if you mouse has a high bInterval and for one poll would decide to NAK as the movement was so slow that there was no new data), then this could have an effect. But then I'd say it is a 'bug' if the USB descriptor has bInterval of >1.
- @DuaneDibbley The response rate of optical sensors is easy to test with a polling rate tester such as MouseMovementRecorder.exe which I linked to a few post ago.
Set the mouse dpi to 800dpi or even 3,000dpi. Move the mouse very slowly and MouseMovementRecorder.exe will show the optical sensor replying at a very low frequency. Better yet, take your hand off the mouse so it's not moving and the optical sensor will reply at 0Hz. If the optical sensor is replying at 0Hz with a 1,000Hz bInterval, that means the optical sensor is NAKing 1,000 poll requests.
Now increase the dpi to 20,000 and see what MouseMovementRecorder.exe reports even with the mouse completely stationary. It'll be replying at a much higher frequency.
Also of interest, Windows polls the mouse buttons on the Viper 8k at 8,000Hz but only polls the optical sensor at the polling rate set in the Razer mouse software. The polling rate for optical sensor is rate limited with NAKs.
If Windows is polling the mouse at 8,000Hz but the optical sensor is set to 1,000Hz, then the sensor NAKs 7,000 out of 8,000 poll requests. If the mouse is completely stationary at low dpi, it's NAKing all 8,000 polling requests.
