Joined
·
1,213 Posts
In the process of hoarding mouse related web files before they can't be found anymore I came across the updated version of Mouse Movement Recorder packaged in the windows 10+8.1+8 MarkC mousefix.
This version of MMR has a new functionality to influence "catchup"
From the readme:
Quote:
To visualize the discrepancy either: press "s" to show catch up delay.
or set it to "noCatchup", because it's not a real condiment.
Show catchup delay, and loops
No sauce:
Whichever view you prefer. On noCatchup the delayed movement will be shown on the next poll.
Tested on Windows 7 x64, fixed clock frequencies. Timer resolution does not affect this whether its 15.6ms or 0.5ms , nor does hyper-threading, core-parking, dwm, mouse fix (in before...) or anything else.
Windows cursor is just a mess.
How to recreate:
Put your computer under any type of load:
Open some explorer windows, notepad, steam and a web browser if you really need to.
Using two screens and/or playing videos is very good for showing this.
Move the mouse around at different speeds, sometimes it happens more at low speed sometimes at high.
Dedicate at least a couple minutes to testing as this behavior is by definition inconsistent.
This delay happens even without doing such things, but way less often.
If you're on wi-fi, you're basically doomed.
![smile.gif]()
This doesn't not show up on old mouse movement recorder as it behaves like "autoCatchup" without shown delay.
You could observe discrepancies when dragging windows but this is by just moving the cursor.
This brings me to ask: is wm_mousemove the problem or does GetCursorPos get treated with low priority?
If it's the second, then rinput will suffer the same fate.
Could be irrelevant since probably game simulation is set up to "catchup" as well, but that's not granted.
Try it out for yourself. See how bad it is on later windows versions.
This version of MMR has a new functionality to influence "catchup"
From the readme:
Quote:
As soon as you open up the program you will get prompted with the command list. You can recall it whenever you want by pressing the space bar.
To visualize the discrepancy either: press "s" to show catch up delay.
or set it to "noCatchup", because it's not a real condiment.
Show catchup delay, and loops
No sauce:
Whichever view you prefer. On noCatchup the delayed movement will be shown on the next poll.
Tested on Windows 7 x64, fixed clock frequencies. Timer resolution does not affect this whether its 15.6ms or 0.5ms , nor does hyper-threading, core-parking, dwm, mouse fix (in before...) or anything else.
Windows cursor is just a mess.
How to recreate:
Put your computer under any type of load:
Open some explorer windows, notepad, steam and a web browser if you really need to.
Using two screens and/or playing videos is very good for showing this.
Move the mouse around at different speeds, sometimes it happens more at low speed sometimes at high.
Dedicate at least a couple minutes to testing as this behavior is by definition inconsistent.
This delay happens even without doing such things, but way less often.
If you're on wi-fi, you're basically doomed.
This doesn't not show up on old mouse movement recorder as it behaves like "autoCatchup" without shown delay.
You could observe discrepancies when dragging windows but this is by just moving the cursor.
This brings me to ask: is wm_mousemove the problem or does GetCursorPos get treated with low priority?
If it's the second, then rinput will suffer the same fate.
Could be irrelevant since probably game simulation is set up to "catchup" as well, but that's not granted.
Try it out for yourself. See how bad it is on later windows versions.
