the acceloffset 0 helped for me....... i just hate the lg i hit enemies spot on they dont die they shaft at me 2sec i lose 200/100 :(

so learn how to move, hitting as much as possible is not so important if u take 40% shaft back

i know how to dodge just looks like my hitbox is as big as an elephant, also get railed from all angles even newbies with 14% accuracy hit me....

:D:D

i know how to dodge

just looks like my hitbox is as big as an elephant, also get railed from all angles even newbies with 14% accuracy hit me....

so it looks like you actually don't

i knew someone was gona say that.. :)

thx bst for the info, sense feels fine.. just looks like my "hitbox" is lagging behind me.. dont know how to explain..

but mostly still get all the kills and do lots of damage in CA..

yea or it could be that QL is just a genuine piece of shit, ex:
http://dl.dropbox.com/u/7295110/qlnetcode.avi

positioning is important too, if you are in the wrong place, you can be lg'd easy but you can't lg back... also the person who gets the initiative usually gets the kill with the lg, extra health can easily be used up in turning around, switching weap, aiming, etc.

If your accel feels too fast, then try lowering it. But seems to me you can now lower specific areas of your accel. So the question is, where is it too fast? If you're comfortable with the feel of the 180's and 360's you do in game, then you can try these settings:

cl_mouseacceloffset will make it so you need more force to begin accel, which is useful if you only want the top end of your accel for 180's but aren't so interested in accel when in lg battles.

cl_mouseaccelpower - you can set it so it will accelerate a lower accel (ie 0.05) at a faster rate. So you could set your cl_mouseaccel to 0.05 and make it so at low mouse movement you get 0.05 accel, but when you move your mouse fast its more like 0.1 accel. (that happens with mouseacccelpower set higher than 2)

I think thats how they work anyway ;) thats what it feels like

could anyone please explain the cl_mouseaccelpower (and offset)?

Today the sens/accel felt wrong, and I played around with it:

(wmo, 2.9 sens, default yaw/pitch,accel 0.169, style 0, no senscap, no offset)

I thought that cl_mouseaccelpower=0 + cl_mouseaccel 0.169 would be the same thing of cl_mouseaccelpower 2 (the default value i think) + cl_mouseaccel 0, but they seem to be very different, although it might be just in my head.

It's definitely different from the "beforeupdate" anyways.

Oh, and could you please elaborate more on the offset, especially when you say: "[...] which is useful if you only want the top end of your accel for 180's [...]" ?

read the devblog

accelpower stems from the mathematical term "power" x^2 = power, that way it affects the acceleration strength (how the curve looks actually)

acceloffset defines when acceleration begins to work
let's say: sens 4 acceloffset 8
that means you have to accelerate beyond sensitivity 8 to see acceleration at all

thanks for the info regarding the offset
As for the power, I'm aware of the fact it's x^2 by deafault, I just have no idea what's the "x" in the equation: is it my cl_mouseaccel value? is it the sens?

2 is the power, and thus the value, that is changeable via mouseaccelpower

style 0 accel hasn't changed at all, so it should be exactly the same.

have you been playing with m_cpi?

accuracies are the same for me, but the feeling of the mouse is much more loose
it's too fast when moving slowly for me...had to half the cl_mouseaccel to 0.05 @ 400 dpi to get the same "speed"
but tracking is still too lose and my sense of flicking is totally gone now

all standard/default values (offset 0, power 2, yawpitch 0.022, deprecated style 0)
sens 4 accel 0.1 now 0.05

I'd say keep your fucked up mouse feeling, it's the only thing that doesn't make me look even worse ingame than I already do.

ok, somewhere it was mentioned that horizontal and vertical movement were untied or tied for acceleration calculations in the engine

only true for the old style 1 or for style 0 too?

and can you fix it injx?

style 1 accelerated two axes independently. doing this produces undesirable behaviour.

style 0 does it correctly.

k ty injx

llol

I'm having same problem :(

My sensitivity is fucked. ya ya, cl_mouseaccelpower 2 / cl_mouseacceloffset 0


STILL FUCKED.

It is NOT the same as before the update. I went from 42+ lg to 30.

TO 30 PERCENT.

The tracking doesn't work right, it feels like it is sticky and slow and unresponsive, it aint me. its quake.

How do i fix this?
sensitivity 4.65
m_yaw 0.014
m_pitch 0.015
m_filter 1
cl_mouseaccel .45
cl_mouseaccelpower 2
cl_mouseacceloffset 0

I figure its the mousebug raping me even harder, so i want to try m_cpi.

