it would always listen when "someone" says somethings better... go search the forums this has come up before.

i did, and it still gave no real conclusion, i just found that -1 should only be used for low dpi mice like the 3.0 intellimouse i use, and that it can cause accel if u dont have stable 100+ fps

well that is quite a result? :p yeah i found 0/-1 causes strange behaviour with any kind of higher dpi mice. i loved the feel though... i guess it really depends on what you think is better for your game.

I think it really depends on your OS. You'd be better off searching for it, though, like zealot said.

in_mouse 1 : Direct Mouse Input
in_mouse 0 : Windows mouse sensitivity & acceleration settings
in_mouse -1 : Don't actually exist within the game code (even though it was mentioned in changelogs, etc). Would result in the same thing as setting in_mouse 0.

lol

For me, -1, 0, and 1 all do distinctly different things...

-1 uses classic windows cursor position grabbing
0 turns mouse input off (windows cursor floats over the game allowing you to move it, but it will never center)
1 turns DI on.

Someone's looking at the wrong codebase... :P

1: DirectInput mouse: *by far* the best option
0: no mouse support
-1: WM mouse: crap, still exists solely because it was the pre-1.17 default and the whine was earth-shattering

People say there's some automatic filtering when using in_mouse 1, is this true? The aiming feels slower when using it, but that may be in_mouse -1 being kinda twitchy.

Of course not. It's just one of those absurd stories people like kdawg and Gaz make up to try and convince everyone how clever they are, then other retards repeat it forever as if it was true.

add> and indeed, here's the same lie stated as fact 18 months ago http://www.esreality.com/?a=post&id=1116194 and doubtless every year before that too. sigh.

such a shame strider isn't around anymore

serious
he was one of my favorite q4/pk players to watch

strider not ztrider :(

FUCK YOU!
YOU CAN'T CRUSH MY DREAMS!

arQon is correct, I was looking at a separate codebase than the latest 'Q3' release.

1: DirectInput mouse:
0: no mouse support
-1: WM mouse:

i have tried both but as usual with loads of practice u can hit the same on each one

In_mouse -1 makes the game use Windows cursor grabbing--between every frame of the game (usually 125hz) the Windows cursor is centered on the screen and you move the cursor some distance away from the center of the screen. That distance is relayed to the game as XY values for mouse movement, the frame is rendered, and the process repeats itself. No smoothing is automatically applied to these inputs, so it feels raw and clean when you use it, and after using in_mouse 1 for a while it may even feel fast and jittery.

The problem with using this method is that the cursor cannot move outside of the window the game creates, the size of which is dictated by the resolution you are running the game at. If you run a high dpi mouse with a low screen resolution, you will run into clipping (negative acceleration) problems really fast, but if you use a low dpi mouse it should be fine. You can figure out how fast you can move your mouse (in inches per second) by using this formula:

(Xres/2) * (FPS) / (Mouse DPI)
or
(Yres/2) * (FPS) / (Mouse DPI)

for the X and Y components, respectively.

But if it feels fine it usually is--the negative acceleration effects are very pronounced.



This clipping problem is avoided by using in_mouse 1, but the mouse inputs, allegedly (haven't seen the code for this, but I can feel it when A/Bing the two modes), have some sort of automatic smoothing applied to them, adding some nearly imperceptible delay to the mouse movements and clicks.


Both let you play just fine though, it's really a matter of what you're used to.

intelligence? on ESR?
sir, GTFO or you shall be flamed and forgotten

cool.

so whats better for wmo 1.1a

-1 probably

Why? It sucked. If its set to -1, it depends on intellimouse drivers, which is something stupid. Why not set it to 1 and just use only Q3 to tweak your sens? (so it doesn't depend on the driver's speed bar, "allow precision" and the rest of typical driver bs options, plus it will feel always the same if you play at another computer).

I don't play at other computers, or use factory drivers, allow precision doesn't function on my PC because of a patched system file to remove windows pointer ballistics (always 1:1), I'm not using any desktop sensitivity modifiers and so they feel basically the same.

I just checked what one I was using with my ie 3.0 and I had in_mouse 1. I played in warmup with -1 and it feels the same response wise and such.

Subjectively, -1 was a slightly more notchy feeling, barely if any quicker responding and a little less stable feeling. But the differences weren't anything to make a book about. Seeing as I read this thread before I tried comparing the two the above may as well be placebo, and probably is since the differences were slight.

For me in_mouse -1 is perfect @ my Razer DB. The difference in mouse behaviour is huge imho:

in_mouse 1 smooth running crosshair causes by constant and direct mouse response (perfect for lowsenser who use only arm accel)
in_mouse -1 less smooth in order to have different mouse response (perfect for midsenser who uses mouse accel but don't want to disclaim more control @ pixelshots)

So I point out that Q3A is out of the box designed for lowsensers and many less experienced quakers don't know about the different input cvars...

Yeah I use -1 with Razer DB@1600dpi as well. Around 19cm/360 and it feels perfect.

does it -really- matter?

If you are a gamer yes.

people tend to spend more time discussing sensitivities and mousepads more than actually playing

True ;-)

I still think -1 is pointless.

Tastes differ, you know.