Ok I think its important to have this poll once every 2 years to see how our mouse sensitivities change.

I use 15cm with Razer Lachesis but started with 3-4cm back in 1998

Have fun.

32cm for 1,75x so it's 18,3cm for 1x. It's sometimes too much and sometimes not enough, depending on the situation.

Yeah I agree with that. I just played some 6 player ffas and felt like 19cm is a bit too low in certain situations.

I used 60cm/360 degrees when I played CS and it became ~30cm for QW. I increased my sens to ~15cm about two months ago because it takes me too long to warm up now. Also, I tend to play with a long sleeve shirt when it's cold, and it felt nearly impossible to play at times with low sens :E

Something like 18 cm...

As Angua once said: "Use as high sens as you can handle. You'll get used to aim with the high sens." Or something like that. So... I use 5cm for 360 degree turn. Usually I shaft >25% vs. middleclass players on povdmm3. If I'd played more ofter my shaft, I'm sure, would be around 30%.

Shouldn't that be "Use as LOW sens as you can handle" ?

You gain a lot by having lower sens, you don't gain much by using very high sens, especially not in duels.

Thats my theory anyway

5cm for 360 that's just about reppie's sensitivity, whatever works works. i have about 1.5 swoops on my ikea clothpad for one 360.. i should up it .. Bah!

Angua did say high sens, but I agree with you D;

~50 cm for 360 degrees

Impressive.

9 cm for 360 degrees

mouse: Logitech G5 Revision.2007 2000DPI (no setpoint installed)
sensitivity windows XP SP3 - default (6th notch)
sensitivity ezquake - 1.7
in_mouse 3

13-15cm for 360 turn.

in_mouse 3 (in 1.9, in_mouse 2 in 1.8.3)

MS IE 3.0

13cm for 360.. usually enough for any situation but sometimes too high for my lg skills...
higher is better especially in 4on4 imo.

17cm.

For those who don't see the poll, click this link

I see dead people.

15cm.
modded G1 mouse (grip and weight) in_mouse 3, no setpoint, sensitivity 1 (set sens with pitch and yaw) sys_highpriority 0 (normal).
I find 15 cm very comfortable to use, 180 turns is no problem. I have used 15cm for ages.

Theres two types off direct input. buffered and unbuffered. I would like ezquake to support unbuffered direct input, since current is buffered.
"..the unbuffered read can only give you the very last mouse input, while the buffered read can give you the current, but also previous mouse data.
The buffered read causes mouse lag, because the mouse data gets recorded before processed.." (I read somewhere)
I played around with in_di_bufsize, and it feelt quite ok reducing it to like 1 or 2 instead off bigger values, while using in_mouse 2.

is in in_mouse 3 raw data api, like this --> http://msdn.microsoft.com/en-us/library/ms645543.aspx#_win32_Raw_Input_Model ??

Interesting Jaco.

In_mouse 3 that you (or Carmack???) is mentioning, says DirectInput, so my question: Does the 12ms lag occur in Raw Input, guess not?

Otherwise, I still haven't found a way to get in_mouse 2 (using directinput) to feel the same in 1.9 as in 1.8.3, tried to change the Buffersize, but that just seems to fuck up my sensitivity making it faster regardless of what I type more or less :S.

Well, where? Because I've explained on this forum not so long ago what that buffer does there. I quoted Microsoft's documentation there. And I'm tired to repeat myself everytime some user reads something "somewhere".

Buffered and Immediate Data

ok sorry Johnny.
But is in in_mouse 3 raw data api, like in the link i posted? (i guess so but not sure)
Was thinking about removing that carmac stuff. Its from when he made q3, and the in_mouse stuff isn't the same in as in qw (in_mouse 3) and its about old windows version etc. (like old ps/2 rate was 40hz in winnt)
btw i realy like in_mouse 3

Yes, please change your post somehow so that it doesn't confuse anyone, because in_mouse 3 in ezQuake really doesn't "Processes DirectInput mouse movement events", what you pasted is a description of an custom algorithm by id Software made on top of what we know as in_mouse 2.

Sorry but I can't resist killing cl_placebo 1

This means that no matter what you set in_di_bufsize to, always a number between 16 and 256 will be used.
And yes, Raw Input is that Raw Input you posted link to.

Johnny_cz: What buffsize is used in 1.8.3? (sorry if it's a stupid question) But I still can't get the same feeling in 1.9 and 1.8.3 using same cfg with in_mouse 2 :/

Getting used to in_mouse 3 now anyway, but it would be nice to find out what it is that makes the difference.

For cl_placebo fans I've added immediate data DInput mode

fog: Up to 1.9 DInput buffer size was 16, since 1.9 it's still 16 by default, but the way it's being set is different and I can confirm that there is some difference between 1.8 and 1.9, especially after in_restart (without changes). I don't know what's the cause though.
Edit: No, I take it back, I can't confirm there is a difference. What I get in both builds: in_mouse 2 in my config - mouse has same sens as with in_mouse 1 (3), after in_restart (without changes) I get some mouse acceleration in both builds (the only reason why I prefer in_mouse 3 - it doesn't get jammed after in_restart)

Haven't used in_restart in either 1.8.3 (dunno if it works there either) or 1.9 when using in_mouse 2, and I can a 99.9% sure say that there is a difference. I play a lot of povdmm4's and I tested vs a player i've been playing vs before and that I get around 40% vs. Tested first 1.8.3 and got around that %, tried 1.9 with in_mouse 2 and same cfg as 1.8.3, was down to 34% and almost impossible to hit, mouse felt totally strange, then back to 1.8.3 with same cfg and back to 40%. (I don't mean to brag, just saying that I really did notice the difference since it's the map i've played most and <35% vs that opponent kind of never happens otherwise.)

EDIT: The difference were in how the mouse reacted to small and fast movements, it wasn't nearly as exact as before. Strange shit I must say.

In case someone doesn't know, in_restart is only required when changing something related to input that actually requires re-initializiation of the input, for example changing in_mouse values.

Do NOT write this command in your config.

ye, i noticed that in_di_bufsize would change automatic if set to low (but ez would not always print it in the console that it uped the value, but often it would say it uped it to ca 50) so if there was some difference, if must have been betwhen 16 and higer values like 256, 512 etc bufsize. (still not sure if it was)

about 5 cm (approx the width of two US quarters, which are 25mm afaik)

when i use lg my script changes it to 1/2 sens so its 10cm for lg for me.

What is cm?

INCHES BABY!