someone asked me this years ago. it is possible to setup a source game to be the same as quake, but as the source engine's acceleration is framerate dependent, you MUST have a constant framerate in the source game, else it will fluctuate.

first set sensitivity, m_yaw and m_pitch the same as quake.

then in the source game set m_customaccel 1 and m_customaccel_exponent 1.

the last two settings are,

m_customaccel_max = cl_mouseSensCap

m_customaccel_scale = cl_mouseAccel * fps / 1000


where fps is your framerate in the source game, not in quake.

If m_customaccel_exponent is something other than 1, you cannot equate the two methods.

what would be equivalent sensitivity?
if this works, I might finally play portal

set sensitivity, m_yaw and m_pitch the same as quake

source actually blocks the editing of pitch(but not yaw lol?), is there a way to convert the equivilent accel/sens into .022 format?

I think it should be just a ratio, so sense 4 at 0.22 is sense 2 at 0.44

i believe it affects accel differently though

would be good to know... also, why is .22 the default?

~0.022 = (360 / 65536 ) * 4

Assuming the engine uses 65536 for the maximum possible iterations of a 360 degree turn, an m_yaw of (360 / 65536) with sensitivity 1 would mean one of these iterations per mouse count.

The guys at id (HL ran goldsrc which was modified from a quake engine, and later goldsrc evolved into source, and I guess some characteristics like this were kept) found early on that this m_yaw made for ridiculously low sens, so they increased it by 4. This made the sensitivity numbers much more "normal" , like 2-4-8 etc.

With sensitivity 1, m_yaw x changes the view by x degrees per mouse count.

didn't think ANY original quake C/win code would remain after all the iterations of re-writes with moving to C++, directx and all :)
I think I still have the HL2 leaked engine sources somewhere, I should do some searching and check.

lol was that leaked?
EDIT: LOL nice bump.......

hl2 code was leaked in like 03. valve scrapped the entire project and started over

oh didnt know that. Do you have a source for it? is the code still out somewhere?

This may be of some relevance

https://github.com/ValveSoftware/source-sdk-2...e.cpp#L396

yaw happens here

https://github.com/ValveSoftware/source-sdk-2...e.cpp#L484

well the SDK is not the complete sourcecode? or?

Yeah thats generally the case, but that chunk of code looks very similar to what happens in quake3.

https://github.com/id-Software/Quake-III-Aren...put.c#L420

Heres the quake3 equivalent line to the 2nd link in my previous post

https://github.com/id-Software/Quake-III-Aren...put.c#L458

http://www.eurogamer.net/articles/2011-02-21-...-2-article

Thanks :)

new_sens = old_sens * ( old_pitch / new_pitch )
new_accel = old_accel * ( old_pitch / new_pitch )

new_yaw = old_yaw * ( new_pitch / old_pitch )

where new_pitch would be 0.022 if it's fixed by the engine.

So true.

no i idea why I missed that
why do they coincide exactly, getting passed on to directx or something?

You don't need mouse accel to play Portal. You could play it with a fist up your ass and still it'd be one of the best gaming experiences you've had in a while

not my cup of fisting, but im glad youd enjoy that

So m_customaccel_exponent 1 means what exactly? Power of 2?

In ql with mouseaccelstyle 0, what value should be set so that moving the mouse twice as fast results in twice the sensitivity? How does sens/yaw affect this?

1) yes.

2) setting your sensitivity to zero, and using any value of accel will get you that behaviour. not sure why you would want to do that though.

Was hoping for something a bit more... mathematical.

Oh, nice, thanks!

Shame I don't get a consistent framerate in Source. I wonder why these companies keep creating accel code that is framerate dependent.

yeah, well they're not really doing it on purpose. it's because you cant tell whether a piece of code has framerate-dependent behaviour just by looking at the code - you need to do some analysis first.

as developers try to do more complicated scaling algorithms, it's more likely they will accidentally break the conditions required for framerate-independence, to which they are oblivious.

Maybe if enough people e-mail valve they'd fix it!

How much will your sensitivity fluctuate on the source engine if you're dropping frames? Enough to warrant not using it?

For example, I cap at 120 but in some fights I drop to 60-70's

off the top of my head, the base sensitivity will stay the same, but the acceleration will fluctuate proportionally to the frametime.

so a drop from 120 to 60fps will double the accel.

So then, theoretically speaking, it will fluctuate to try to accomodate in the drop of frames in an attempt to normalise the acceleration?

If so, then it shouldn't feel to different to the user.

Hope i'm understanding this right.

No, the real accel will fluctuate, i.e. you will *feel* twice the accel in reality.

it is broken. it's not like q3-style accel which does keep track of the frametime to give a constant feel across different framerates.

Following this formula the more u have FPS the more u need accel, this is wierd.

Lower fps results in more mouse movement per frame, which would result in a greater amount of acceleration.

Interresting, ty.

l4d has an accel command, as far as I can tell it's the same as quake 3.

Command is m_accelsomething2 or something.

injx, any idea if m_mouseaccel1 or m_mouseaccel2 in source engine are frame dependent? I've never actually tried to use them.

these cvars:

m_mouseaccel1
m_mouseaccel2
m_mousespeed

control the windows registry settings for the old windows pointer acceleration.

they are nothing to do with the engine's internal mouse accel.

these vars wont have any effect if windows pointer accel is disabled/nullified or if you are using raw input. they should be regarded as obsolete.

but cs source added raw input some weeks ago, so , doesn't these make it frame-independant?

no.

the way the game obtains its input (pointer or raw) is a completely separate issue and doesn't change anything i have said in this thread.

It's ironic that the game where everyone gets constant 125 fps isn't framerate dependent for accel, and the game where a lot of people don't get 125 fps is. :(

what about offset?

nice bump

Config fraggers.

none of your question matters...u won't be any better than you are now

accelstyle? fps cap?

it's funny when newbies are so concerned about customization when they can't even do anything.