Overclock.net banner
121 - 140 of 144 Posts
Not to mention the CPI difference scales with the step as well. To a point where on some mice around 6000 step you might have a whooping extra 400 CPI.


Edit: Or mice like G402 and G302 where CPI steps not what they are labeled in LGS.
 
Is collect or log start more accurate? because i get different results when using each one...
Collect may interact with what's under the cursor adding extra overhead while Log should be relatively free of that so personally I would prefer log. However I would say both are as accurate as each other regarding the results obtained but different for reasons mentioned.
 
Founder of Blur Busters / TestUFO here.

Does MouseTester support windows hooks? Such as HOOKPROC LowLevelMouseProc via SetWindowsHookEx()

PURPOSE: By having optional window hook support, one can MouseTester simultaneously on a 2nd monitor while playing a game on a primary monitor. Testing mice under real-world full-throttle operating conditions.

In rare cases, we found that individual mouse performance sometimes degrade ONLY when the computer is at CPU100%/GPU100%, because of various factors such as OS overheads, inefficient drivers, EMI interference on USB cables (error correction latencies), etc. A mouse that works perfectly consistently (1ms intervals between polls) on a mostly idling PC, can go very inconsistent on a full throttle PC from a lot of unanticipated factors that only happens at full-throttle situations.

Near-identical setup looks massively worse than the other, for unanticipated reasons. So some gamers need to be able to MouseTester at full gaming load.

Also, ideally during hook mode, the MouseTester will need to run in Admin mode at raised process & thread priority level (higher priority than all the game threads) to minimize game-activity interferences percentage, and maximize system flaw interference percentages (OS/driver/EMI/etc factors).

MouseTester can be the low-CPU-utilization realtime-priority app to analyze mouse during a real-world gaming situation. It won't be perfect, but we've found some situations where unexpected mouse flaws emerge on some system configs but not on others (different mice / different drivers / different OS builds / etc).
 
I've made some updates to the software to address some things that came up while testing the Razer Avalon (Razer Viper 8K) mouse.

Some under the hood changes that hopefully improve the timestamping accuracy.
I removed the priority and core affinity since they didn't seem to affect things that much, at least on my system.

Aesthetic changes to plotting to help with the visualization of a much higher volume of reports compared to 1,000 Hz

Plots will look different because the smoothing lines use an 8ms time window average instead of a fixed 8 sample average. This is most noticeable at inflection points like the peak of a fast flick.

I added keyboard shortcuts to Start/Stop/Plot. The hold button to collect method still works but I've noticed the timing performance is worse than the Log Start/Stop method.


2476331

The average holds at a fairly steady 0.125ms which is 8,000 Hz in this short segment. I do get some timing blips in longer captures but I feel that is because of the software/Windows 10 more than the mouse itself.
 
It seems that windows mouse control settings they do influence the results.
My Logitech MX510 this is 800dpi , Windows offer two settings:
1) pointer acceleration as it moves .. I have disable this.
2) pointer speed movement.. I have set this at full.

This is my results ... which I can not evaluate.
Question: Should we set Windows ( pointer acceleration as it moves .. & pointer speed movement..) at very specific settings ?

2476374
 
This is my results ... which I can not evaluate.
Question: Should we set Windows ( pointer acceleration as it moves .. & pointer speed movement..) at very specific settings ?
Neither of those Windows settings are supposed to affect Raw Mouse Input, which is what the software is using to collect the counts.

To confirm you should log the same movement (can skip the measure part) with the settings changed and there should be a distinct difference in the counts if the pointer speed settings are actually affecting the data collection.
 
Neither of those Windows settings are supposed to affect Raw Mouse Input, which is what the software is using to collect the counts.
To confirm you should log the same movement (can skip the measure part) with the settings changed and there should be a distinct difference in the counts if the pointer speed settings are actually affecting the data collection.
Well in my case the pointer speed movement setting, it does affect your software, by minimizing speed movement setting I get variable results, as low as 200 up to 400 and 1700 at full.
Additionally, you software download refer to Ver 1.4 , but the software itself this mention Ver 1.3.
I am guessing that Logitech SetPoint software this using NET. , this is capable to by pass your work.
 
