Play with in_mouse 1 for two weeks, then play with in_mouse 2 for two weeks. Decide what you like best.

the bind goes to 1, waits a bit then goes back to 2. It's meant to counter a bug from the closed beta iirc.

there is still some bug though it somehow seems connected with m_filter and vertical movement - when filter is enabled some small vertical movements can start being ignored after a while, it's like you need to move the mouse with certain speed in order to unblock the cursor from staying still vertically(bug can be triggered when using some minimizer with QL for example), you gotta not only change in_mouse but m_filter to 0 aswell and then back to get rid of it

the bind actually goes to 0, and then back to 1, thats what threw me off a bit, because in the configs themselves, in_mouse is set "2", yet in the bind, it goes in_mouse 0 -> in_mouse 1.

the bind is from the beta, no one uses it anymore afaik, back then there probably was no raw input in ql.

hm, anonymous has this to say about it
http://www.esreality.com/?a=post&id=1696516#pid1696516

only stermy uses 1 afaik, rest use 2. Also stermy uses a lot of delaying stuff like cg_filter_angles which seems to have no influence on him due to high sens

the game feels significantly more responsive to me, with in_mouse 1.. i do not understandt that at all

I was experimenting with in_mouse 1 recently and I came to this conclusion:

It's accelerated, but in a very weird way.

It is similar to something like this:

sensitivity 4
cl_mouseAccelPower 3
cl_mouseAccel 0.1
cl_mouseSensCap 4.2

I think the overhead produces a latency for direction changes such that some counts are ignored during the initial motion.

It feels smoother and I like it for LG'ing, but it throws off my aim for anything else.

Wasn't that the main benefit of raw mouse input, when it was introduced? To get rid of the low accelerated feeling using direct input and a lower DPI? I remember playing with in_mouse -1 some years ago. The game was Soldier of Fortune 2. (-1 was the default for SoF2 unlike SoF1) When playing with in_mouse 1 and changing sensitivity from 3 to 4 (changing dpi accordingly) i felt a very small amount of neg acceleration. That wasn't the case with in_mouse -1. With direct input my sens had to be at least 3. Thats how i remember it. I was pretty high sens back then. (like 8cm/360°)

Something like that.

in_mouse -1 != in_mouse 2 though

A piece to the puzzle:

http://msdn.microsoft.com/en-us/library/windows/desktop/ee418864(v=vs.85).aspx

Use raw input whenever possible.

/thread

Use raw input whenever possible.

/thread

I've used 1 for a while, tried 2 for a few weeks when it came out and never understood why my lg was consistently 5% lower even though my sens felt the exact same, switched back to 1 and it instantly went back up