well if you move the pointer, (that can only travel pixel to pixel) in a 45 degree angle, it's only natural that it will move like that, i think.


btw all my mice have always been reporting on low frequencies when moving them slowly, dont know about anything that would always report at a fix rate.

yes it is normal, all mice do this. Also you might want to apply some fix so you get rid of those red and green lines,

what kind of fix

marc C exact 1:1 registry for Win7/8.1. Although you might fix it with setting windows sens to 6/11.

yeah that's what i'm using

It will certainly report that if you have a game open while you run it.

The mouse only knows X and Y axis movement, it will always cause "stair-like" cursor travelling when moved diagonally. Except when the respective counts are received within the same report packet, then Windows will assemble both and make the cursor travel perfectly diagonally. This mostly happens at faster speeds of moving the mouse.

The polling rate in Hz naturally depends on the rate data is being received at. If your mouse only interrupts the host 2 times a second, there will be two polls during that second, i. e. 2Hz.

Did you have a game open while these lines appeared? Make sure to use 6/11 and disable EPP. No need for a fix though, in games you should just stick to raw input, especially at 2300cpi.

i was/am using the markC win8.1 fix at 6/11 and EPP disabled

And you were not in-game?

The problem cannot be the mouse. MMR has naturally no means of judging mouse movement, so the MOUSE MOVEMENT column can be deceiving at first sight. The only thing it does is compare the reported count data with the pointer behaviour. If they are mismatched, the problem lies within your system, not the mouse. Possible causes of mismatch: Hitting the resolutive borders of your screen with the cursor, re-center of the cursor in in-game scenarios, OS acceleration, OS pointer speed interpolation. EPP off, 6/11 takes care of the latter. MarkC is used for games that forcefully enable EPP by modifying the acceleration behaviour of Windows - flattening it out, so that even when EPP is enabled, there is no acceleration.

And to reiterate, "stair-like" cursor behaviour for diagonal movement is normal.

i didn't have any games open, i was just on my desktop moving the mouse around (near the middle of the monitor so no borders)

what gives?

Nothing to worry about.

Other people have already answered some of your questions, but I'll re-answer them:

Stair like effect is completely normal, and most often seen at low speeds. Internally, the mouse is scanning the mouse-mat and recording movement, and may have noted +1.2 counts of X movement and -0.9 counts of Y movement since the last poll.
It sends 1x0 and updates its internal position to +0.2X and -0.9Y.
A little more movement, +0.5X and -0.5Y and the total is now +0.7X and -1.4Y and the mouse sends 0x-1.
For some mice this happens in the mouse, for others it happens in the mouse driver software.

The MouseMovementRecorder Frequency column is just the measured time between mouse inputs (1/time), so if the mouse is slower than a count every 1ms (1ms = 1000Hz), then it will send 1 count every 2ms (500Hz), or 1 count every 4ms, and so on, slower and slower, if you left the mouse still for a minute, and then nudged it very slight, it might show 0Hz or 1Hz.

If you run MMR while also playing a game, it will show red and green because the (some) games reposition the pointer to the centre of the screen, which is what people are talking about.
That is NOT what is happening to you.

What you are seeing is that Mouse movement and pointer movement don't always happen at the same time in Windows.
The mouse can move, and then there can be a short delay until Windows also updates and moves the pointer position.

Because people freak out about MMR showing colour, MMR attempts to match up the mouse movement with the pointer movement and show a single line with no colour. It does this by waiting a short while after it sees mouse movement to see if it also sees the (maybe delayed) pointer movement.
If the pointer movement is TOO delayed, then MMR will give up waiting and show a green 0x0 pointer movement line.
When it does finally see the pointer movement, it will show a red line, because 2 or more mouse movements have caused a single larger pointer movement.

The delay seems to be longer for Windows 8.x. The delay can be longer when the system is busy.

There are MMR options to examine and diagnose this delay:

- If you want to get accurate Frequencies displayed, and don't care about the red or green press 'C' key on keyboard until MMR displays : "Catchup mode = NoCatchup".
This causes MMR to not bother delaying, and the Frequency column will be more accurate.

- If you want to ensure that you are getting exact 1-to-1 with a fix, then press 'C' key until MMR displays : "Catchup mode = Always"
If you still have much red or green, then press '+' key a few times until you get only occasional red or green.
This causes MMR to wait a longer time for the matching pointer movement.

- If you want to know how long the delays are, then press 'E' key to display extra detail (and probably also '+' key so "Max catchup delay" is around 2000 to 8000), and/or press 'S' key.
'E' causes MMR to show Extra detail about the movements.
'S' causes MMR to show how long it waited before it saw the pointer movement.
If all or most of the "Pointer:" movement reported is @+500µs or less, there is nothing much to worry about.

Wow, thanks MarkC! I had no idea you frequented these forums. Thanks so much for clearing that up for me.

I do have another question though, which can be found here: http://smoothmouse.com/forum/topic/346-looking-for-a-program/

feel free to reply here to it though!

I currently have a close friend of mine who is programming something up for me, but if you know of a program please let me know.

Thanks Mark!

I don't know of a program that does that, sorry.

if the "stair like effect" is normal, would show some paint drawings.

did you change win sens from 6/11?
that can cause distortion too if I remember correctly