M_cpi 800
so my sens with above settings = ???

read the changelog and do it yourself ???

with m_cpi set to the correct value, sensitivity is degrees turned per cm afaik. good luck trying to figure that out :)
http://phoon.us/mouse may or may not help.

but it said m_yaw needs to be 0.022.. mine is 0.014 .. so i dunno what to do

no, it does not say that. change the m_pitch/m_yaw to your liking.

eg.: if you'd want to play with a sens that let's you do a 360° over 25cm, /sensitivity should be 360/25=14.4 degrees per cm.

that is, if i understood any of it.

m_cpi 800
sens 20.5
accel 0.63
power 2
offset 0
yaw 0.022
pitch 0.024

with the default values ("old settings"), is accel in any way influenced by m_cpi and sensitivity?

in other words: if i'd set m_cpi to 2000 will i have to use 0.00xx accel values or does it "scale" in some way? i'd love to use 400dpi accel values with whatever m_cpi is set, but i guess that's wishful thinking.

if you change the value of m_cpi it will change the strength of the sens/accel. but if your actual cpi changes in the same way then the feel will be constant (e.g. 400cpi and m_cpi 400 compared with 800cpi and m_cpi 800).

m_cpi is only ever supposed to be set to either 0 or <your cpi>.

if you're talking about the numbers being 'nice' then for normal setups the numbers tend to be fairly nice. if you get weird values like 0.0003 then that's a reflection of your setup being weird.

if you're using m_cpi, then i'd say typical values for sens are 5 - 50, and accel 0 - 1.

now that's pretty cool. thanks, that is exactly what i wanted.

the idea was to set m_cpi to either 0 or "my cpi", sorry for the confusion.

eg.: current setup is what would be sens 4.05 accel 0.1 with 400dpi and recalculated for 900. i will switch to m_cpi 900 with /sensitivity 14.03 and /cl_mouseaccel 0.1 now :)

cool, note that both the sens and the accel values need to be converted so those settings will be something like sens 14 and accel 0.05.

ok, i need some help then.

i thought it was:
400dpi: /m_cpi 0 /sensitivity 4.05 /cl_mouseaccel 0.1
= 900dpi: /m_cpi 0 /sensitivity 1.8 /cl_mouseaccel 0.02

= 400dpi: /m_cpi 400 /sensitivity 14.03 /cl_mouseaccel 0.1
= 900dpi: /m_cpi 900 /sensitivity 14.03 /cl_mouseaccel 0.1

but you are saying it's:
m_cpi 900 and /cl_mouseaccel 0.02 (0.1/2.25² ~ 0.02)? :/

neither. it's

400dpi: /m_cpi 0 /sensitivity 4.05 /cl_mouseaccel 0.1
= 900dpi: /m_cpi 0 /sensitivity 1.8 /cl_mouseaccel 0.02

= 400dpi: /m_cpi 400 /sensitivity 14.03 /cl_mouseaccel 0.05
= 900dpi: /m_cpi 900 /sensitivity 14.03 /cl_mouseaccel 0.05


just as sens becomes deg/cm, so accel becomes deg.sec/cm^2

thanks, heh :)

i'm getting old, should've been able to figure that out on my own. have a [+] :p

my settings:

sens 1.80
accel 0.07
yaw 0.022
pitch -0.022
accelpower 2
accelOffset 0
mouse cpi 450

After calculating m_cpi I got this:

new sens: 7,015
new accel: 0,001

Am I doing something wrong here ?

the sens is correct, but the accel is 0.048.

Ah right. Thanks.

do you mind explaining how you did the accel part, again? i'm still confused, because i don't end up with your values.

i got this to work with:
old_sens: 1.8
old_accel: 0.02
m_cpi: 900

new_sens (degrees/cm): (m_pitch * dpi in cm * old_sens) = new_sens
(0,022 * (900 / 2,54) * 1,8) = ~14.03
new_accel (degrees/cm²): 0.05

how did you get there? :/

the formulae are in the devblog:

new_sens = old_sens * (old_yaw * m_cpi / 2.54)
new_sensCap = old_sensCap * (old_yaw * m_cpi / 2.54)
new_accel = old_accel * ( old_yaw * (m_cpi/2.54)^2 ) / 1000
new_pitch = old_pitch * (0.022 / old_yaw)
new_yaw = 0.022

for the accel it is

new_accel = 0.02 * ( 0.022 * (900/2.54)^2 )/1000
= 0.055

thanks :)

