Try using this:
m_cpi 1000 (and 800 on the other pc) (your dpi value)
sensitivity 20 17.325
m_yaw and m_pitch both default!!!
And put all accel related cvar's to 0, just to make shure there won't be any trouble using m_cpi

I will explain shortly how it works - the best feature of m_cpi is that it is the only cvar you must change in order to have the same sensitivity on two(or more) setups or different mice with different cpi(dpi). In fact, the sensitivity value is actually your sensitivity in centimeters needed to make a 360 degree turn in game. If you wonder about accel, the only thing I know is that cl_mouseaccel is set to your real accel value.

Edit: These are the actual formulas in order to convert your settings to m_cpi:

new_sens = old_sens * (old_yaw * m_cpi / 2.54)
new_sensCap = old_sensCap * (old_yaw * m_cpi / 2.54)
new_accel = old_accel * ( old_yaw * (m_cpi/2.54)^2 ) / 1000
new_pitch = old_pitch * (0.022 / old_yaw)
new_yaw = 0.022

The other way is to divide 360 by cm you want, and the given number will be your new m_cpi sensitivity.

Source

m_cpi ftw.

syncerror's documentation of the m_cpi setting:
http://www.quakelive.com/forum/showthread.php...ight=m_cpi

(make sure ...
1: the dpi don't get modified by mouse-driver-scaling-factors.
2: in_mouse "2" so win-multipliers and win-accel can't do any harm)

Sweet thanks will try that, I am NOT using accel and I use default pitch/yaw values. I also use in_mouse "2".

So is the general rule to set m_cpi to your dpi?

How did you get to sens 20, 21 and 20.7 given the info I just gave?

When I measure I get ~21.5cm/360

Yes, set m_cpi to your DPI and then divide 360 by the cm you want. If you want 21.5 then sensitivity = 16.744. If you switch mice set m_cpi to its DPI and your sensitivity will be the same.

I'm confused here.. Why would I divide the cm I want by 360 to get the sens? afters setting CPI shouldn't my sens already be directly related to the CM's? So if I want 30CM/360 my sens should be 30, no?

Will give it a try when I get home and let you know.

So if I want 30CM/360 my sens should be 30, no?

No, it is not. Sorry, I made a huge mistake there...

The sensitivity formula to switch sens to the m_cpi sens is this:

new_sens = old_sens * (old_yaw * m_cpi / 2.54)

I forgot that you can also divide 360 by cm you want ingame and the number you get should be your new sensitivity.

So, if you calculate your sens by the formula it is:

2.5*(0.022*(800/2.54)) = 17.325

And if you divide 360 by ~20.86cm, you will get ~17.3

So, in the end, you should use sensitivity 17.325

No, I said divide 360 by the cm you want. 360 / cm = s. If you want 30cm/360 then sensitivity = 12.

"So is the general rule to set m_cpi to your dpi?" - well, to your "effective CPI", because some mouse drivers are able to apply scaling to your mouse dpi. if that is not the case, yes: seta m_cpi "your mouse dpi".

"I'm confused here." - when you use the m_cpi setting, sensitivity has a natural scale of [turn in degree / distance in cm]:

example 1 (you want sensitivity "10" [°/cm] and want to know what distance will be needed for a 360 [°] turn):
360 [°] / 10 [°/cm] = 36 [cm] --> the distance you will need for a 360 [°] turn will be 36 [cm].

example 2 (you want a desired distance which you measured 36 [cm] and want to know what sensitivity [°/cm] you have to use):
360 [°] / 36 [cm] = 10 [°/cm] --> the sensitivity you will need to use to have 36 [cm/360°] will be "10" [°/cm].



your case is example 2:
360 [°] / 21.5 [cm] = 16.744 [°/cm] --> sensitivity "16.744" to have 21.5 [cm/360°].
but ...
keep in mind, that measuring by ruler always had problems:
when you measure the distance for a 360 turn and the crosshair ends at a position above or below the initial position, your mouse movement included a vertical component which manipulates the result of cm/360.
even when the crosshair ends at the initial positon, your measurement might be inaccurate aswell, because your mouse movement could include a rotation back and forth which made the crosshair follow a bow instead of the horizon.
and if the applied turn gets lower (let us say 180 degree turn instead of 360 degree), a measurement error of 3 millimeter has twice as much influence in percent.
therefore ...
i would prefer syncerror's formula and then cross-check it with the ruler measurements before and after the cfg-change:
new_sens = old_sens * (old_yaw * m_cpi / 2.54) = 2 * (0.022 * 1000 / 2.54) = 17.323 degree/cm --> sensitivity "17.323" & m_cpi "1000 respectively 800".
when the ruler measurements before and after the cfg-change on both systems differ in a coarse manner, your mouse driver (one or both) most likely scales your mouse dpi.

Thanks to all for replying. 17.32 works like a charm. Guess my
Effective sens is 20.78/360cm.

np.

no problem ;)

