Who you gonna call? The Blur Busters! For Everything Better Than 60Hz™
https://forums.blurbusters.com/
A Blur Busters Patreon is coming later this year -- keep an eye out for it!RocketRager wrote: ↑06 Apr 2021, 17:55A real hero. If I rank up past champ, I’m donating to the site somehow lol
100% will utilize.Chief Blur Buster wrote: ↑06 Apr 2021, 17:59A Blur Busters Patreon is coming later this year -- keep an eye out for it!RocketRager wrote: ↑06 Apr 2021, 17:55A real hero. If I rank up past champ, I’m donating to the site somehow lol
Does synchronizing SPI with USB polling events in the mouse firmware matter if you use a 240hz monitor? Does it reduce microstutters?Chief Blur Buster wrote: ↑06 Apr 2021, 17:48Theoretically Possible: Custom Frame Rate Capping Software That Syncs To Poll Rate
If you are a software developer, there is a solution
Now, there are potential workarounds, like writing a custom frame-rate capper that uses a mousehook (LowLevelMouseProc callback and the WH_MOUSE_LL event). Basically an RTSS clone that monitors the mouse poll rate and synchronizes frame rate to a divisor of the mouse poll rate. And using a 280 Hz VRR monitor to achieve the low-lag 250fps frame rate cap synchronized to poll rate (1000Hz).
Recipie:
1. VRR display
2. Refresh rate capable of syncing to poll rate
3. Custom frame rate capping software that syncs to poll rate (or divisor thereof)
However, just merely upgrading to 240Hz display refresh rate will still be a big upgrade even for refresh-rate-unsynchronized 1000Hz device poll rate.
SPI means thousands of things to me, mostly non-mouse-related. Can you narrow down your question to something specific? Unless you’re referring to sensor rate (which is not necessarily relayed over an SPI bus).axaro1 wrote: ↑07 Apr 2021, 11:25Does synchronizing SPI with USB polling events in the mouse firmware matter if you use a 240hz monitor? Does it reduce microstutters?Chief Blur Buster wrote: ↑06 Apr 2021, 17:48Theoretically Possible: Custom Frame Rate Capping Software That Syncs To Poll Rate
If you are a software developer, there is a solution
Now, there are potential workarounds, like writing a custom frame-rate capper that uses a mousehook (LowLevelMouseProc callback and the WH_MOUSE_LL event). Basically an RTSS clone that monitors the mouse poll rate and synchronizes frame rate to a divisor of the mouse poll rate. And using a 280 Hz VRR monitor to achieve the low-lag 250fps frame rate cap synchronized to poll rate (1000Hz).
Recipie:
1. VRR display
2. Refresh rate capable of syncing to poll rate
3. Custom frame rate capping software that syncs to poll rate (or divisor thereof)
However, just merely upgrading to 240Hz display refresh rate will still be a big upgrade even for refresh-rate-unsynchronized 1000Hz device poll rate.
, with 1000hz I play more stable and better, according to this theory will try to check 2000 hz )) tyI mean synchronizing optical sensor data with polling events, like Razer is doing with Motionsync.Chief Blur Buster wrote: ↑09 Apr 2021, 23:13SPI means thousands of things to me, mostly non-mouse-related. Can you narrow down your question to something specific? Unless you’re referring to sensor rate (which is not necessarily relayed over an SPI bus).
Visual jitter experience, in the phantom array effects;Anonymous475812 wrote: ↑23 Jul 2022, 21:19How did you determine that it should be at least 6x oversample and would there be any benefit going beyond that? In example 2000Hz poll for 144Hz monitors, which is 14x oversample.Chief Blur Buster wrote: ↑06 Apr 2021, 17:09For unsynchronized poll rates, you just need to oversample by about 6x, to prevent any mouse microstutters.
It is true that 1000Hz poll is too low for 360Hz monitors, since that's only a 3x oversample, when eliminating the mouse microstutters requires a higher oversampling factor, about 4 to 6x, preferably closer to at least 6x oversample.
