- ReaverI'm using:
1800 DPI
1000 Hz
Sensitivity: 10
Axe X: 10
Axe Y: 10
Windows Pointer:8/11
Acceleration: Off
I also heard that anything above 6/11 is innacurate,is it true?
Actually everything BUT 6:11 for Windows pointer is inaccurate, causes skipping. Like this:
Read more on www.overclock.net/t/17...tion-guide
Mouse input methods for UrbanTerror on Windows
WM_MOUSEMOVE
This is used by the option \in_mouse -1. WM_MOUSEMOVE is limited by the screen resolution. This means that if you move the mouse slightly — but not enough to cause the pointer to move to the next pixel — then no WM_MOUSEMOVE message is generated. So, using this method to read mouse movement negates the benefits of high-definition input.
WM_MOUSEMOVE also applies the Windows pointer acceleration (also known as ballistics) to the raw mouse data (see below on removing mouse acceleration).
DirectInput
This is used by the option \in_mouse 1. DirectInput creates a second thread to read WM_INPUT data, and using the DirectInput APIs will add more overhead (thus increase latency) than simply reading WM_INPUT directly. DirectInput is mainly useful for reading data from DirectInput joysticks.
DirectInput also enables you to directly bind MOUSE4 and MOUSE5 buttons in-game.
WM_INPUT (aka Raw Input)
This option is only available on builds based on 'recent' ioQuake3 sources, such as Optimized ioUrT build and dmaHD, with Raw Input (like Quake Live).
This is used by the option \in_mouse 1 with conjunction of \in_rawmouse 1. WM_INPUT messages are read directly from the Human Interface Device (HID) stack and reflect high-definition results and provides lowest possible input latency.
Using WM_INPUT also allow you to directly bind MOUSE4 and MOUSE5 buttons in-game.
Remove mouse acceleration on Windows XP and Vista
To remove mouse acceleration completely on XP, you can use the good old CPL mouse-fix, or try Cheese mouse-fix. Both can be downloaded here.
Remove mouse acceleration on Windows 7
To remove mouse acceleration completely on Windows 7, you can use MarkC's Mouse acceleration fix.
No Drift-Control aka prediction
You should try the NDC firmware provided by Razer (make sure you uses the correct firmware for the DeathAdder version you have) and uses highest possible DPI settings. NDC seems a good choice for gaming, especially if you are low (in game) sensitivity player.
If you are high sensitivity player, you could also opt for lowering DPI setting.
Test for mouse hardware positive/negative acceleration:
This test is not necessary, but you could do it if you are curious.
Enable DirectInput:
\in_mouse 1
(restart client or do \in_Restart)
The test:
1) Start UrbanTerror WITH DirectInput Enabled.
2) Set a low sensitivity (lower than your normal sensitivity).
3) Aim your crosshair at a specific point like a corner or something that's easily recognizable.
4) Slowly move your mouse all the way across your mouse pad to the edge.
5) Move the mouse *fast* (as fast as you can) back to the starting point.
Now one of three situations have occurred:
1) The crosshair has overshot the point you picked out. This is positive acceleration
2) The crosshair has undershot the point you picked out. This is negative acceleration.
3) The crosshair lands spot on (with human error in mind). No acceleration is present.
As easy as this, and repeat the test 3-5 times to make sure it's a positive result.
For more information about Razer products, go to http://razerblueprints.net.
Mouse input related CVARs for UrbanTerror
Code:
set cl_freelook "1" // mouse look [bool|def=1] set cl_mouseAccel "0" // mouse acceleration [bool|def=0] set cl_mouseAccelStyle "0" // mouse accel style set cl_mouseAccelOffset "5" // mouse accel offset set in_mouse "1" // mouse input api: [1=direct input(no neg.accel),-1=desktop cursor|def=1] set in_rawmouse "1" // HD mouse latency: [1=low,0=normal] set cl_platformSensitivity "1.0" // Indicates the mouse input scaling [float|def=1] set m_filter "0" // smooth mouse [bool] set sensitivity // mouse sensitivity seta m_pitch "0.022" // mouse sensitivity vertical ratio seta m_yaw "0.022" // mouse sensitivity horizontal ratio /// <negative m_pitch value> = invert mouse
Code:
set zoomSensitivity "1.95" set cl_zoomSensitivityFOVthreshold "90"
PS:
I uses DeathAdder 1800 (1.39NDC firmware) on Goliathus Control
1800 DPI, 500Hz, Driver sens: 10(10/10), Windows sens: 6/11, No accel (Cheese mousefix applied for 75Hz display)
In game sens: 0.625/110FOV & 0.585/90FOV (Raw Input)
