Well, you sound like you've tried a lot of things, that's good.

I basically just pick a number and set it.

Recently I felt like trying out accel, as I never gave it a good shot.

How I did it? I just picked a number that sounded reasonable, and within my 'sensitivity' limits.
Same for accel.

I wanted a medium sensitivity low accel(from high sens no accel).

I just picked a number between low and high (between 6.2 and half of that) and it worked.

There's no good reason to keep changing sens endlessly, and it doesnt have to be a precise number.

Set some goals, do you want high mid or low sens?

Just pick a number and stick with it.

i always had one major consideration with my sensitivity picking, that consideration = ability to move comfortably. the other stuff comes after that for me.

It depends on a lot of things - how you hold the mouse, the DPI of your mouse, etc... If you're sporting 3000 DPI (and actually running at 3000 DPI), even the exact same values in cooller's config will give you a different feel. What kind of mouse do you have, and how do you generally hold it?

I surely agree with your comment. Of course acorrding to mouse,mouseware use or not and etc.. there's not one value only taken

I use logitech g9 mouse and logitech mouseware. dpi is 1600.
In mouseware sensitivity 6 and accel 0.

In q3, my sensitivity 1.255 / accel 0 / m_yaw,pitch 0.022
when I horizontaly turn 360 degree, mouse is moved by 20cm.(experimented by 20cm width mousepad)

The point of accel was to make it so you can make minute movements and get pixel accuracy, but not be completely gimped when you need to turn around quickly. For someone who palms the mouse (and generally does most of the mouse movement with the elbow and wrist), this is a good idea. However, as high sens, you most likely do your movements with your fingers/wrist, and you rely on making smaller movements. Controlling accel in that situation, without using extremely small levels of accel, is next to useless.

If you're going to incorporate accel into your config, you'll probably want to drop down to 400dpi, as it would be a pain to be using extremely small sens values at 1600. If you're dead set on staying with 1600dpi, then you'll just have to play around with values quite a bit. Watch your demos and see how your flicks are responding. If you're coming up short, bump the sens up slightly - if you're overshooting, drop it down slightly.

What about using different sens and accel for different weapons?

I don't get why no top players use that. I mean, some weapons like LG need more precise tracking arm movement, but then rocket would need a more fingers/wrist flick movements. I use a different one for LG, other for RG, and other for the rest. I would like to have a general sensitivity and accel for everything, because sometimes I get paranoid about the "it can make your aim inconsistent", but I want to keep moving like most russians do (fingers/wrist flicking your mouse) because I've played like that for years, and with that kind of sensitivity im not able to aim with RG and LG. I simply do not get how you would play with 2.75 and near no accel (0.15). Thats pretty fucking low when you have to make sudden turns, or flick rails in very vertical maps like hub (im talking about fox cfg, who uses the same mouse as me, 1.1a).

Then, there is Cypher who uses sens 5 and accel 0.1, extremly high for LG imo (how in hell he does those stats with that kind of sens?) also same mouse.

The only explaination for me is that they use the Intellipoint drivers, and Fox has set a faster cursor speed than Cypher in those, so one has it more low on Q3, and the other higher, to compensate. If you have also the wmo 1.1a, just watch a Fox demo and see how he turns arround, then use his sens and accel. That is just not possible with such low values IMO.

What about using different sens and accel for different weapons?

I don't get why no top players use that. I mean, some weapons like LG need more precise tracking arm movement, but then rocket would need a more fingers/wrist flick movements. I use a different one for LG, other for RG, and other for the rest. I would like to have a general sensitivity and accel for everything, because sometimes I get paranoid about the "it can make your aim inconsistent", but I want to keep moving like most russians do (fingers/wrist flicking your mouse) because I've played like that for years, and with that kind of sensitivity im not able to aim with RG and LG. I simply do not get how you would play with 2.75 and near no accel (0.15). Thats pretty fucking low when you have to make sudden turns, or flick rails in very vertical maps like hub (im talking about fox cfg, who uses the same mouse as me, 1.1a).

Then, there is Cypher who uses sens 5 and accel 0.1, extremly high for LG imo (how in hell he does those stats with that kind of sens?) also same mouse.

The only explaination for me is that they use the Intellipoint drivers, and Fox has set a faster cursor speed than Cypher in those, so one has it more low on Q3, and the other higher, to compensate. If you have also the wmo 1.1a, just watch a Fox demo and see how he turns arround, then use his sens and accel. That is just not possible with such low values IMO.

I disagree, LG doesnt 'need' low sens at all, can aim just as fine with it with high sens.
I doubled my sens a while ago and it only had positive effects on my lg.

You can basically get used to any sens, if not to extreem.

I don't know why you think otherwise, but it's wrong.
It IS possible with such low values.. just move your arm fast(+he has accel)