Discussion starter · #132 ·
Thank you, I fixed the title bar.

I am guessing that Logitech SetPoint software this using NET. , this is capable to by pass your work.
It is possible that this Logitech software is affecting the Raw Mouse data. Google search indicates certain versions will. This also means any game that uses Raw Input to collect mouse data, not just my program, will be similarly affected. In general this is not a good thing, it is better to have 1:1 mouse reports to Raw Input counts.

The settings that I was referring to are the OS Mouse Properties Motion settings and assumes the OS mouse drivers are being used.

2476428
 
The settings that I was referring to are the OS Mouse Properties Motion settings and assumes the OS mouse drivers are being used.
This is good to know, but OS mouse driver this is very poor for my mouse. But I will use one more time your software so to bring mouse data to 800 cpi and inspect performance / tracking repeat ability.

According my book, it is unwise to overload the mouse driver if you care for tracking precision.
 
Am I blind? Where is the Hz graph on the plot window.... I don't see it on 1.2 or 1.4.
First choose in Plot Type "Interval vs Time".

You have to check how far appart are dots on the horizontal graph (which is hard to check for a whole second). But it should be approx 1-2 ms, or less depending on your mouse polling rate. I Am not sure, if you can zoom even that far enough to check on scale of us. But should be enough for polling stability: try to check for any missing dots in your polling rate range. So for example 500hz = every 2ms packet from a mouse. So check if dots are each 2 ms from each other, when you max polling rate. Do quick circles!

I also recommend you to set Data Point Start and End, which should filter period when polling isn't maxed. And read tutorial how to use it to make sure, you are doing it right!

For quick polling test: you can try this: Mouse Rate Checker
Note: if you are not doing quick circles, it doesn't enough data, so don't worry your polling isn't maxed.

Also vertical placement of dots tells you: how fast DPC (interrupts) are handled by your OS.

QUESTION: I can't zoom to more than scale of 100 hundreds of us. Then it gives me some memory exception. Anyone idea why? I selected start and end period. While I saw other people had it zoomed down to 1 us!!!

EDIT: for polling rate stability, you can use Frequency vs Time and check for vertical spikes in graph! BTW this is available only in a newer version - 1.53 (which I don't think is official). It was accused to have malware somewhere, but it has even source code available I think. I have one 1.53 version - don't remember from where, but Bitdefend didn't report any detections.
 
Would it be possible to remember the last graph type used and display the next collected data using the same graph type?

Also apparently my razer 8k is refusing to run at above 1000 hz. hmmm
Try different test: Mouse Rate Checker

Check this post, maybe there will be something useful I have the new Razer 8000 Hz prototype gaming mouse on my desk. - Blur Busters Forums
Try other USB, not sure if you don't need USB 3 for 8khz. Also try disable Legacy USB support in bios and check bios features. I would also recommend to disable USB selective suspend in power plan, also for USB 3! You can use this great utility for managing power settings: Windows power plan settings explorer utility

Also make sure in device manager uncheck allow to wake computer using mouse and keyboard, unless you use it.

And uncheck allow to turn device off to save power for all: hid/mouse/keyboard/usb devices you see there!

You can also benefit from reducing mouse buffer size, this is probably from Windows 2000 times, when CPU would crap out from anything and 1ms+ DPC latency times...


Also make sure you disable dynamictick and use 0.5ms timer resolution - check ISLC. Also you will wanna test your computer for DPC latency with 8khz mouse, download latencymon...
 
hey guys you seem to know alot about this stuff and was wondering if you could help me as my g pro wireless seems to dip right down to 500hz when set to 1000hz for some reason i dont know why here is the link to the post i made about it as not to clog up this thread but any help would be very appreciated G PRO WIRELESS dips to 500hz when set to 1000hz
 
121 - 140 of 144 Posts