EPT![[image loading]](http://www4.slikomat.com/11/1015/ga-spad.jpg)
Mouse Movement Recorder - Page 4
| Forum Index > Tech Support |
|
Srdjan2311
Serbia20 Posts
| ||
|
Medrea
10003 Posts
I did however get a lot more red blocks (increased flat velocity) than the last test where I got none at all really, which leads me to believe that this test may not be appropriate for the MX518. It is afterall a really old mouse. And yes every mouse that has over-prediction will have this experience reduced at high polling rates. under predicted mice will also wobble less. Perfect predicted mice will be perfect, but there is no such thing as perfect prediction unless the mouse was made for like a perfect diamond mouse mat or something. Or it can read the future, or your mind. EDIT: hmm, I decided to set my windows to 6/11. And i ran the previous two tests again. Neither red blocks or green showed up in either test (expected, i would have been surprised otherwise). In both tests I ran with no mu values at all. hmmmm. | ||
|
ilovelings
Argentina776 Posts
| ||
|
Medrea
10003 Posts
EDIT: I know when in doubt 6/11 but I just want to make sure about what the mu value actually means. UPDATE: Alright here is the deal. 5/11 adds a flat decreased in velocity to the mouse where 6/11 is raw input.I can move the mouse, and the mouse signals the motion value, but the cursor will not move to the next pixel because the movement is not enough to move to the next pixel with that decreased sensitivity, even though it is enough at 6/11. Because a cursor change is not registered until the next movement where the remainder pushes the cursor to the next pixel, this is registered as a net 500 mu (1000/2). That being said. When it comes to other people, I always recommend 6/11 sensitivity as it makes debugging way eaisier. To demonstrate this. I will update with another picture. | ||
|
Medrea
10003 Posts
+ Show Spoiler + ![[image loading]](http://dl.dropbox.com/u/34863088/skipless%206_11.png) | ||
|
Srdjan2311
Serbia20 Posts
 . I learned quite a few new things from you thanks. | ||
|
Medrea
10003 Posts
On October 16 2011 08:19 Srdjan2311 wrote: yeah it does. It indeed means your mouse input is stable Heh. When determining if a user is having a problem, I always have them set windows to 6/11. Never go higher than 6/11 as it can introduce skipping. Lower is just not "true 1:1" That 1k 1k 1k .5K behavior also scares a lot of people. But it is no worry. EDIT: honestly the most important thing is that enhanced pointer precision is OFF. Even in games. Everything outside of that we can live with. | ||
|
Cyro
United Kingdom20326 Posts
On October 16 2011 06:06 Medrea wrote: Ok I need to make something clear. There is no instability. I am overpolling the device. The results are EXACTLY as expected. Here is how the breakdown works. The MX518 in my hand I estimate updates around 800 times a second (actually a little higher or lower than that but for example purposes this will do), varying on a bunch of different factors. The first poll reads nothing. .200ms later the mouse updates. -poll reads the mouse. .400 ms later the mouse updates. -poll reads the mouse. .600 ms later the mouse updates. -poll reads the mouse. .800 ms later the mouse updates. -poll reads the mouse. Hard to say since it is the exact same time in this example, but lets say the mouse has not produced a value yet. If it doesn't here it will definitly will on the next poll. The polling rate will be measured by that application as 500/1000/1000/1000/500. It is normal and perfectly stable. It is easy to figure out what to expect given those flags you gave me. -alwayscatchup -showcatchupdelay + Show Spoiler + ![[image loading]](http://dl.dropbox.com/u/34863088/skipless.png) Yes as expected. Notice how the pattern is always 2 to sometimes 4 1k's and then a 500. I tried my best to whip the mouse around as much as I could. The pattern is VERY stable. The imperfections you see are a combination of human error, and sometimes imprecision. In the screenshot above, I was probably making a turn. EDIT: After rereading through I found that some people could be confused by the green blocks. The green blocks means the mouse on screen moved less than the mouse told the operating system. This is NOT negative acceleration. This is lower total velocity. Quite simply, I lowered my sensitivity in windows from 6/11 to 5/11. I don't have to worry about pixel skipping, afaik win7 fixed that problem. Its an unfixable problem. If you are running anything that doesnt directly multiply into 1.0, you get pixel skipping. 6/11 is 1.0 sensitivity, 4/11 is 0.5 There are a few other settings you can use to change sensitivity without inconsistent pixel skipping, 5/11 is not one of them. Anything above 6/11 will multiply your mouse input, making you unable to select certain pixels, but if the sens multiplies into 1 you wont skip inconsistently. The settings you can use for this are 1/11, 2/11, 3/11, 4/11, 6/11, 8/11 and 10/11. The others are inconsistent | ||
| ||