I used to have a sensitivity of 2.27(45cm/360 no accel) later 3.1 and then 6.2(20cm/360), over the time of those changes, my aim improved, you get used to having to use smaller mousemovements.

Also, I have to correct you on cyphers mouse settings, yes he uses accel 0.1 and sens 5, BUT, he also has m_pitch and yaw at 0.018, so his sens is actually lower, comparable to around, 4.0 sens with m_pitch/yaw 0.022.

You can basically get used to any sens, if not to extreem.

You still can, LeXeR 2/2 style!

:D that's not TO extreme, fatal1ty used around that too, with extreem I mean /sensitivity 100 or /sensitivity 0.00001 or accel > 3 or so:D

:P

Forgot to mention I use a lower fov for RG than the rest of weapons, so I feel like if sens was higher. Is there a way to know how much you have to lower sens/accel to get the exact feeling as the rest? For example, sens 3 accel 0.5 on everything, fov 100 on everything but RG (fov 90). I know I could just try by trial and error measuring how many cm/360, but thats useless if you use accel, since your arm is not a robot that moves in the exact same speed. Also would be a pain the ass and cba really.

Isnt there a math formula or something?

No math formula that I know of, would be difficult calculating that because fov doesnt only have effect on sens, but on accel too.

of course there is, but there are several different methods of scaling sens with fov.

for example, the method used by q3 when using +zoom is to take the ratio of vertical fovs. however they make huge mistakes in the implementation by assuming the player is using both a 4:3 screen res and fov 90 (ish) when unzoomed.

there are other physical ratios you can use, some of which are easy and some require a bit of maths, but it's difficult to argue why one would be more 'the right one' than another.


either way, whatever you scale your sens by, you should also scale your accel by, to retain the same 'feeling'.

Yep, here & there.

I don't have time to read all of that tbh.

If I use sens 3, accel 0.5 and fov 100, but fov 90 for rail, what do I do to get the same sens feeling when fov 90 (as it seems faster)?

well the point is there are different methods of scaling sens with fov, but here are 3 for you:

fov 100, sens 3, accel 0.5

1) fov 90, sens 2.517298894, accel 0.419549816
2) fov 90, sens 2.7, accel 0.45
3) fov 90, sens 2.769187039, accel 0.461531173


at the moment i subscribe to method 3, but see which one feels right for you.

So, how did you get those values?

the scale factors are given by:

1) tan( zoomFov / 2 ) / tan( fov / 2)

2) zoomFov / fov

3) sin( zoomFov / 2 ) / sin( fov / 2)


each method represents a ratio of something physical that can only be explained with diagrams. as i said before, it's difficult to say why one should be more 'correct' than another.

I see what you did there. So how many decimals is Q3 sensible to?

enough. you get something like 6 or 7 places.

Also: there's your issue with per weapon sensitivity settings =P

I switched to same sens and accel for everything, with a nearer fov for rail. The problem now is that it seems to go faster with rail because of the fov 90, and the rest being fov 100. Annoying.

i played everything from sens 2.5 accel 0 to sens 9.6 with low accel. the thing is that i tend to miss a lot when i get bored with the game, so changing cfg makes it more interesting. for me at least. i agree with ddk, movement is most important, if you feel comfortable with that, the aim will come by itself.

btw i could never play good with low sens no accel cause i move like a fucking brick with sens 3 accel 0

MS 3.0 (400dpi) btw, take that into consideration.

i recomment some noob cfg, fov 100, sens 5, accel 0 / 0.1, you should be off good.

That noob cfg is basically Cyphers cfg.

yeah, i know. so?

I have one question

is this same value?

sensi 2 m_yaw/pitch 0.011 VS sensi 1 m_yaw/pitch 0.022

yes, if you have accel 0.

i developed a method of calculating the optimal sens and accel values based on real-world variables, such as tracking style and swiping/flicking speed and things like that.

i cant be bothered explaining it at the moment, but basically you first ignore accel and choose sens so it's low enough to accurately track slow-moving enemies, but not so low that it is uncomfortable or that you run out of mousepad when tracking slow-moving enemies. dont worry about spinning 180s or rjs or anything like that while you do this.

then once you have your base sens (mine is 50cm/360) then you add accel until you can successfully do a fast swipe of the mouse. now this depends on player preference, but for me i like a 'fast swipe' to equal a 180 turn, so add just enough accel to comfortably perform a swipe.

once you have your accel value, you need to lower the sens a little bit and increase the accel a little bit.

By slow moving do you mean running or walking? :P

slow moving, as in you have to rotate your view slowly in order to maintain tracking.

the actual speed of the target is irrelevant, this is all about angles.

That isnt very accurate of a calculation:D lots of 'little bits' :P

