Mouse DPI & sensitivity?!


(edxot) #41

hi Azztec

it is m_pitch that you must change, instead of m_yaw

about sensitivity, i rather bind 4 keys to change instantly the sensivity ingame.
1st - the lowest i can play with (long distance aim)
4th - the highest i can play with (short distance aim)
then 2nd and 3rd, chosen to fit the gap.

most of the time, when playing outside, i choose the 2nd. and inside i choose the 3rd. leaving the 1st and 4th to some special ocasions.

some people (mostly good shooters) dont realize how important it is to have an high sensitivy. that is the reason they will never use a rocket launcher/ obliterator properly. and most of the times get stuck in mining lasers or bridges. because the speed is more important than aim, for those situations.

however there are some drawbacks. before you get used to it, you will be caught using the wrong sensitivity, leaving you aimless in some situations.


(Dthy) #42

You can bind one key to toggle sensitivity. For example I have:

bind "mouse5" "toggle sensitivity 6.5 3.5"

You can add as many variables as you want, and it will go in order. Any more than 2 is just pointless imo. Personally, I find asking about different peoples sensitivity is pointless, as everyone aims differently. Just find a sensitivity which you can control well enough in all (if not most) situations.

As already been stated, m_pitch (and m_yaw, but not as much) can help aim, the settings I use for them are:

seta m_yaw "0.0195" ; seta m_pitch "0.013"

I found the best way to get used to a sensitivity is first playing some offline bot matches. After you find a sensitivity you can cope with, take it online on public (try to find a server where you have the smallest lag) then you can fine tweak it from there. Samurai also gave me some good tips and a “Sensitivity guide” (even though it’s for ET, it’s still applies to pretty much any FPS) which helped me, I can send it to you if you want, just PM me.


(r3fleX) #43

I usually stop myself posting in most threads, but i feel the need to contribute before this guy starts taking on some of the rediculous advice posted in this thread.

Setting different sensitivity toggles for different ranges is just purely retarded. You should find a sensitivity that is low enough to aim accurately (be in control of) yet still be able to turn without getting caught out by opponents.

The whole point is to stick with 1 sensitivity and build up “muscle memory” whereby your muscles remember how far the mouse must move instinctively to the target. If you keep changing sensitivities you will never build up this muscle memory as it will change far too often (very high to very low sense) so your muscles will never find a preferred sense.

In terms of mouse driver settings generally if you are a low sensitivity player i’d advise using around 400dpi/500-1000hz polling rate and then alter your in game sensitivty to what you wish. For high sense players i don’t really know whats best… i guess from the minute movements you would require much higher dpi for that extra bit of precision and highest polling rate.


(JinxterX) #44

Arrogant as usual, ignorant child, learn to spell.


(Rex) #45

Just checked the forum again and discovered this post, ohhh dear… :rolleyes:

Why should good shooters realise that high sensitivity is so important, if 95% of the good players play with low or mid sense?

[QUOTE=edxot;400642]that is the reason they will never use a rocket launcher/ obliterator properly.[/QUOTE] Please what? The best rockets never played on high sense. Even if I try, I don’t need a high sense and can also play on my low one properly.

Stuck in mining laser or bridges? Glitches? Speed more important than aim? In Need for Speed or what?
This sentence makes absolutely no sense at all.

Well takes some time to find the right one. But sometimes you should just try out different settings. Personally I used to play with a very high sense for like 3 years in the past until some of my mates convinced me to try out low sense. So I tried it and it turned out that I played 3 years with the wrong sensitivity. :tongue:


(Azztec) #46

Thanks in advance! :smiley:

If I get this right then I also shouldn’t switch dpi on the fly?

