Re: NVIDIA G-Sync Pulsar monitor - Asus ROG Strix XG27AQNGV
Posted: 07 Mar 2026, 13:26
No. Human hand shakiness.hash wrote: ↑06 Mar 2026, 19:45Could you elaborate on this handshake filter thing? I tried google but not much showed up.Chief Blur Buster wrote: ↑25 Feb 2026, 22:10A lot of GSYNC Pulsar benefits disappear with 400/800dpi mice settings, common in CS2 for handshake-filter, but hurts Pulsar blur busting.
Is it some kind of overhead when starting and stopping usb data transmission?
(i made an account just to ask this question lol)
When DPI is high, micro shakiness from hands can become visible, and some paid esports athletes use 400-800dpi in CS2 to prevent that.
This is not easily googled stuff (unless you've got Level 10 Expert Google-Fu). This is "VIP ESports Talk" or fanatical stuff, the people who talk to people on prosettings.net and invitation-only Discord channel.
However, the problem is that if you're using low-MPRT, the low DPI can sabotage slow mouse movements. 400dpi is only 400 mouse positions per inch. So if you move at 0.25 inch per second, you have only 100 mouselook frames per second. Why throttle your brand new 720Hz or 1000Hz monitor to only 100fps, when you can use higher DPI and lower sensitivity. 1600dpi at one-quarter mouse sensitivity you used to use at 400dpi, to get the same edpi calculated at mouse-sensitivity website calculator.
Likewise, 400 dpi has more mouse coarseness at slow mouse movements, which means your mouselook frame rate can be below your Pulsar refresh rate = rough mousefeel during slow mouse looks / multiple image effects during slow mouselooks.
This does not affect fast flicks (Ideally no difference between [email protected] vs [email protected] or [email protected]), but high DPI can make your shaky/shivering/muscle-spasms/human-imperfections more visible.
However, 1600-3200dpi massively improve the pros of improved slow-mouselooks / slow-hunting / slow-tracking (e.g. like a sniper hunting through forest for camoflaged enemies, or 3rd-person POV adjustments like Rocket League, or trying to read RTS map while scrolling RTS map a bit slower). It keeps those slow-movements at a high frame rate without Hz-sabotage or Pulsar-sabotage.
Recommended Pulsar Mouse Settings to prevent Pulsar sabotage
(Difference between "I don't notice Pulsar" versus "Wow, Pulsar looks visually great for slow mouse movements")
- Mouse 1600dpi or more.
- Mouse 2000Hz (unless it overloads mouse loop, then go back to 1000Hz)
- *Higher poll rate is OK in RawInputBuffer-capable games like Valorant (4000-8000 becomes usable without overloading CPU loops)
- High quality mouse pad, clean mouse pad, high quality mouse sensor, wipe mouse feet often
- Game Proportionally Lower Sensitivity
- Window Control Panel Mouse Pointer "Enhance Precision" = OFF
- Window Control Panel Mouse Pointer "Sensitivity" = slightly lower to slow down mouse cursor
NOTE: The last bullet used to be not recommended (interferes with old games like Wold of Warcraft) but all new games ignore Windows Control Panel except for mouse pointer behaviors.
Make sure you use a calculator like mouse-sensitivity.com to figure out settings to use. Preserve your muscle memory, make sure aimtrainer behaves the same as before, so try to perfectly adjust DPI:sensitivity ratio by raising DPI while lowering sensitivity. Many games won't let you enter 3 digits, e.g. 1.0 -> 0.125 = problems. Sometimes you have to edit a text file (.ini .cfg) to edit the extra digits, e.g. old copies of Team Fortress 2.