lol

you dont seem to understand the point of the program...

Yes I do.

No you don't.
1:1 being shown by MMR has nothing to do with acceleration curve, it just means 1 count received from the mouse moves 1 pixel on the screen and 7/11 clearly overrides that with x1.5 scaling...
You dont need accefix with win7/8/10 unless the game turns on EPP(and no quake or any other modern game does that). There's no accel with EPP turned off on any mouse slider setting. Accelfix simply alters the chosen EPP-on sensitivity setting to behave the same as it does with EPP being off so that in games like CS1.6(which enable EPP) you get linear mouse movement.
The only bad thing you might get is 2d pixel skipping cause of 7/11 instead of 6/11, just use raw input in every game for it to behave the same as 6/11+EPP-off

You dont need accefix with win7/8/10 unless the game turns on EPP(and no quake or any other modern game does that)

So why did MarkC spend so much effort into it if it's basically useless?

Maybe he plays CS1.6.

read his faq

Why do you need the fix?
If you don't know you need it, then you don't need it!

Some older games, such as Half-Life 1, Counter-Strike 1.x, Quake, Quake 2, Unreal and others, while they are active and running, call a Windows function intending to disable variable mouse acceleration by forcing ALL movement to be accelerated by the same amount (doubled).
On Windows 2000 and earlier, that removed all variable acceleration.
Pointing and aiming in those games was OK, because the mouse response was then linear (all movement was accelerated by the same amount; it was doubled).

In XP, Vista, Windows 7 and Windows 8.x, Microsoft changed how mouse pointer acceleration worked.
Now when those games call the function (asking that all movement be accelerated), Windows enables the mouse 'Enhance pointer precision' feature, which adds mouse acceleration using a varying curve to control the mouse response. (It enables it even if you have it turned off in the Control Panel Mouse settings.)

With 'Enhance pointer precision' enabled, slower mouse movements make the pointer go extra slow and faster mouse movements make the pointer go extra fast. It is not linear and not straightline.

This is annoying, because where you are aiming at depends on how far you move your mouse, and also on how fast you moved the mouse to aim.

So if I went to a lan to play QL, if im using in_mouse 2 all I need is 'Enhance pointer precision' disabled and 500hz? or i dont even have to bother with 'Enhance pointer precision' because I use in_mouse 2 and my mouse will feel the same everywhere?

if you use in_mouse 2 you shouldnt give a fuck about windows settings

Not even dekstop resolution matters? thast good to hear.

and what is the point of the program exactly? MarkC claims that its mousefix-reg-builder can create a reg file to remove acceleration for any position of the slider. I use position 4 instead, and also made my own custom reg file with the builder but I still get red/green lines too.

What is it that you seem to understand that we don't?

left column = counts received from the mouse
right column = cursor movement in pixels

There are a number of things that can cause red/green lines, and not all of them are reasons for concern.

* EPP enabled without the fix
* Pointer speed not set to 6/11 (yes, even when you have built a custom fix for a specific pointer speed)
* Cursor hitting edge of screen
* Games/applications that control the cursor position (eg: games that re-center cursor after each input cycle)
* Crap computer/operating system (cursor takes so long to move after counts are received that MouseMovementRecorder doesn't associate them)

It seems as though MarkC has gone to a lot of effort to explain what the fix actually does and when it is useful. If you haven't already read the readme, I would suggest checking it out, as well as some of the discussion here
http://www.esreality.com/post/1846538/markc-w...ation-fix/

Understand what a mouse fix builder REG file does for you:

Only when 'Enhance pointer precision' (EPP) is ON, you will get 1-to-1.

This might not be of much use, because 1-to-1 has the exact same sensitivity as position 6/11.

So you can't have your cake (have 7/11 for extra mouse speed) and also eat it (have exact 1-to-1) at the same time.

What a mouse fix builder fix CAN DO, in some cases is this:

- Allow 7/11 (or your chosen sensitivity) for normal Windows programs (on the desktop).

- Become enabled while in-game, so that you get exact 1-to-1 and 6/11 while playing a game.

In effect, in some cases, it is like using 7/11 normally, but going into the Control Panel just before you start your game and selecting 6/11 for the duration of the game.

BUT there is a crappy problem: For it to work this way, the game must be one of those games that sets EPP on, and must be allowed to set EPP on.

For Half-Life and CS 1.6, that means NOT using the -noforcemspd or -noforcemparms launch options.
For Half-Life 2 and CS:GO, that means NOT using the -noforcemspd launch option BUT ALSO using the -useforcedmparms launch option.

Of course, far better for those games is to use the newish Raw Input options to get 1-to-1.

So in q3/ql we can forget about this if we use in_mouse 2 is what I understand.

Yes