1) yes, it does

2) No, the math behind DPI/sens is much more complex

http://www.funender.com/quake/mouse/index.html

lmfao, cripple.

1) no.
(why the fuck resolution should affect sensitivity? even your own link says it doesn't.)

2) yes.
(math in general is too complex for you, you already failed to count up to 4 in another thread.
only the dpi changes, which lickwidice compensates with sensitivity by forcing a constant result of the multiplication.)

if you got nothing to say, just do it, pony boy.

Resolutions affects sensitivity, if you have evidence that prove otherwise, feel free to post it.

the link you posted says otherwise, the forumula in inches is 360/(yaw*dpi*win sens multiplier*sens)

The sensitivity doesn't change, but it will probably feel different. Altering FOV will have a similar effect.

Exactly.

I run a double display setup right now, obviously same exact config/mouse/DPI - changing the screen resolution and swapping between 4:3 and 16:9 (r_mode 9 / r_mode -2) creates a very different mouse feel.

In theory, the sensitivity hasn't changed, the ratio is exactly the same.
However, in practice people will notice the "difference"

Smackahontas here's another link that's actually relevant, if you came here to bash me and post youtube links you might want to try a heartless thread


http://www.esreality.com/post/2285350/higher-...ensitvity/

"if you came here to bash me and post youtube links you might want to try a heartless thread" - if you came here to post fully retarded troll-content you might want to try a pony thread. oh wait ...

Teen Queen's fountain of knowledge:
"Smackahontas here's another link that's actually relevant" - yeah, this is the second link you post that proves you wrong: resolution doesn't affect sensitivity.

I don't think you read the thread, try to read a few posts and then MAYBE just maybe you will finally realize that changing resolution doesn't directly affect your sens but the in-game feel is different.

Can you at least try to comprehend that whilst trying to search for another youtube video?

yeah, this is the second link you post that proves you wrong: resolution doesn't affect sensitivity:

"Can you at least try to comprehend that" - ye, comprehension: you are too retarded, pony boy:

It doesn't affect it directly but it feels somewhat different.

you already sound like jamerio:
underwear affects sensitivity, if you have evidence that prove otherwise, feel free to post it.
http://en.wikipedia.org/wiki/Russell%27s_teapot

it gets even funnier, because i already wrote that you posted the evidence on your own:
"even your own link says it doesn't."

I agree with you however my logic tells me Teen Queen may be onto something.

DPI = Dots Per Inch right?

So won't a higher resolution result in more dots per inch required?

What I'm saying is:

at Res X: DPI required to move from point a to b is ~ 500,
at Res Y: DPI required to move from point a to b is ~ (Y/X)*500

Not exactly, the ratio remains the same but the overall feeling is a bit different, especially when swapping 3:4 and 16:9 aspect ratios.

Considering quakers always want the same exact feeling when aiming and get picky about minor changes, I would go as far and say that resolution does have some effect on sensitivity.

But I guess we can wait for that German psycho to post another youtube vid and prove me wrong \ :( /

so ridiculous how you try to evade how useless your posts are.
Teen Queen's fountain of knowledge:

"So won't a higher resolution result in more dots per inch required?" - idea behind that is:
the dpi of your mouse must be high enough, so the distance between two dots (smallest distance your mouse can recognize) results in a rotation angle that is smaller than 2 pixels on your screen.

experiment:

screen with a low resultion and a mouse, which doesnt violate that rule.
now you replace the screen with one that has much higher resolution and therefore violates that rule.
this makes the smallest turning angle - your mouse can measure - be higher than 2 pixels on the screen.

but the mouse input characteristics like cm/360 and accuracy didn't change. you just see more pixels passing by at the smallest distance your mouse can process (gl with that).

just imagine the second screen has an infinite amount of pixels. does this mean the mouse now needs an infinite amount of dpi to be accurate? no.

that is why i never gave a fuck about that rule. especially since the human hand's accuracy in dpi is much lower than the dpi values of modern mice.
but a lot of players use it, so it is up to you to decide if it is necessary or not.

This is what m_cpi is designed for..

1) no, feeling might change though
2) yea, thatll work

