You can adjust the ratio between horizontal and vertical mouse movement.

i THINK

sens 5 , m_yaw 0.022 = sens 2.5 , m_yaw 0.011


not sure tho :)

m_yaw / m_pitch is just a multiplier for the sensitivity value.

if you double both it's the same effect es doubling the sensitivity

but you have the chance to adapt them to the reality (a monitor isnt 1:1 but 4:3 16:9 format, so to have a perfect feeling of the mouse you would have to set your m_yaw : m_pitch like 4:3 (with that factor)

anhi wrote:

m_yaw / m_pitch is just a multiplier for the sensitivity value

thats not right.
so why you think ppl like cooller playing with m_yaw 0.014 and not just lower the sensitivity? change the m_yaw and m_pitch is a completle different game-feeling.

well does he have a different value for _pitch too?
yaw is a multiplayer for the horizontal movement and pitch for the vertical one. it doesn't change the "feeling".

You are right. He has a different setting for m_pitch.

Ok, so for the test.

Set m_pitch and m_yaw to 0.011 and adapt the sens, i mean
the cm for one turn. And play for some hours ... you will see a different, esp. if you using different fovīs (then u will feel the change immediately) like zoomfov.

You are wrong but also correct (unknowingly) because on different m_yaws and m_pitches the accel operates differently, but not the sensitivity, for example

0.022 pitchyaw 5 sens = 0.011 pitchyaw 2.5 sens BUT

0.022 pitchyaw 5 sens 1 accel <> 0.011 pitchyaw 2.5 sens 1 accel

You see, it only affects the sensitivity and not the pitch/yaw.

So by manipulating the pitch and yaw, you can make acceleration operate slower, so that it's a more gradual acceleration, or more violent. make sense? (get it? make "sense"? Bwahahahha)

sure. that was what i mean.

i play with 0.013 since quite a while (i changed it when i changed my fov and mousepad so i didnt had to use a crappy sens, i use accel 0 so i never noticed..thanks
[+]

m_yaw is the yaw and m_pitch is the pitch!

tbone thanx
but
1)myawpitch 0.022 + sens 5 = myawpitch 0.011+sens 2.5 ?:P
i think u meant smth like myawpitch 0.011 + sens 10 :D
2)with myawpitch lowered the accel feels slower i think , is this right ?

with myawpitch lowered the accel feels slower i think , is this right ?

ye

BTW, when you're playing quake, make sure to check out the m pitch/yaw commands often. Quake adds extra 0 values, but I don't know why. For exmpl: 0.0022 or somethin...

Both commands does effect your aiming, and sensivity influence I guess.

"m_yaw is the yaw and m_pitch is the pitch!"

lol!!!

Here is the code from cl_input.c which is responsible for transforming dx and dy mouse increments into corresponding view angles. This is the ultimate answer to all Quake 3 mouse sensitivity questions. :)

/*
=================
CL_MouseMove
=================
*/
void CL_MouseMove( usercmd_t *cmd ) {
float mx, my;
float accelSensitivity;
float rate;

// allow mouse smoothing
if ( m_filter->integer ) {
mx = ( cl.mouseDx[0] + cl.mouseDx[1] ) * 0.5;
my = ( cl.mouseDy[0] + cl.mouseDy[1] ) * 0.5;
} else {
mx = cl.mouseDx[cl.mouseIndex];
my = cl.mouseDy[cl.mouseIndex];
}
cl.mouseIndex ^= 1;
cl.mouseDx[cl.mouseIndex] = 0;
cl.mouseDy[cl.mouseIndex] = 0;

rate = sqrt( mx * mx + my * my ) / (float)frame_msec;
accelSensitivity = cl_sensitivity->value + rate * cl_mouseAccel->value;

// scale by FOV
accelSensitivity *= cl.cgameSensitivity;

if ( rate && cl_showMouseRate->integer ) {
Com_Printf( "%f : %f\n", rate, accelSensitivity );
}

mx *= accelSensitivity;
my *= accelSensitivity;

if (!mx && !my) {
return;
}

// add mouse X/Y movement to cmd
if ( in_strafe.active ) {
cmd->rightmove = ClampChar( cmd->rightmove + m_side->value * mx );
} else {
cl.viewangles[YAW] -= m_yaw->value * mx;
}

if ( (in_mlooking || cl_freelook->integer) && !in_strafe.active ) {
cl.viewangles[PITCH] += m_pitch->value * my;
} else {
cmd->forwardmove = ClampChar( cmd->forwardmove - m_forward->value * my );
}
}

I prefer to guess and make up rumours, thanks.

Sorry for spoiling

looking at this reminds me of my epic fail java programming learned at univ... sigh~

xD

OLOL U NERD!111

anyway, did u stole this from carmack or whut?

=P

q3 is open source you know? :p

i know.. i'm just assuming he got this before august 2005...

=P

ye... RIGHT :D

this should be modified to have only raw mouse input without all that extra crap.

Hm, cannod find there neither DI or raw input... Can you help me?

what on earth are you on about?

I probably haven't phrased it correctly but what exactly do we need m_pitch and m_yaw for ?

for independently scaling the sens and accel on horizontal/vertical axes of course.

what have you been smoking?

a ye, forgot some people want that. I presume cl.mouseDx/Dy are mouse coordinates. so he adds sensitiity and m_pitch m_fov values to that to calculate the actual distance the view moves in game. if we were to remove these values we'd get a "cleaner" output presuming we don't want m_pitch/yaw and accel.

I just tried setting m_pitch/yaw to 1 and reducing the sensitivity to get the same 360 distance. I must say it feels quite different, more steady and solid. think I'll keep this setting. :)

