ET low DPI only?
•
14 Jul 2011, 14:31
•
Journals
Yesterday I was speccing a match on ETTV and a discussion started about DPI. One guy said only 400 to 800 DPI is good for ET.
Can anyone explain me exactly why because this guy couldn't make it clear for me.
The higher your DPI the more precise your mouse is(The more Dots it tracks per Inch). In my logitech Setpoint driver I can also change 'speed' and 'acceleration'. Everybody always told me turn acceleration off, this also seems pretty logic to me. So Now I have 'speed' in the logitech driver left and '/sensetivity' ingame those 2 can still make me a high or low sens player. No matter how high or low my DPI is.
Also we had a little discussion about what is better. To make it short you should take what feels good for you. High sens overall gives you better movement(or makes it easier to move faster) and low sens makes it easier to aim exact where you want.
Correct me on anything if I'm wrong.
Can anyone explain me exactly why because this guy couldn't make it clear for me.
The higher your DPI the more precise your mouse is(The more Dots it tracks per Inch). In my logitech Setpoint driver I can also change 'speed' and 'acceleration'. Everybody always told me turn acceleration off, this also seems pretty logic to me. So Now I have 'speed' in the logitech driver left and '/sensetivity' ingame those 2 can still make me a high or low sens player. No matter how high or low my DPI is.
Also we had a little discussion about what is better. To make it short you should take what feels good for you. High sens overall gives you better movement(or makes it easier to move faster) and low sens makes it easier to aim exact where you want.
Correct me on anything if I'm wrong.
no negative accel
Also some DPI values may cause some sort of mouse acceleration, but I don't know about the details.
... which you'll always want at the 6th notch.
Basically: The higher your screen resolution, the higher your dpi have to be, and the higher your sens, the higher your dpi have to be. So high sens + high screen resolution = megha dpi needed!
However, as most players use a quite low sensitivity and don't play at really high resolutions, 400 dpi are enough most of the times.
That's just the stuff I remember from some comments and journals by h8m3 and Mztik, could be wrong afterall!
Edit: Here's the Excel file http://www.ba.onlinestereo.org/Tools/DPI.xls
thanks to siril
use this instead !
I guess this was it, pretty much. :D
At least this is how I heard it from a friend of mine, and I also recall reading up on the subject somewhere. There's still a possibility that I'm completely wrong, and if that's the case, then feel free to correct me.
However, if your dpi aren't high enough for your resolution, you simply skip pixels and can't hit every pixel on the screen. Simple as that.
Well, no idea how things are calculated but it works a little like this I guess:
400 dpi -> 400 pixel -> you can hit every single pixel
400 dpi -> 800 pixel -> you can only hit every second pixel
'basically' :-P
if i understood u right
I just gave this 400/800 as a really basic example.
Maybe I still have the dpi.xls file on my other harddrive, will check for it tomorrow night.
Or maybe h8m3 manages to find this journal (is he even still around?)
found it :)
oh and btw, what dpi does IME 3.0 have? :x google just gives me alot of diff values :x
Edit: IME 3.0 uses 400 dpi (the new and the old version)
However, I'm quite certain there was *something* related to negative acceleration that made it impractical to use high DPIs in ET. Of course that is if you don't use RInput.
büdde :)
Ich kann momentan nur groß reden und theoretischen Blödsinn von mir geben :->>
if you imagine the center of your screen to be this o: [-o-]
the larger your resolution the further it is from the edges of the screen [--o--]
so the further your cursor can move before it skips off the edge of the screen, which is basically what causes neg. accel, as the extra gets carried over onto the next update loop
B = ( 360 * tan[ F/2 ] ) / ( pi * W * M )
B = sensitivity (cvar)
F = fov
W = screen res width
M = m_yaw
R = ( pi * W ) / ( I * tan[ F / 2 ] )
where
W = screen resolution width
I = real sensitivity (distance per 360 turn)
F = horizontal fov
R = mouse resolution required
convert your sens to inches if you want R in units of dpi.
http://www.ba.onlinestereo.org/Tools/DPI.xls
rawinput + slac
does slac detect rawinput as a external program messing with et and therefore flaging it as a cheat ????