Professional Documents
Culture Documents
and calculate : threshold threshold_factor, round up and use that value instea
d
(e.g. Windows 2000 Low accel has threshold=7, 70.5 = 3.5, round up to 4 and ent
er 4)
- When next asked for 'Pointer speed scaling ... when the mouse is faster than .
..', accept the automatic values.
(e.g. Accept 0.5 and then accept 1, which correspond to 0.252 and 0.254)
MOUSE MOVEMENTS THAT ARE DIAGONAL OR AT AN ANGLE
For the default fix builder fixes, acceleration will most closely match your old
version of
Windows for movements that are mainly horizontal or mainly vertical.
If your mouse movements are often diagonal or at an angle, then the thresholds m
ay need to be
increased by 10% to 30% before mouse response will be similar.
This is because of differences in how Windows 10/8.x/7/Vista/XP and Windows 2000
/98/95 compare the
mouse speed to the thresholds.
In Windows 2000/98/95, each movement axis (X/Y) is compared separately, and has
its own
pointer-speed factor applied.
If X_Movement > threshold then use higher speed-factor for X; otherwise use lowe
r speed-factor for X.
If Y_Movement > threshold then use higher speed-factor for Y; otherwise use lowe
r speed-factor for Y.
In Windows 10/8.x/7/Vista/XP, the X axis and Y axis movements are combined, and
both have the same
pointer-speed factor applied.
(Very approximately)
If X_Movement + Y_Movement/2 >= threshold+1 then use higher speed-factor; otherw
ise use lower speed-factor.
Examples for a threshold of 7:
For Windows 2000/98/95:
X
Y
X factor
Y factor
6
3
1.0
1.0
6
4
1.0
1.0
7
1
1.0
1.0
7
2
1.0
1.0
8
1
2.0
1.0
8
2
2.0
1.0
10
4
2.0
1.0
For Windows 10/8.x/7/Vista/XP:
X
Y
X factor
Y factor
6
3
1.0
1.0
6
4
2.0
2.0
7
1
1.0
1.0
7
2
2.0
2.0
8
1
2.0
2.0
8
2
2.0
2.0
10
4
2.0
2.0
(Note that for these at-an-angle movements, Windows 10/8.x/7/Vista/XP generally
uses higher speed-factors.)
If the threshold is increased to 8, then examples for Windows 10/8.x/7/Vista/XP:
X
Y
X factor
Y factor
6
3
1.0
1.0
6
4
1.0
1.0
7
1
1.0
1.0
7
2
1.0
1.0
8
1
1.0
1.0
8
2
2.0
2.0
10
4
2.0
2.0
(Note that for these at-an-angle movements, the speed-factors used are perhaps n
ow closer to Windows 2000/98/95.)
CROSSING A THRESHOLD, AKA TRANSITION STEEPENING
If you sweep your mouse from slow to faster, from 5 counts-per-update to 10 coun
ts-per-update,
you might cause these mouse counts:
+5 +6 +7 +8 +9 +10
On Windows 2000, Low acceleration, mouse speeds greater than 7 cause doubled poi
nter movement,
so the pointer movements would be:
+5 +6 +7 +16 +18 +20
On Windows 10/8.x/7/Vista/XP with a W2K_Low mouse fix, the pointer movements wou
ld be:
+5 +6 +7 +12 +18 +20
As the mouse speed transitions over the threshold, the first movement greater th
an the threshold isn't DOUBLED.
The speed-factor used is an average of the previous zone (1) and the current zone
(2), or 1.5. 81.5 = 12.
This is normal and expected and GOOD! (Trust me!)
Don't worry about it.
REVERSING DIRECTION LEFT/RIGHT OR UP/DOWN
If you move the mouse in one direction, slow down, stop, and reverse the mouse,
you might cause these mouse movements:
+3 +2 +1 -1 -2 -3
On Windows 2000/98/95, the pointer movements would be:
+3 +2 +1 -1 -2 -3
On Windows 10/8.x/7/Vista/XP with a threshold acceleration mouse fix, the pointe
r movements will sometimes be:
+3 +2 +1 +0 -2 -3
When the mouse reverses direction, a single pointer-pixel will sometimes be miss
ed or discarded.
This sometimes happens, and can't be fixed.
Live with it; it's only a single pixel!