http://www.ncts.at/files/sens_accel_calculation.txt

0.625 is your value

Thanks.

It kinda of feels like the accel is kicking in sooner than before. Do I need to change the cl_mouseacceloffset aswell? This is what I was using originally sensitivity 4.7, cl_mouseaccel 2.5, cl_mouseacceloffset 5, and cl_mouseaccelpower 1.

accelPower 1 is silly at any accel value > 0 because it just means base sens + 1.

So if you have sens 4.7, it means that your sens is 5.7.

Your accel is effectively 0, and I'm not surprised since if it was 2.5 at 400 cpi it would be so high as to be practically unplayable.

Neither offset or cl_mouseaccel >0 at any value would have an effect with accelpower is 1.

Let me explain, the accel formula is as follows:

Sens + [(Accel(Velocity - Offset)) ^ (accelpower -1)]

If accelpower is set to 1, then (accelpower -1) evaluates to 0.

So you have |x|^0 which is always 1.

What you probably did was take sens 4.7, and cut it in half (2.35) since you changed from 400 to 800 cpi.

However since you were using accelpower 1 (and an accel >0), your sens was made 5.7 in the actual game.

When you changed to 800 cpi, and used sens 2.35 with accelpower 1 (and an accel > 0) your sens was made 3.35 in the actual game.

The sens you were actually looking for at 800 cpi was half of 5.7 which is 2.85. Instead you're at 3.35 which is slightly more sensitive.

Not only that but higher cpi does _feel_ as if it accelerates faster (it does in terms of counts, but not in terms of how it interprets mouse motion, if anything it interprets the motion more smoothly).

What you are experiencing coincides exactly with this data.

In conclusion I recommend these settings to keep things simple and keep the sens the same as what you were familiar with at 400 cpi:

sensitivity "2.85"
cl_mouseaccel "0" (default)
cl_mouseAccelOffset "0" (default)
cl_mouseAccelPower "2" (default)