- Joined
- Aug 20, 2007
- Messages
- 21,432 (3.40/day)
System Name | Pioneer |
---|---|
Processor | Ryzen R9 9950X |
Motherboard | GIGABYTE Aorus Elite X670 AX |
Cooling | Noctua NH-D15 + A whole lotta Sunon and Corsair Maglev blower fans... |
Memory | 64GB (4x 16GB) G.Skill Flare X5 @ DDR5-6000 CL30 |
Video Card(s) | XFX RX 7900 XTX Speedster Merc 310 |
Storage | Intel 905p Optane 960GB boot, +2x Crucial P5 Plus 2TB PCIe 4.0 NVMe SSDs |
Display(s) | 55" LG 55" B9 OLED 4K Display |
Case | Thermaltake Core X31 |
Audio Device(s) | TOSLINK->Schiit Modi MB->Asgard 2 DAC Amp->AKG Pro K712 Headphones or HDMI->B9 OLED |
Power Supply | FSP Hydro Ti Pro 850W |
Mouse | Logitech G305 Lightspeed Wireless |
Keyboard | WASD Code v3 with Cherry Green keyswitches + PBT DS keycaps |
Software | Gentoo Linux x64 / Windows 11 Enterprise IoT 2024 |
I honestly can say if I haven't noticed it on my 120hz monitor I really don't think I need a table proving to me I need an upgrade. Ignorance in this case saves cpu cycles.You would think that is the case, but it is not, the intervals are not in lock step with the monitor. Blurbusters did a whole write up on why higher hz mice are needed, I can't find the specific article at the moment, but here is their opinion.
Also, lol at believing any jitter less than 1ms could possibly be detected by a human.
If they really want to fix this "issue" the way to do it would be to lock the sensor poll to the monitor refresh rate. But big numbers sell.