Windows xp mouse acceleration registry

If you have never noticed any unwanted mouse acceleration, you do not need to apply this patch. Link to comment Share on other sites More sharing options K Posted December 7, Posted December 7, Thanks DeadEye! WantedDeadeye Posted December 7, Your welcome. GrimReeper Posted December 7, Mouse acceleration means the pointer moves farther if the mouse gets moved faster.

If you've set it to eg. With mouse accel it only moves if you move it slow but or more if moved fast. Premgenius Posted December 7, No problems here and If there was I'd prefer to download it directly from Microsoft. Herby Posted December 7, Nice patch!.. Anyway fact is, is the hard-coded value. The difference is larger though when using anything else than 60Hz on XP or when using a different screen dpi.

These five coordinate pairs, or inflection points which form the acceleration curve are stored in the registry. The first inflection point is always 0, 0. The curve is linearly extrapolated beyond the last inflection point, which is to happen rarely as the physical velocity of the mouse has to be over 40 inches per second.

The inflection points are stored by using fixed-point No worries though, to make a custom curve you don't need to understand how the coordinates are converted. This isn't enough for us, though, as we want complete control over the curve. How to make a customized acceleration curve Down to the point. Use of the registry editor isn't required though. Windows Registry Editor Version 5. From a practical point of view it makes sense to name the file as "WindowsDefault.

A pop-up window will appear and in case asks if you want to data in the file to be written in the registry. The file can be easily viewed in text editor by clicking the file with the right mouse button and selecting 'Edit' in the drop menu. Let's connect the coordinates to make pairs. Because the physical velocity of the pointer on y-axis is plotted against the physical velocity of the mouse on x-axis , the gain factor, in theory, describes how many times faster the pointer moves on the screen than the mouse moves on the pad.

Also in theory, a fixed gain factor of 1 would mean that the pointer and the mouse are moving equally fast. This doesn't however mean that one virtual count sent by the mouse would equal to pointer movement of one virtual unit. How big of a gain factor that results in the aforementioned scenario is important when making a custom curve. It can be calculated by using the formulas addressed in the 3. In other words when using enhanced pointer precision, higher refresh rate always results in faster pointer movement.

This is not desirable. Thus, all 4 gain factors should be scaled accordingly if using anything above 60Hz. Below are the resulting virtual speed multipliers and percentual speeds at 60Hz. Here, a gain factor of 5. There are no variables in the formula for the physical velocity of the mouse, so x-coordinates don't need to be changed when making scaling due to refresh rate alteration.

The figures in the chart are only to make the customization easier and to give a quick overlook of the curve. Windows 7 users don't need to make any manual scaling because - as mentioned in the 3. To XP and Vista users I recommend making the scaling to the used refresh rate if it's not 60 before further modifying the curve.

To make things easier, here are the registry files where the default MS curve is already scaled for most common refresh rates. So when using enhanced pointer precision in Win 7, the higher the screen resolution or DPI , the faster the pointer moves. This is desirable behaviour.

Below are the resulting virtual speed multipliers and percentual speeds at 96DPI. As an example, here we'll modify the y-coordinate of the 2. In other words we are modifying the velocity at which the pointer physically moves in theory at least when the mouse is physically moved between 0 and 0. The default decimal value for the coordinate is 1. Tips on designing your own accel curve There is no curve that will perfectly fit different devices, settings and preferences.

Overall I think it's safe to say that the default curve is a bit aggressive. The gain factor at the last inflection point is a wild As a very general rule of thumb, the first three points should approximately be on the same line and equally distant from each other in the graph representing the curve.

The farther the third point is placed on the x-axis, the longer the "normal" speed is preserved when the mouse is accelerated and the later the pointer starts to visibly accelerate.

Note that the mouse DPI is directly proportional to how fast the pointer moves on the screen. So the DPI mouse is twice as fast. The higher the mouse DPI, the earlier the pointer moves 1 count and the harder it is to precisely manipulate and the greater the need for subpixelation. On the other hand, the smaller the DPI, the less efficient general navigation is and the greater the need for actual pointer acceleration. It could be concluded that there's a limit where higher DPI stops being useful.

This is because the higher the update rate, the faster the counts get sent. If a mouse sent a package of 4 counts at Hz, at Hz it would instead send two packets with 2 counts. Because the enhanced pointer precision uses a hard-coded number, a higher mouse update rate results in less calculated physical velocity even if in reality it was the same.

I don't recommend using Hz at all because it is unstable. The files contain comment lines which should prove helpful.

If you would prefer a "blank canvas" type of start, you can scale all the inflection points to have exactly the same gain factor and work your way from there.

Ending words I would like to thank MarkC for his work on decoding the 'enhanced pointer precision' feature. I couldn't have written this tutorial without his efforts. In an optimal case, after getting your custom accel curve done the pointer movement feels more natural compared to before. So natural in fact that you don't feel anything special in the pointer behaviour.

By now I can tell it is an addicting feeling. The great thing about having a customized 'enhanced pointer precision' is that you can have the same accel in all games that support Win32 mouse input. I don't want to take any credit from this tutorial because it was simply gathering bits and pieces from the net. Only thing I found out myself was how easy the numbers are to convert with the Fixed Point Converter. Sadly I'm not yet skilled enough to write a tool where the curve could be graphically adjusted and where the whole process was done automatically.

Zest vs Trap. Solar vs GuMiho. Dark vs Solar. Rogue vs ByuN. Dream vs Rogue. Maru vs Classic. Cure vs Maru. Alpha X AfreecaTV YouTube. Liquipedia Discussion. Westballz Link to comment Share on other sites More sharing options Posted February 20, I have Windows XP 64 bit. BlueMe Posted February 20, If nothing else works, try this :.

Posted February 21, Create an account or sign in to comment You need to be a member in order to leave a comment Create an account Sign up for a new account in our community.

Register a new account. Sign in Already have an account? Sign In Now. Go to topic listing. Recently Browsing 0 members No registered users viewing this page.