placebo.

multiplying by 5 and then by 0.022 is exactly the same as multiplying by 0.11 and then by 1.

there's nothing 'cleaner' about it.

exactly what I thought. still going back and forth between these two "same" settings screwed up my aim completely. interesting

what settings are you using? (including accel)

it's in my cfg

If this code is correct (which it seems) then the formula for the turning angle of one direction :=

Angle(x) = yaw * x * (sens + ((x * accel) / frame_msec)

yaw := the value of m_yaw or m_pitch
sens := sensitivity value
accel := cl_mouseacceleration value
frame_msec := 1 / com_maxfps
x := mouse input value (0 to 10 are normal above that are more or less extreme flicks (measured with cl_showmouserate in q3)


This formula also shows when turning into a graph that if you'd decrease m_yaw you would have to increase your sens by the same amount to get the same result. This also goes for accel.

Thus:
m_pitch 0.022
sens 5
accel .1

is the same as

m_pitch 0.011
sens 10
accel .2

Hope that'll clarify it all.

*Awaits a coherent response*

Its in there somewhere! I'd stay away from all that code stuff though, it looks scary :o

Hey guys I make a mod where I limit m_yaw and m_pitch to use certain camera angles (Like side view makes m_yaw 0.000

I never thought anyone changed m_yaw or m_pitch past 0.022, but after this thead I'm a little worried.

Anyways, here's what my game does. I even included a x-box controller config so you could see how they control sensitivity... lol.



// /*** *** *** *** *** *** */
// /*** *** *** First Person *** *** *** */
// /*** *** *** *** *** *** */

// Makes the player look straight, as though they never looked up/down.
// Set before switching to certain views, like Top Down View.
// centerview
// force_centerview



// Set FP or TP
firstperson "1"
// thirdperson "1"
// thirdpersonshoulder "1"
// cam_command "1" // 0 FP / 1 TP / Sometimes 2 = Whatever or FP



// Toon looks around, but camera view won't.
// thirdperson_mayamode "1"



// Collision - TP, if camera touches a wall, it zooms in
cam_collision "1"



// Mouse/JOY - Can it pitch/yaw? Useful for say, Side Views...
// M = .022 / Joy = -1.5p 1.0y
m_pitch "0.022"
m_yaw "0.022"
// joy_pitchsensitivity "-1.5"
// joy_yawsensitivity "1.0"



// Set the camera location
cam_idealpitch "0"
cam_idealyaw "0"
cam_idealdist "0"



// What the camera is allowed to do
c_minpitch "-9999"
c_maxpitch "9999"

c_minyaw "-9999"
c_maxyaw "9999"

c_mindistance "-9999"
c_maxdistance "9999"



// Shows what angles the cam has
// cam_showangles "1"

// /*** *** *** *** *** *** */
// /*** *** *** JOYSTICK MOVE/AIM *** *** *** */
// /*** *** *** *** *** *** */

// joy_pitchsensitivity "-1.5"
// joy_yawsensitivity "1.0"

// DO NOT UNBINDALL
joy_name "xController"
joystick "1"
in_initjoy "1" // Quake II/III
in_joystick "1" // Quake II/III/IV
in_joystickLeftStickMove "0" // Quake IV
joyadvanced "1"
joy_advanced "1"
+jlook

joysidesensitivity "1.0"
joy_sidesensitivity "1.0"
// joy_pitchsensitivity "1.0"

// Quake / I think Half-Life
joyadvaxisr "1"
joyadvaxisu "3"
joyadvaxisx "4"
joyadvaxisy "2"
joyadvaxisv "0" // ???
joyadvaxisz "0" // ???

// Half-Life 2
joy_advaxisr "1"
joy_advaxisu "3"
joy_advaxisx "4"
joy_advaxisy "2"
joy_advaxisv "0" // ???
joy_advaxisz "0" // ???

joyadvancedupdate // ALWAYS AT BOTTOM
joy_advancedupdate // ALWAYS AT BOTTOM

bind "R AXIS POS" "+back"
bind "R AXIS NEG" "+forward"
bind "U AXIS NEG" "+moveleft"
bind "U AXIS POS" "+moveright"

bind "Y AXIS POS" "+lookup"
bind "Y AXIS NEG" "+lookdown"
bind "X AXIS NEG" "+left"
bind "X AXIS POS" "+right"

In Quake/HL Tech, you can use
chase_active 1
chase_back 0
chase_right 0
chase_up 0

this can also be explained in this way:

the sensitivity changes both: vertical and horizontal settings at the same time,

and the m_yaw: horizontal, and m_pitch: vertical, changes each of the settings
individually.

do you guys agree?

Mmm

m_side and m_forward commands does the same thing as m_yaw and m_pitch ??

No - they do something similar, but for when you're not using mouselook (which of course you are, so they do nothing).

m_ze_goggles 1
:c

forward rj scripts or anything in general that uses centerview; +lookdown etc. :)

hii guise

what does m_bitch and m_yawn do??




(voices in my head made me post it :( )

so m_yaw 0.018 and m_pitch 0.019 makes the feeling on a 4:3 crt like a 3:3?

no

vertical and horizontal mouse speed is the same by default if not how do i make it equal ?

why anon... why...

ofcourse its the same by default. 0.022 for both.

Dear god I was like "so many numbers in this thread, where is Weird?" I kept scrolling, then I saw the NL flag "AH THERE HE... Oh it's kevz."!

Removed erroneous information re: values, tested again and found that while they definitely appear to affect the 'feeling' of the mouse movement, I can't exactly call it more accurate. Also a bit of a necropost but meh.

what is wrong with your brain

nice necro