st

1br

not sure how to reply to that comment.

I like this post.

From Lorfa's cvar guide:

m_cpi "0"

Description:

This changes the units used by sensitivity and the cl_MouseAccel formula to more familiar ones.

There are a couple requirements:

1. That m_cpi is set to the CPI value of the mouse.

Note: In order to set m_cpi correctly, it should take into account any driver-level sensitivity setting that affects the game. For example, you have a 1000cpi mouse with a driver setting of x0.6 - you would set m_cpi to 600, not 1000. Many driver-level settings do not affect the game when in_mouse is 2. If not sure a quick test should clear things up.

2. That m_yaw is set to 0.022

After that, sensitivity changes from a dimensionless multiplier, to degrees per centimeter, and cl_MouseAccelOffset changes from counts per millisecond to centimeters per second.

In order to convert your existing sens and accel settings to the new scheme with m_cpi, there are some existing calculators out there that will do the conversion. If you want to do this manually, you can use the following formula for conversion from old to new.

new_sens = old_sens * (old_yaw * m_cpi / 2.54)
new_sensCap = old_sensCap * (old_yaw * m_cpi / 2.54)
new_accel = old_accel * (old_yaw * (m_cpi/2.54)^2 ) / 1000
new_pitch = old_pitch * (0.022 / old_yaw)
new_yaw = 0.022

One nice feature of this is that when changing the mouse CPI, the only value you have to change is m_cpi. So if you were using a 400 CPI mouse and had all your m_cpi values set, then switched to a mouse with 800 CPI, you wouldn't have to adjust your sensitivity any. Just set m_cpi to 800 and you're all done.

Recommendation:

Personal preference. I have however found that a lot of mice do not seem to have the exact CPI value stated which throws off the calculations when trying to convert from m_cpi 0 to m_cpi >0.

who?

Ok I understand now I had gotten confused because of a comment by Yakumo. m_cpi works the way I though it did.

which comment would that be?

I didn't say you were wrong. It just confused me. The comment about accel not converting and being dpi dependent. I just didn't realize it had no relevance to m_cpi.

I didn't say you did, I just wondered :)

if you ever need it -
newAccel=oldAccel*((oldCPI/newCPI)^2)

Additional source: http://www.quakelive.com/forum/showthread.php?15458-New-Mouse-Sensitivty-and-Mouse-Accel-Features