May 9 2011, 07:57 AM, updated 15y ago
QUOTE
fdsdfg United States. December 08 2010 06:49. Posts 815 Profile #
'Reduce mouse delay' will read the hardware input of the mouse rather than the Windows API.
Since it cannot disable window's reading of the hardware input (only lock the pointer), this means the data is being read twice - by windows and by sc2.
Now, instead of SC2 asking windows 'what's my x-y coordinates?' it has to have a hook into the mouse driver to read the raw input, interpret that into relative movements, and finally into x-y coordinates.
Pro - not waiting on Windows API / polling rate
Con - extra overhead
'Reduce mouse delay' will read the hardware input of the mouse rather than the Windows API.
Since it cannot disable window's reading of the hardware input (only lock the pointer), this means the data is being read twice - by windows and by sc2.
Now, instead of SC2 asking windows 'what's my x-y coordinates?' it has to have a hook into the mouse driver to read the raw input, interpret that into relative movements, and finally into x-y coordinates.
Pro - not waiting on Windows API / polling rate
Con - extra overhead
This post has been edited by pepsi89: May 9 2011, 07:58 AM
Quote
0.0416sec
0.32
6 queries
GZIP Disabled