Quote:
p.s. v1.4 and v1.5 have problem, v1.3 - no.
Same here. Look like problem when .NET 4.6 on system.
p.s. v1.4 and v1.5 have problem, v1.3 - no.
Win 7 x64. All .NET 4.x: Full 4.0 standalone, and then 4.5x, 4.6x - from Windows Update. Nothing else.Originally Posted by dobragab
Thanks for feedback.
Did you install THIS update?
What operating system are you using?
After 4.5 and 4.6 installed??? It's bad advice.
It always be the same!
>if it's related to foreground boosting inside the operating systemYea just trying to understand if it's related to foreground boosting inside the operating system, sounds like it's losing context which would mean the data capture task could be running with less Quantums (less priority/time) that would affect the results which sounds like that's what's happening.
>It is a measure of how well this software collects data from your usb mouse through the windows raw input api.It is a measure of how well this software collects data from your usb mouse through the windows raw input api. There's definitely other factors involved that could impact the readings, a friend and I looked at the code and there's actually a few ways to improve the accuracy of the readings. Nice for the toolbox but don't make it your only source of truth. Depending on available time, might be able to do a code pull request to the author to make the changes.
Just don't move mouse on anything else except Mousetester itself when you measure MOUSE. For what purpose you move it over other applications windows? There is way to have more precise measurement but you move into opposite direction.But moving the mouse over the desktop, brings windows explorer up to 4% cpu usage, moving mouse over Task manager only uses 1%.
It is not hipervisor timer, it's just recalculated TSC.Synthetic timer, are you running in a virtual machine?
This "new" 10MHz is just the third model of TSC using inside QPC/QPF since Windows NT.the new 10Mhz query performance timer frequency I have been able to find
You are in one step to the best possible solutionI wrote a quick and dirty mouse hook (Mouse32) to try and see what was going on.
google: qsxcv mousepad mousetester site: overclock.netI was wondering how to test whether my mouse is properly and accurately tracking on my mousepad. Can anyone help me by pointing me in the right direction? Should I do a single fast swipe or continuous fast / slow circles? What graphs am I analyzing afterwards?
Is Mousetester the appropriate tool for that or is there something else you'd recommend?