This is imo totally irrelevant as this will be fu** up your muscle memory. Some people suggest to use a different value for m_pitch and m_yaw depending on your resolution ratio (4:3, 16:9 etc.). Default is 0.022, I suggest something between 0.008 and 0.015. However if you have mouse acceleration, you may want to decrease x. If you left \cl_mouseAccel equal to 0, then there is no point modifying these parameters, just adjust the sensivity at your convenience. \m_pitch x (post-acceleration vertical sensitivity)īasically, x is going to be a coefficient multiplying the horizontal and vertical sensitivities for m_yaw and m_pitch respectively (if x equals 0 for m_yaw, and you will only be able to move your cursor vertically). \m_yaw x (post-acceleration horizontal sensitivity)
But -0.015 is large enough to avoid that, and small enough to prevent weird accelerations you may experience in Quake 3. If you decrease this acceleration too much, what happens is that your cursor will end up moving in the opposite direction than your hand. However, if you experience (like me) for some reason strong accelerations when you move suddenly your mouse, for instance when you want to rocket jump, and or when you want to reach an enemy at the corner of your screen, then I suggest you to set x equal to a negative value. It is obviously your mouse sensitivity, replace x by what you want. I highly recommend to use 1, but some people prefer -1, so pick the one you prefer. There was a superfulous CTF mode bundled into the original package, but it was clearly an afterthought. 1 corresponds to di/raw mouse, while -1 is win32 mouse. Quake 3 Arena did excellent deathmatch in its day, but as far as the online crowd is concerned, team-based action is where it’s at. \in_mouse x where x may be equal to either 1 or -1. However, I struggled a lot against Quake 3 to find a satisfying configuration. Having a good mouse configuration is essential in any fps game.
0 kommentar(er)
