Blur Busters Forums

I tried adjusting MouseDataQueueSize to 300 (decimal).

I found that the input latency decreased. You can try it out.

Sandy wrote: ↑

22 Nov 2025, 06:48

I tried adjusting MouseDataQueueSize to 300 (decimal).

I found that the input latency decreased. You can try it out.

100 is the default, 300 should make it worse

This setting has no real effect.

rekaa02511 wrote: ↑

22 Nov 2025, 08:45

Sandy wrote: ↑

22 Nov 2025, 06:48

I tried adjusting MouseDataQueueSize to 300 (decimal).

I found that the input latency decreased. You can try it out.

100 is the default, 300 should make it worse

I tested it for a long time in CS1.6 and the mouse response is much faster.

Hyote wrote: ↑

22 Nov 2025, 08:51

This setting has no real effect.

I also tested decimal -1, and it automatically became 4294967295. This also works very well; bullets can easily hit enemies. Windows is really strange; changing any number and then switching back to the game, you'll feel a difference in latency and accuracy.

rekaa02511 wrote: ↑

22 Nov 2025, 08:45

Sandy wrote: ↑

22 Nov 2025, 06:48

I tried adjusting MouseDataQueueSize to 300 (decimal).

I found that the input latency decreased. You can try it out.

100 is the default, 300 should make it worse

I also tested decimal -1, and it automatically became 4294967295. This also works very well; bullets can easily hit enemies.

No, you can make up a random DWORD, set it to the max value and notice a difference either because of some placebo effect or Windows is just making something up for a few moments. Regardless this value does nothing and if you want to optimize your PC, then look for real values that affect real things. Mouse and keyboarddataqueuesize are of no use.

stop these placebo windows tweaks ffs

dermodemon wrote: ↑

23 Nov 2025, 05:50

stop these placebo windows tweaks ffs

The `mousedataqueuesize` value causing mouse issues was confirmed by Microsoft during the Windows XP era, but it has never been completely resolved. Microsoft simply set the default value to 100.

Today I also tested it with a decimal value of 80, and the overall screen was smoother, but the mouse occasionally became unresponsive.

This value supports a range from 1 to 4294967295, which is an extremely large range; no one can test all the numbers.

I don't know how to get this through so you understand. The value is in effect, you can set it too low and make your mouse and keyboard lose packets but these values contribute nothing to latency or performance.