Have you set m_cpi correctly on both standalone and steam?

What Memento_Mori said ^ And is your dpi still the same?
Be sure that you are really using the same config/settings.

Same in_mouse too?

was 100% sure this is a hearztless thread @_@

Same. As we know he cleaned his config. Now it's time for the next step - switch to steam.

There's nothing different about the way the code works at all, the steam version just added login stuff to the client that was done in the launcher before.

I'm guessing maybe you'd set a game profile in the razer drivers to set cpi for quakelive.exe that doesn't exist for quakelive_steam.exe.

I'll double check after work. I'm usually really thorough with this kind of thing though. Hopefully it's something simple like m cpi or razer drivers. Maybe windows 10 installed razer drivers without asking me. I'll let you guys know thx.

>windows 10

Found your problem.

Does razer synapse has some custom profile that can be executed on applications launch? Could be the reason.

You could try to disable accel and use a ruler to make a 360 degree turn and compare.

Edit:

Not fixed.

Sens is still random. All settings are correct. Config is correct. Only default mouse drivers.

If your sens and accel keep getting random, then it's most likely the good old sens bug.
I can't tell you exactly why it's happening (except 'gj id'), but ql basically keeps digging out your old values and sets them as current.
I got rid of that problem by:



Hope this helps.

=(

Different mouse didn't work? :(

If this happens to others, switching to steam, when QL will be steam exclusive - the end is nigh!

Ontopic: did you try other USB ports?

Okay I found out the issue.

It's my two monitors. When I'm on the desktop I use a 40 inch TV, then when I switch to Quake I change my primary monitor to the 120hz gaming screen. Basically this seems to fuck the mouse sens up (even though both screens are the same resolution) If I reboot with my 120hz screen as primary, it's fine. But this never used to happen with stand alone. In fact, if I make this bug happen then quit steam and load stand-alone, the sens is fine. So there surely HAS to be some code difference with input handling. Otherwise how can this be explained? odd =)

Thanks for all the help.

QL, and most certainly its input code, knows nothing about your multi monitor setup.

hi. have you tried in_restart command when experiencing this issue?

Win10 has a lot of issues like that with multimonitor setups atm, steam/ql have nothing to do with it

I believe I experienced this myself last night actually with win10.
I turned on extended desktop to start streaming and I'm sure my sensitivity changed by up to as much as maybe 0.5cm/360

I'll try and look into it some more today and verify it wasn't something else that happened while setting up, there are DPI settings that affected some games in win8 before that ms gave some settings to help with, but that shouldn't really happen with raw input at all, and it certainly wasn't a problem with QL in win8, but that's the only thing I can think of right now to try investigate in win10.

If you are using extended desktop to extend it to the igp's display for OBS, I don't think that's needed for a long time now. I'm myself not really an attention-whore type, so I don't stream my doings to the interwebs, but I was setting up OBS some time ago, so the kid could stream to his friends, and I read it somewhere that enabling the IGP is enough, no actual display is needed.

If you just extending to have a second screen, than just ignore this post:)

yeah, it was only for the second screen, have to keep checking that the stream isn't' stuck on 'awaiting gamestate' as it's prone to do on every single map change, have to alt-tab until OBS wakes up again.

That and see the twitch chat

:)

Yeah I noticed it's not just Quake. It happened in Skyrim too lol. Must be a win10 thing :)

Stuck on awaiting gamestate in OBS happened even more in win8 for me.

I've tried, but haven't actually been able to replicate this yet.

I have noticed this with latest Catalyst drivers. I dunno when this issue started. If you have multiple monitors connected into your video card, even if they are disabled, it severely effects latency and causes input accel issues. You need to disconnect any monitor other than the monitor you are playing on. This is not a QL issue. This issue is present in all games.

You can test this very simply. Confirm your primary monitor is the only enabled monitor in Catalyst, and disconnect the cables to other monitors. Your primary will go black and reinitialize, despite all other monitors being disabled, and you will have normal response again.

It appears to be a Catalyst issue and an inability to actually disable monitors and/or maintain scope on primary.

Check
Mouse dpi
m_yaw
m_pitch
sensitivity
m_cpi
cl_mouseaccel
cl_mousesenscap
cl_mouseacceloffset
cl_mouseaccelpower
cl_mouseaccelstyle
cl_maybeyourbrainhasproblems

i missed a rocket once, should I post on esr about it?


















Getting rediculous.

(using the trailer voice) When Windows goes wrong..... again!