Easy: I don't use acceleration.

Easy: I don't use acceleration.

Easy: I don't use acceleration.

Easy: I don't know how to use the new system.

This lol

Same. I just consider myself lucky I don't use accel (anymore).

Easy: I read the devblog and made the calculations

post your old settings and someone will calculate them for you.. but it wont be the same.

id like to try 2 things:

800dpi
sens 3.5
accel 0.01
yaw/pitch 0.022

and

450 dpi
sens 4
accel 0.1
yaw/pitch 0.018

if you could calculate that for me that would be awesome :)


so with in_mouse 2 and m_cpi 800 does the mouse actually run on 800dpi despite the fact that the driver says 450 dpi?

"so with in_mouse 2 and m_cpi 800 does the mouse actually run on 800dpi despite the fact that the driver says 450 dpi?"

The idea of the m_cpi command is that you tell the game what DPI your mouse has so that when you change your mouse or actual DPI you only have to change m_cpi to get the exact same sens/accel as before.

Also, http://www.esreality.com/?a=post&id=2090830#pid2090830

Easy: I don't bother learning the new system.

Easy: I don't use acceleration.

easy : set it to behave like accelstyle 0

wat

Easy: I have keept the accel settings that I have used the past 8 years.

Easy: I don't use acceleration.

can aim when my crosshair is moving with different speeds :X

Uneasy: ive used style 1, accel 2, offset 5 before. im now at style 0 (does it even matter now if its 0 or 1)? accel 0.1 offset 10

not really able to get the old feeling back tho but these new settings are quite close

For a year or so I've been using Fox's config. Not having known anything about configs at the beginning of my QL "career" I found it comfortable to play with and therefore hardly have I ever obtained any knowledge about it. And now, after the last update I have a strange feeling that something is totally wrong with my sensitivity (to speak generally: with the way cursor behave, not sure if it's sens thing). Literally I am no longer able to move smoothly, let alone aiming... Does anyone have same problems and have possible solution? I just want it to be exactly like it had been before the update took place.

do you have an autoexec.cfg?
then you have to edit this in the file

if you have cl_mouseaccelstyle 0
you just need to set cl_mouseacceloffset to 0
and everything should be fine..

That is probably the solution for lots of people. I've noticed that many player's cfgs contain cl_mouseacceloffset 5 when using cl_mouseaccelstyle 0. This had no effect before the update, but now the cl_mouseacceloffset will kick in with the new unified accelstyle making it seem like the new style is different, but once you set the offset to 0 your accel will be exactly as it was before...

It seems there's no such command like accelstyle :( I simply copied fox's config with no changes at all

fox = 0

the only oddity in his accel/zoomfov stuff was that he used zoomsens 1 ( or whatever the cvar is ) which doesn't scale the accel according to the fov ( for some wacky masochistic reason, some people like their sens scaled but not the accel ).

http://www.esreality.com/index.php?a=post&...pid1955924

the accel always felt completely fucked with zoomsens 1 to me ( no scaling what so ever )

Dont like it, I know this new method might be superrior but there was no reason in removing the old.They could have kept boths styles and let people coose for themselfs.If theire going to continue doing their work like this, then they can remove in_mouse -1/1 aswell, afterall 2(raw) is "superrior" and the rest of inputs are "useless" and there is no need in offset anymore right?I dont play much and I dont have time to figure out these new settings, besides that their calculation method doesent work like it was supposed to.Sensitivity is just "similar" but not quite the same..

well the old isn't really removed, both were merged, and how you set the options decides if you use old q3 accel style or more custom style

cl_mouseaccel your old value
cl_mouseaccelpower 2
cl_mouseacceloffset 0

and it should be the old way like in the beginning/q3

well not quite..

According to SyncErrors formulas that he posted it should be like this:

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

sensitivity "1.6" // Mouse sensitivity
cl_mouseaccel "0.1" // Mouse acceleration
m_pitch "0.015" // Mouse Y-axis sensitivity
m_yaw "0.014" // Mouse X-axis sensitivity
in_mouse "2"
cl_mousesenscap "1.7"
cl_mouseaccelstyle "0"
cl_mouseacceloffset "0.1"
m_forward "0.15"
m_side "0.14"

these are my old settings which means that new ones should be something like this:

sensitivity "14.11023622" // Mouse sensitivity
cl_mouseaccel "0.555521111" // Mouse acceleration
m_pitch "0.023571428" // Mouse Y-axis sensitivity
m_yaw "0.022" // Mouse X-axis sensitivity
in_mouse "2"
cl_mousesenscap "14.99212598"
cl_mouseaccelstyle "0"
cl_mouseacceloffset "0"
m_cpi "1600"

cl_mouseaccelpower "2"

Now if I did something wrong.. please correct me, because this is not the same sensitivity I had before.

EDIT:
You need to ask yourself this.. how many % of people will actually benefit out of this!?You cant expect from a random newbie to know all of this.I understand there were some issues for people having odd mouse bug that changed sens during the games.But theres a vast majority that got adjusted to old sens and are having difficulties to adopt to the new one.Im not saying theres something wrong with it, those that want to use it fine.. use it, but those that dont want to, should have an option.

Isn't m_cpi optional, I don't use it and my settings are as they were before the update (with offset 0).

well you dont use offset so it doesent affect you..

and as for m_cpi, its used in the formula as SyncError posted here:

http://www.quakelive.com/forum/showthread.php...l-Features

Well, someone correct me if I'm wrong, but I think offset worked only with mouseaccelstyle 1 before.

the offset never did anything to style 0 accel.

I am using acceloffset with accelstyle 0. Can I get similar sens/accel with offset 0?

m_cpi 0
sensitivity your old value
m_yaw your old value
m_pitch your old value
cl_mousesenscap your old value
cl_mouseaccel your old value
cl_mouseaccelpower 2
cl_mouseacceloffset 0

as close as it can get..

the formulae are only for people who want to activate the m_cpi feature. it's completely optional.

as long as the new accel cvars are on their defaults, the traditional style 0 accel is unchanged.

if something is different for you then it's either in your head, or something else is causing the difference.

if something is different for you then it's either in your head, or something else is causing the difference.

Please, Im not idiot I can feel the difference.. I cant explain whats causing it maybe its accelpower or smth else, thats why im asking about it?Im saying something has changed and I dont know what even if I use old settings its still different, mouse is faster and I know it is!!Its not in my head or a placebo, sensitivity changed.

faster or more responsive? do you have the same cm/360 as before?

its more "wobbly" accel.. its faster

but have you measured it?

.

you don't HAVE TO use m_cpi
if you set it on 0 you can use your old setup with accelstyle 0 being depreciated

Mouse bug still isn't fixed either

To find the new custom accel you can bring down your console by pressing ctrl+alt+` then type cl_mouseaccel and hit tab. That will show you all the accel commands!

Was waiting for this. Finally [+]´d!