I say [1-8]ms as there is no way to predict if frames or mouseinput will be 'perfectly' synched: the ms before the frame got rendered a mouseinput was received so the delay between mouseinput and frame is 1 ms. Or the 'worstest' synched: the ms after a frame got rendered and mouseinput was processed, a new mouseinput was received. The maximum delay between mouseinput and frame will be 8ms.
So how could we do better 'in theory'. We cannot increase the FPS due to config restrictions preventing spreadlaming. So the only thing we can do is increase the mouserate. As shown with loekino's drumming, we want to double the mouserate to keep the beats in tune. So if we have 125fps / 250hz the delay interval will be [1-4]ms.
The 'bestest' synch: 1ms, a frame gets rendered the ms after an input was received.
The 'worstest' synch: 4ms, just before the frame got rendered a mouseinput was received. This time the interval is 4 because mouseinputs are beeing sent at double the speed.
Continuing this line of thinking we should decide 1000hz is the 'bestestest' synched as it in theory should give you a 1ms interval as mouseinputs are beeing sent 1000 times a second and there will always be a mouseinput the ms before the frame. In rL mouse dont give stable 1000hz polling rates. You can check it out for yourself: even while doing the most fast circles on your mousemat its impossble to keep a stable 1000hz. This results in loekino skipping some beats and in the end the delay that was constant turns into one big chaos.
As you can see there is no problem when using lower fps as long as the 500/ fps = integer 1,2,3, etc. The result is you will have a fixed amount of beats every frame, a fixed amount of mouseinputs per frame. This results in a more consistent tracking. 500fps
250fps
166fps
125
100
83
71
63
Long story short:
use 500hz
cap fps: 125, 100, 83, 71, 63
So how could we do better 'in theory'. We cannot increase the FPS due to config restrictions preventing spreadlaming. So the only thing we can do is increase the mouserate. As shown with loekino's drumming, we want to double the mouserate to keep the beats in tune. So if we have 125fps / 250hz the delay interval will be [1-4]ms.
The 'bestest' synch: 1ms, a frame gets rendered the ms after an input was received.
The 'worstest' synch: 4ms, just before the frame got rendered a mouseinput was received. This time the interval is 4 because mouseinputs are beeing sent at double the speed.
Continuing this line of thinking we should decide 1000hz is the 'bestestest' synched as it in theory should give you a 1ms interval as mouseinputs are beeing sent 1000 times a second and there will always be a mouseinput the ms before the frame. In rL mouse dont give stable 1000hz polling rates. You can check it out for yourself: even while doing the most fast circles on your mousemat its impossble to keep a stable 1000hz. This results in loekino skipping some beats and in the end the delay that was constant turns into one big chaos.
fps= 125 = 8ms usb= average 666
frames 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0
inputs. 1 1 0 1 0 1 1 0 0 1 1 1 0 0 1 0 1 1 1 0 0 1 1 0 1 0 1 1 0 1 0 1 1 1 1 0 1 1 1 0 1 0 1 0 1 1 1 1
So lets take the highest possible mouserate thats stable at all times?
fps= 125 = 8ms usb= 500 stable
frames 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0
inputs. 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
OR
frames 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0
inputs. 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
As you can see no matter what the the mouseinputs will be stable, the delay will be a constant 1 or 2 ms. But what happens if you got a shit pc that doesnt do 125fps?
fps= 100 =10ms usb= 500 stable
frames 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 0
inputs. 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0
As you can see there is no problem when using lower fps as long as the 500/ fps = integer 1,2,3, etc. The result is you will have a fixed amount of beats every frame, a fixed amount of mouseinputs per frame. This results in a more consistent tracking.
500fps
250fps
166fps
125
100
83
71
63
Long story short:
use 500hz
cap fps: 125, 100, 83, 71, 63