Okey, polling rate between 500-1000hz.
This site (https://wiki.archlinux.org/index.php/Mouse_Polling_Rate) tells me the delay time, now I need to make another devestating choice. My screen has a delay of 5ms, so (if I’m correct) it’s no use of going for the 1000 Hz? This means I still got to choose between 125 or 500 Hz. The higher the better, but 500 Hz still gives the Deathadder 2 ms delay and I have got a 5ms delay on my screen? Should I opt for the 125 Hz which gives me a delay of 8ms?

And even though my Deathadder supports 3500 dpi, I should go for the 450 dpi option?


(Azztec) #47

[QUOTE=edxot;400642] it is m_pitch that you must change, instead of m_yaw

about sensitivity, i rather bind 4 keys to change instantly the sensivity ingame.
1st - the lowest i can play with (long distance aim)
4th - the highest i can play with (short distance aim)
then 2nd and 3rd, chosen to fit the gap.[/QUOTE]

Don’t you find it hard switching sensitivity just before you decide to shoot?

[QUOTE=Dthwsh;400643]You can bind one key to toggle sensitivity. For example I have:

bind "mouse5" "toggle sensitivity 6.5 3.5"

You can add as many variables as you want, and it will go in order. Any more than 2 is just pointless imo. Personally, I find asking about different peoples sensitivity is pointless, as everyone aims differently. Just find a sensitivity which you can control well enough in all (if not most) situations.

As already been stated, m_pitch (and m_yaw, but not as much) can help aim, the settings I use for them are:

seta m_yaw "0.0195" ; seta m_pitch "0.013"

[/QUOTE]

What about those values (m_pitch & m_yaw) in QW, would it be usefull for me to do that?
I also read these settings would can give different results in different games, so these values would be good for playing QW, but might be completely useless if I plan another game?


(Dthy) #48

Changing the m_pitch & m_yaw values in game just means you won’t have to use any software your mouse came with to change the X and Y sensitivities. I’ve only changed these values in QW, not in any other game. From personal experience, having a lower m_pitch makes tracking heads easier once you’re aiming at head level, of course, you’ll have to move your mouse more up and down since the Y value would be lower, but it just takes getting used to.


(edxot) #49

[QUOTE=r3fleX;400656]I usually stop myself posting in most threads, but i feel the need to contribute before this guy starts taking on some of the rediculous advice posted in this thread.

Setting different sensitivity toggles for different ranges is just purely retarded. You should find a sensitivity that is low enough to aim accurately (be in control of) yet still be able to turn without getting caught out by opponents.

The whole point is to stick with 1 sensitivity and build up “muscle memory” whereby your muscles remember how far the mouse must move instinctively to the target. If you keep changing sensitivities you will never build up this muscle memory as it will change far too often (very high to very low sense) so your muscles will never find a preferred sense.
[/QUOTE]

thank god i am not so short brained.

your theory fails, and fails and fails, etc …

after it fails, you go crying to promode: “this game dont need vehicle whores or radar” (depending if you got killed by titan/anansi or grenade).

just because you can seat outside enemy spawn killing all foot noobs in other team, leaving objective defendless (place where you wont find enemy noobs) does not make you owner of thruth. you are just another type of noob. and i confess something to you. its the worst kind of noob. because it’s the quitting type, and server gets empty.


(Rex) #50

:smiley: :smiley: Ohhh this made my day :smiley:

[QUOTE=edxot;400809]your theory fails, and fails and fails, etc …

after it fails, you go crying to promode: “this game dont need vehicle whores or radar” (depending if you got killed by titan/anansi or grenade).

just because you can seat outside enemy spawn killing all foot noobs in other team, leaving objective defendless (place where you wont find enemy noobs) does not make you owner of thruth. you are just another type of noob. and i confess something to you. its the worst kind of noob. because it’s the quitting type, and server gets empty.[/QUOTE]

HAHAHHA :smiley: Samurai I always knew it, noob! Server gets empty, because of missing radars!

Holly ****, seriously edxot, you really want to steal the retard of the month award from the cookie cheater? :smiley:


(Azztec) #51

Wow, comon guys, no need to start bitching here. We all have different oppinions, what in the end works out for single one of us. There is no such thing as ‘This is the only right way to do it’.
I just wanted to know how other people use their mouse and how they feel comfortable playing with it. I appreciate everyone’s oppinion, but again, there is no ‘right way’.


(Dthy) #52

Where’s Kleppy with is drama button when you need him?!


(edxot) #53

they troll in terror


(Ashog) #54

already around the corner…I canz smell him! :smiley:


(r3fleX) #55

[QUOTE=Azztec;400703]
If I get this right then I also shouldn’t switch dpi on the fly?[/QUOTE]

Well its entirely up to you, personally i never switch dpi/sensitivity at all, i stick to one sensitivity that i am used to and it works for the games i play. I admit the only useful time to switch sensitivity in QW could be when you are switching between vehicle use to infantry play for example… you have low sensitivity for infantry aiming, but once in a tank a higher sensitivity for turning rapidly is useful. Here pixel precise aiming isn’t required as the splash damage from the weapon means you just need to aim close to the target.

As i tend to avoid playing a vehicle role as i don’t enjoy using them, or i play games where there are no vehicles (CS) i’ve never needed to toggle the senstivity for this use.

Test them out offline, i find when you use 125hz it feels heavier and delayed (which makes sense :tongue:) and therefore i use 1000hz as its feels much lighter and responsive to my mouse movements, which is what i prefer.

Well i’d say this is more dependant on the game you play, as i also have a DA and had this dilemma. In QW however i find i can play with any dpi and there is little difference to my performance if i alter in game sensitivity to keep them the same. But since i now play CS:GO i found it pretty hard to keep a steady precise aim with high dpi but as soon as i reduced it to 450dpi aiming becomes alot more manageable and if you play often enough you can build up the “muscle memory” which i keep stressing in pretty much every post.

If you are looking for some further advice a good basis to start from is by reading Raziels Aiming Guide for RTCW, and also do some research for information and just make logical decisions of how to setup (take into account if the info is outdated etc).

EG.n0thing’s CS1.6 Setup Video
RELOAd’s Aiming Intel Article

There are many more useful articles like these, but thats where you have to go out and find them yourself :wink:

Generally find your personal setup and style, stick to it (and not adjust your configuration every time you loose) and improve it by practicing alot.

Have fun !

I look forward to your logical explanation as to how it fails in response to all the “advice” i just posted, please enlighten me.


(edxot) #56

i still remember the trouble i got when trying to teach you how prediction worked.

and that, was easy stuff compared to this.

in fact, i was talking to Azztec, not to you. i also get tired of talking to you, and getting trolled by your girlfriend.

so, this time, you will have to guess some explanation.


(.Chris.) #57

In other words, you aint got ****.


(Ashog) #58

i have recently tried to swithc back from 4500 dpi to 800 as suggested. surprisingly felt better, smoother and more responsive.


(Kl3ppy) #59

what what? drama? no, this aint drama, its just stupidity :tongue:

oh, not the OP, just the guy who says samu fails :smiley:


(Breo) #60

:frowning: <- steal :smiley: