Sensitivity Information
Tweadle
Join Date: 2005-02-03 Member: 39686Members, NS2 Map Tester
It would be nice if you could know exactly what mouse sensitivity you were using via an in-game "cm per 180degree" turn or something. That way, we can aim to keep our sensitivities the same in all circumstances, be it with a different mouse, a different windows sensitivity or a different computer. We'd also be able to convey to others exactly what conditions we're playing in which is currently difficult and never an exact science.
Not seen it before and I don't know how hard it would be to implement (what with all the factors outside of the game) but I think it would be a really neat and useful feature with no drawbacks.
As a side-note: I hope and presume that mouse acceleration will be off by default!
Not seen it before and I don't know how hard it would be to implement (what with all the factors outside of the game) but I think it would be a really neat and useful feature with no drawbacks.
As a side-note: I hope and presume that mouse acceleration will be off by default!
Comments
(m_yaw is for horizontal movement; replace with m_pitch for vertical movement. Also, if you left your Windows mouse speed setting at the default then the sensitivity in pixels per inch is just the mouse's DPI rating. In fact, I'm not sure if Half-Life uses the Windows mouse speed setting at all; if not, then just use the mouse DPI always. Finally, this is only true for the classes with 90 degree field of view, since sensitivity <a href="http://www.unknownworlds.com/forums/index.php?showtopic=97248" target="_blank">varies</a> with field of view.)
(For this reason, in NS I set my m_yaw and m_pitch to 1/800 = 0.00125. Since I have an 800 DPI mouse, this means my sensitivity variable is expressed in degrees/inch. Sadly, in Source it is not possible to change m_yaw.)
Regarding the suggestion, in order to provide that information directly you'd have to ignore the Windows mouse speed setting and make the user input his mouse DPI. Should be doable; I think Half-Life might already do the former (not sure, I've never changed my mouse speed setting - might also depend on whether the game is run with -noforcemspd). If NS2 also has variations in field of view between classes, this number would again only be valid for one particular field of view, since it is natural for the sensitivity to vary in proportion with the field of view.