It doesn't feel exactly right, but my lg is back up to 39% now, the sticky feeling when dragging my crosshair slowly is gone now with m_cpi set at 800.

Could you perhaps give me the numbers for 400 dpi mouse?

Just so i can test that too..

if you're using m_cpi and you change the cpi on your mouse, all you need to do is change m_cpi - the other settings remain: thats the whole point.

what happens when u do m_cpi 800 but ur dpi is actually 1600 or vice versa ?

then the sensitivity number wont be deg/cm, it'll be off by a factor of 2, and similar for the accel settings.

thank you sir for your quick, concise answers

The higher your ping goes, the more noticeable it will be. Feels really strange.
Also your rockets start from your hitbox which is where you was some 100+ ms before. You can even hear the doppler effect from your own rockets if going +forward fast enough.
Your pov is now completely decorelated from your hitbox.

youtube or didn't happen

lol at you accel noobs with problems

no accel 4life yo!

quiet you!

shouldn't you be busy teaching the levelup crew how to pronounce 'deus' properly for dreamhack?

haha i thought that

"duece" ??? ain't tennis m8

the de should be as if you were saying deity but then with the oos at the end

highfive!

Man, I thought I understood this new system for sens/accel. Going to have to try and contact czm and hire him to explain it to me. My head hurts. :(

I experienced the same.... still don't have the answer how to fix it. In the end I just started getting used to it. But it definitely is more sensitive.

To me it seems more responsive and better. Maybe it's just because i don't get the sens bug and the feeling is consistent.

only thing I changed was acceloffset, and everything was back to normal.

I made a spreadsheet for everyone still having trouble, based on injx's formulas. I beta tested it with the settings here and it works.

https://public.sheet.zoho.com/publish/sharpe1337/calc-1

Works fine, thanks.

http://www.quakelive.com/forum/showthread.php...post141600


^^ your thoughts please, cause I don't seem to get any answer there.
Thanks.

power is meant in an idealistic, philosophical way
either sensitivity is multiplied with a high enough factor*dpi (internal sens) or just a 1 is added to it so it is always > 1

just mathematical stuff you shouldn't worry

All I want to have is the old accel back:

I used to have sens 3,5; accel 0.01 (800dpi)

seta sensitivity "3.5"
seta cl_mouseAccel "0.01"
seta cl_mouseAccelPower "2"
seta cl_mouseSensCap "0"
seta cl_mouseAccelOffset "0"
seta m_cpi "0"

Would this be the same as pre-update?

That's what I'm wondering, do you only have to convert previous accel values if you're using m_cpi?

yes, using m_cpi "actualcpi" you have to do this (posted on dev blog):

new_accel = old_accel * (0.022 * (900/2.54)^2)/1000
new_sens = old_sens * (0.022 * 900/2.54)

if you set it to 0 it *should* stay the same.

so do I actually have to change something or can I just neglect it with my settings?

if you were using style 0 it shouldn't be any different.

Accelent!! That's part of what I was mixed up about, thank you!

I don't understand what it is with Quake and mouse accel. Nobody in any other game I've ever played even considered using accel. :/

It just seems like it would be nothing but detrimental to muscle memory.

no other game requires the same kind of dynamic mouse movement that accel benefits

you just have to find something you like and get used to it, you're already using several different speeds for all your standard moves anyway ( flickshots, 90°, 180°, rj and the list goes on )

Apparently it doesn't, as many pros use it. If you can find a sensitivity without accel where you shaft/rail well, your awareness is good and so are your rockets, just stick to it.

cl_mouseaccel 0

You're welcome.

so i just got my wmo and decided to use the new commands

i use 38cm / 360° with no accel so its easy for me to get my old sens back, but something seems to be wrong with my calculations (probably the m_cpi value)

if m_cpi is set correctly, then sens = ° / cm, in my case 360 / 38 = 9.47
i have a wmo 1.1a so i set my m_cpi to 400
*fixed

turns out i need something like sens = 13.6 to have 38cm / 360°, how can that be? where is the error?

The error is that you're not using in_mouse 2 tbh.
Also, most recent wmo and ie3.0 models use 420ish dpi sensors. Dunno if that's even relevant but even know I can't be arsed to take a look at that m_cpi gimmick.

i am using in mouse 2
meaning i shouldnt do the windows correction, my bad

edit: okay using m_cpi = 420 and the calculated sens for 38/360 works. cool, thanks

m_cpi is set to the dpi of your mouse or 0 to turn it off, otherwise you are missing the point of it and the windows sens shouldnt matter if you play with in_mouse 2