Sens + Fov
•
19 Oct 2007, 12:55
•
Journals
How much do you need to turn 360 degrees and what you use
I need 30 cm to make 360 degrees :D using logitech mx510
Fov 120
I need 30 cm to make 360 degrees :D using logitech mx510
Fov 120
Fov 105 and MX518.
Whole Qpad Lowsens (40cm) for 270°
Razer Deathadder.
windowssens: 5/11
1800 DPI
sens 1.2
pitch 0.016
razer driver sens: 6/10
accel enabled.
16cm/360°
Intelli 1.1 SS, 400DPI
500HZ
Win 6/11
ingame: 6.00
m_pitch 0.022
Edit: accel off :-)
but about 15 for 360°
fov 90
windows 6/11
ingamesens 2.66
m_pitch/yaw on default
800dpi
mx518
NUKE-Z Z8
ingame 7.00
saitek pm12a
no pad
fov 110
pitch 0.015
fov 110
mx518
fov 90
fov 120
DeathAdder
aber 44 kommt der Sache näher!
50cm/360°
razer pro klick, 400DPI
500HZ
Win default
ingame: 2.00
m_pitch 0.015001
QcK+
MX518
100FOV
1..4 sens
Linux acceleration off
Steelseries gaming glove
It helps me play a lot longer too, less strain/friction on the hand when moving around all the time.
I like it
38cm/225degrees
Mx518, 400 dpi
500 hz
win default
ingame 1.95
default pitch
mx518
I have accelfix.exe set to "disabled"
400 dpi
6/11 windows
O/S implementation
no accel in setpoint
Why you need way more cm for 360? Only thing I can think of is the difference in fps and displayrefresh and r_mode combination.
I have 120 HZ / 125 FPS / R_mode 6
30 cm/360°
logitech G5, 400DPI
1000HZ
QcK+
Win 5/11
ingame: 4.88(/3.88)
m_pitch 0.016
accel disabled
12cm/360°
G5, x2000dpi y1000dpi
1000hz
win default
ingame 3.5
pitch 0.018
36-38 cm for 360 degrees
DeathAdder, 450 DPI, 500 Hz, Razer drivers sens on maximum, system sens on 10 (registry value), sens ingame on 2.6, m_pitch on 0.017
sens default
~30cm/360
mx 310
dpi dont know
hz dont know
pitch dont know
~90cm /360°
deathadder 450dpi 500hz
win def
ingame 0.6
pitch 0.016
no accel
ingame sens: 1,5
80cms /360°
40cm / 360°
ingame sens : 1.60
windows sens 6/10
pitch : 0.01501
no accel :)
28cm/360°
Razer DeathAdder, 1800DPI
500HZ
Win 4/11
Razer Driversens on full
ingame: 2.00
m_pitch 0.01501
Accel off
MX518 - 800dpi
250Hz
Entire widh of a QcK+ for a 360°
Ingame sens 3.00
Setpoint 4/11, using setpoint implementation
m_pitch 0.0165
acceleration off (I hope)
G5 - 400dpi
500Hz
Qpad UC - all pad for 180 turn
sens : 1.75 - no accel
windows sens: 5/11 using setpoint
m_pitch 0.01501
m_pitch : 0.019
fov: 100 or 105 if im tired
after change do a restart. (dont have that prob myself tbh)
can't really feel any difference after the reboot, but ok :D
What is the difference btw?
mx518/qpad glidez/qpad ct large
800dpi
1000hz
41cm/360(using setpoint)
no accel
pitch 0.01501/default
mx518/icemat
400dpi
500hz
63/360
no accel
pitch 0.0155/0.02
mx500 400 DPI
500hz
44cm/360
no accel
pitch -0.022
ingame 1.55
r_mode 4