I play on a 1920x1080 ViewSonic VX monitor and I tell you that the Wheel Mouse Optical is total garbage unless you play on a low-mid sens.

Even at sensitivity 4 and FOV 100, with a 450 CPI mouse yields 23cm/360 degrees and the minimum effective CPI is 557 to the nearest whole number... that means that even with default settings each minimum rotation you can possibly do will be significantly more than 1 pixel. Imagine if you want to play on a mid-high sensitivity 11.5cm/360 the minimum effective DPI is 1113. This is completely unplayable... I tried it once and I could not even hit 30% lg against nightmare bots. Massive pixel skipping was just obviously clear.

On a 1920x1080 monitor if you want your aim to be at least decent (pixel precise) with the Wheel Mouse Optical (450 CPI) you must play on at least 29cm/360. With a higher DPI mouse you can maintain pixel perfect accuracy even at higher sensitivity. If you play at 2cm/360 for example the estimated useful DPI is a whopping 6124!! Having slightly less DPI probably won't harm your aim much so lets say you have a mouse capable of 6000 DPI. That means on 6000 DPI to achieve 2cm/360 you would need: 6000/450 = 13 to nearest whole number 44/13 = 3.3 sensitivity. Therefore higher DPI mice ARE necessary for high sensitivity on high res monitors even for such a basic game such as Quake Live. Input this into funender and you will end up with exactly what I wrote here.



I was wondering what the reason to my poor aim was - a lack of DPI! So I got a SS Kana and set the DPI to 1600 and sensitivity to 2 (12.9cm/360) and my aiming has greatly improved. I now consistently hit 30% lg in tier 4 Clan Wars (which for me was extremely rare with my old setup up WMO at default).

Basically, you must consider the whole picture... the pro configurations e.g you must realise that they may be using different monitors, resolutions different systems, different mice etc, etc... each of which can change your perception of the game and CAN in fact impact accuracy greatly. Basically keep tweaking until you find something that makes you the most accurate. For me its 12.9cm/360 at 1600 DPI (therefore sensitivity 2).

12cm/360 mid high sens


wat.

12cm/360 is ridiculously high.

Your knowledge about mice, sensitivity, aiming and general hardware is complete trash tbh.

Yeah rapha has a lot of trouble aiming at 1920 with his wmo and high sens/accel.. not.

Have you actually bothered to use the funender useful DPI calculator? Thought not... even at default sensitivity the estimated useful DPI is 553 at a resolution width of 1920. The only time you will NOT get any pixel skipping with a 450 DPI mouse on a 1920 width monitor is if you use a low sensitivity >29cm/360. Now having a slightly lower DPI value than useful will not impact your gameplay much but if the value is significantly lower you WILL notice a huge difference in playability.

Basically its advised not to go above sensitivity 5 even with a low resolution since the tracking quality will drastically be reduced. And if possible set the highest DPI that your mouse can track well at and scale down the sensitivity from there. Like this you will get smooth as butter, pixel precise movement.

- no pixel skipping in an fps with a fixed crosshair!
your crosshair doesn't move

Missed my point completely.

I played at 12cm/360 at 400dpi for years, and occasionally switch back to it.

There definitely are pixel skips at that dpi (which is why I changed) but it is not as dire as you make it out to be. I found 16cm/360 to eliminate most of the pixel skips at 400dpi.

Last week I was actually playing around with my sens and tried out my 12cm/360 sens, it was definitely very nice at 900dpi, but the difference with my accs were minimal compared to 450dpi. It was more of a bother because you are actively looking for those pixel skips.

I still play at 450dpi, albeit now with a medium sens + accel, I can't get used to high dpi in windows and I don't like to change default windows mouse settings.

No pixel skipping with an aimbot... you have 100% accuracy with no mouse.

what a relevant post.

Problem: Old mouse broke. Did not use m_cpi
400 dpi to 8200 dpi
2.5 old sens
0.16 old accel
7 offset
rest standard i believe.

I FORGOT HOW TO MATHS

it should be like this @ 8200 dpi
sens 0.12195122
accel 0.00038072575
offset 0.34146341463
this will give u the most accurate feeling compared to the previous one
however if u dont like those long numbers u can round them up
shits retarded though

Thanks buddy!
But apparently I bought a razer mouse, and as per usual they don't work so I'll be returning it very soon. Bollocks.