its far too complicated to write here, hence the "i cant be bothered".

that was just a brief explanation of the philosophy behind the method.

Oh, ye my bad:D

Methods don't work usually. Although one thing I'm curious about trying is, figure out what is the most comfortable speed I can move my mouse at, for long periods of time. Using like mouse movement recorder or something, that way I'd know my inches per second, since I would also measure dpi pretty precisely.

Then I'd go look up what the optimum radians per second turning speed is in cpm for circle jumping. Then set my overall sensitivity with no accel to make me turn at the ideal rate at the "comfortable to consistently at for long periods of time" speed. That would basically give you the best sensitivity for moving well possible.

I use a lowish sensitivity so when I turn to make a jump I used to have to consciously remind myself to move the mouse faster than I thought I had to.

The reason why I say methods don't work is because accel is just a way to turn around faster while keeping precision on slow/no motion shots at the expense of flick aim (unless you are intimately in control of your accel, which takes lots of experience). Usually the accuracy lost from a bit of accel can be counter acted by lower sensitivity.

Anyways no method for sensitivity either, every weapon except possibly gauntlet has situations when it would be better to have a relatively higher sens or relatively lower one. If you want to rail something behind you you'll wish your sensitivity was higher if you want to rail something all the way across a map and not miss you'll wish it were lower.

Always a trade off all you can do for sens is find a compromise that works for you. Same for accel, but I'd argue it complicates the process having two variables to play with. I just adjusted by .1's until I found something I liked.

I've changed sensitivity and accel since Q3 was released. I've played with all possible settings and have found that I could have sick aim with any 'reasonable' setting if I just played enough.

If I don't play for a while, accuracy will go down and it will take a shitload of playing to get the feeling back.

Nowadays I don't play so much and use medium sens with accel 0.1 just because I like the feeling. Accel 0 for me feels "boring".

So basically this is yet another post to tell you to choose settings you're confortable with.


PS I never was able to stop changing settings, so perhaps next week I play with accel 1.0 :))

I disagree with injx on that if you would follow his calculations, you would be right back to the beginning; fine tuning.

I'd say set a goal, pick a number, and just forget about it, don't change it unless it's REALLY uncomfortable(as I said, set a good goal...)
Do the same for accel, and you're done.

Is 1600dpi and sens 4 the same like 400dpi with sens 1? if no, how to calculate the same results

... the other way around, 1600 sens 1 is like 400 DPI with sens 4, roughly.

hm , great.

But the problem is the mouseaccel.

I surf with 1600dpi, because 400 is too slow. But it sucks with the mousesettings ingame.
So, I always have to change the dpi to 400dpi when I want to play.

seta m_yaw "0.0140"
seta m_pitch "0.0150"
seta cl_mouseAccel "0.3"
seta sensitivity "4"

Settings are great with 400dpi, but not with 1600.
Mouseaccel multiplicate the sensitivity or? Which values are ok to get the same feeling with 1600? Changing the DPI always when I want to play gets annoying =[
thanks in advance

Mouseaccel doesnt multiply the sensitivity, basically

seta m_yaw "0.0140"
seta m_pitch "0.0150"
seta cl_mouseAccel "0.01875"
seta sensitivity "1"

should feel the same, but I'm not to sure about that.

He'll have to do the same to the mouseaccel if I recall correctly (not used any other dpis for a long time)

It feels like the sensitivity is correct, but not the mouse acceleration. Its too fast.

that is wrong. dont give advice unless you know what you're on about.

seta m_yaw "0.014"
seta m_pitch "0.015"
seta cl_mouseAccel "0.01875"
seta sensitivity "1"

I forgot to divide the accel.

If you were quick enough you'd see that was not the only thing I forgot =)

1/0

Use a calculator.

I did, linux's calculator, LOL

rofl, try again

divided by 160 instead of 16, I'm full of errors it seems ;D

hey, thats perfect. Thanks for help guys :D

in general the rule is: if you change your mouse dpi, it multiplies the sens by the same factor, and multiplies the accel by the square of the factor.

so going from 400 -> 1600dpi means you need to divide the accel by 16 to keep it the same.

why not just set something and stick to it, lolz.

yeah pick a sensible value and stick with it

i set it so that i can do 180 degree turn- if you do more by a swing of hand then its too high

Yes same here! My how to find your personal sensitivity

- center your mouse on the mousepad (mat)
- exploit the space of it for a comfortable and quick 180° turn
- aware custom options: desirable accel, dinput on/off?
.

best advice here
get a comfortable 180, THEN start toying with accel if you really want to
i played fine for a long time without it, started toying with it.
it took me months to find a value i was comfortable with, but now i can say i don't see myself changing that part of my config anytime soon