Quake3World

Because the mouse sensitivity in Settings isn't cutting it. It's either too fast or too slow.

Thanks

/sensitivity

you can also adjust the yaw and pitch independently (left-right sens and up/down sens) using m_yaw and m_pitch

/cl_mouseaccel adjusts mouse acceleration.

Also

/cg_oversamplemouse - Makes it a tiny bit smoother or so go the rumors

/m_filter - smooths out movement also but can create small bits of lag, most ppl play with this off

/in_mouse - you can have either -1 or 1. I use -1 as it feels a little bit more "loose", the way I like it.

With in_mouse and mouseaccel you will need to play around and adjust /sensitivity also because the "speed" will change as you adjust those values.

[xeno]Julios wrote:/sensitivity

you can also adjust the yaw and pitch independently (left-right sens and up/down sens) using m_yaw and m_pitch

/cl_mouseaccel adjusts mouse acceleration.

Yeah I tried 4.5 for sensitivity and i couldn't move to left or right. I messed around with the m_yaw and m_pitch too but i seem to have no luck. cmds or no cmds, I will always suck lol.

dzjepp wrote:Also

/cg_oversamplemouse - Makes it a tiny bit smoother or so go the rumors

/m_filter - smooths out movement also but can create small bits of lag, most ppl play with this off

/in_mouse - you can have either -1 or 1. I use -1 as it feels a little bit more "loose", the way I like it.

With in_mouse and mouseaccel you will need to play around and adjust /sensitivity also because the "speed" will change as you adjust those values.

the oversamplemouse cmd doesn't appear to be valid. What should I set m_filter to? Yeah it does feel a little more loose now with in_mouse -1

Make sure you have vsync off in your video drivers and in Q3 (r_swapinterval 0). I used it for a while but it lags mouse input badly.

Oeloe wrote:Make sure you have vsync off in your video drivers and in Q3 (r_swapinterval 0). I used it for a while but it lags mouse input badly.

So even though I should use it, it will lag me from time to time?

And what if you put in_mouse back to 1, would it improve the lag?

I've always played with in_mouse 1, but vsync just slows down the mouse input. Your effective sensitivity goes down and fast mouse movements are messed up.

wtf. you guys make it so hard. You are just making it worse.

All you have to use is /sensitivity. That other stuff is only for if you want to go pro. They only tell you that stuff because they are bored and are trying to show off or fuck you up or something. I don't even know. Seriously, when does dzjepp ever post aything helpful?

:icon31:

Lenard wrote:wtf. you guys make it so hard. You are just making it worse.

All you have to use is /sensitivity. That other stuff is only for if you want to go pro. They only tell you that stuff because they are bored and are trying to show off or fuck you up or something. I don't even know. Seriously, when does dzjepp ever post aything helpful?

So what should I set the sensitivity to then? And when I mess with the /sensitivity cmd, I can't move left or right no more.

Really? That's not normal.

Anyway, you should set your sensitivity to a value that gives you the mouse speed that's right for you. Just find the right number with which you're not struggling to turn around 180 degrees (huge arm movement) or struggling to keep the crosshair steady (spinning around). If you keep your wrist at your desk/mousepad when moving the mouse (high sens player), you'll want to be able to do a 180 degree turn with one move of your wrist. If you use more arm movements (bigger mouse moves), you'll want to use a lower sensitivity.

I think FFA/1v1 players use a higher sensitivity then CTF players.

I've been lowering my sensitivity over time to about 20% what it once was. Ofcourse I have another mousepad but aiming has improved a lot and I can still do 180's in one move.

I don't use cl_mouseaccel because it messes up my rail aim (fast aims).

about m_filter - use 0

that way, your raw hand movements will be transduced into xhair movements with high fidelity.

with m_filter 1, I think an algorithm is applied which averages the last two movements, resulting in a smoother (but less accurate) xhair movement.

what is in_mouse -1 vs 1 exactly? one use desktop settings versus mouseware/driver?

The config in Cure's modular config say this:

Use mouse as an input device, 1 to get the same 'feel' as version 1.27h, -1 to get the same 'feel' as version 1.17.

So something about the mouse input changed in pointrelease 1.27h, which you can disable with in_mouse -1.

dzjepp wrote:Also



/in_mouse - you can have either -1 or 1. I use -1 as it feels a little bit more "loose", the way I like it.

i think it's the complete opposite. -1 feels like its a little tighter and easier to hold a line when strafing or aiming. 1 is all loosey goosey to me...

Wow, just tried in_mouse -1. Not good for me. The effective sens is a lot lower and when i try to compensate for it by raising my sens, it still feels clunky. I couldn't do the B2R on dm6 with 125 fps on a listen server, but when going back to in_mouse 1 with my original sens, i did it at the 1st try... Keeping in_mouse 1.

I remember i used to use -1 in the past, but luckily i changed it to 1. Probably helped improve my skills.

It's just a personal feeling thing, like cl_mouseaccel. Some people like it, some don't.

Woohoo! Another new player? It's always nice to see fresh blood in the arena.

Pretty much the only cvars that you need to worry about when considering mouse dynamics are: sensitivity - Your best off adjusting your sensitivity first. Find a value that allows you to move/look around comfortably while still allowing you steadily aim at your targets. I suggest you hop on a server, pick a sensitivity, run around and kill people then periodically increase/decrease your sensitivity in increments of 1 until you find something you like and stick with it.

m_pitch and m_yaw - The pitch and yaw values allow you tweak your horizontal and vertical sensitivities to your liking. Generally they are set anywhere from 0.012 to 0.025 to give you an idea.

cl_mouseAccel - Mouse acceleration basically means that the faster you move the mouse, the quicker you turn in Q3. It is a matter of preference, some use it, others don't. With mouse acceleration enabled you can lower your sensitivity and slowly move your mouse to take aim with the railgun and quickly flick the mouse in a close rocket fight without running out of space on the mouse pad. So in a way it gives you the best of two worlds. You must get used to mouse acceleration, as to just about anything new to you. Mouseaccel, if you choose to use it, is generally set to a value from 0.1 to 2.0.

Set m_filter to "0" and in_mouse to either value (which ever feels better to you).

Good Luck and Happy Fragging!

pumpkin wrote:what is in_mouse -1 vs 1 exactly? one use desktop settings versus mouseware/driver?

From testing on WinXP, both -1 and 1 are influenced by your underlying windows sensitivity.

As I understand it (I haven't looked at the q3 code!), -1 does some horrible voodoo where it lets the cursor wander over the screen in between frames, then takes a vector on the distance off-center and resets it at each frame. That vector is your mouse movement.

1 is supposed to use directinput, and I have no idea what that does.

BUT, if you throw out the speculation and some tests:
- at high, stable FPS, I honestly can't notice much difference
- at low fps (like com_maxfps 15), setting in_mouse -1 and in_restarting seems to lower my effective sensitivity greatly

The rough equivalent of DI on linux is DGA; this is why newer games (just ET I think) based on q3 have in_dgamouse to override the crufty old method.

day wrote:The rough equivalent of DI on linux is DGA; this is why newer games (just ET I think) based on q3 have in_dgamouse to override the crufty old method.

Q3 itself has in_dgamouse too (and has had since at least PR 1.30, I think).

who gives a flying **** just goddamn change it in the menu