Sorta... I've only had problems with quake 3, but I'm not sure if it was cause of my mouse or the polling rate.
The thing is that, just as you said, quake had a input buffer overflow and in occasions it wouldn't detect the mouse click or scroll. I solved it easily by setting in_mouse to -1, which removes the buffer, and is event based instead.
I could guess that most newer games have solved that problem, or have a way of disabling the input buffer as well.
Edit: Just looked it up, and seems that it would only happen with 1000Hz polling rate and a high end mouse. The reason is that the buffer method receives 1000 reports per second(at least with quake 3), and could bottleneck with high end mice that deliver just or slightly above that limit. If you happen to have this problem with any game and can't find a way to disable the input buffer, setting the polling rate to 500Hz should solve it, as the buffer would only receive 500 reports per second.
__________________
Damage is king, Speed kills, Style is everything.
CPU Core i7 920 (0x6A5/D0) |
Motherboard ASUS Rampage II Extreme |
Memory Corsair Dominator 3x2GB DDR3 |
Graphics Card ASUS EAH4890 TOP 1GB GDDR5 |
Hard Drive 1x1TB, 1x500GB Seagate |
Sound Card X-Fi XtremeGamer |
Power Supply ABS Tagan BZ 800W |
Case Cooler Master Cosmos RC1000 |
CPU cooling Thermalright TRUE Black 120 |
GPU cooling Stock, Non-Reference |
OS Windows 7 x64 |
Monitor 24" Acer P243WAID |
Last edited by DataX : 09-23-06 at 08:16 PM
|