in_mouse -1 changes to windows tracking
with high dpi causes neg accel and messes up without 6/11

Ok just saying using in_mouse -1 for me got rid of random positive accel and random negative accel. Both were occuring with in_mouse 2

There is no fix.

QL is mousebugged.

You'll be back.

:D

Not if she goes black.

I'm on Linux and sometimes my sensitivity changes to a much higher value once or twice every game. I created this bind to fix it:

// Restart input.
bind l "toggleconsole; wait; wait; wait; in_restart; wait; wait; wait; toggleconsole; print Input restarted."

Does the sensitivity value change or does the feeling of the sensitivity change?

shits deep

The value remains the same, but the sensitivity becomes much higher.

Same thing happens here. =\

It was much worse for me when I used s_alsa_pcm "default". After switching to "plughw:0.0", it stopped happening as frequently, but still does once or twice every game. Usually in the middle of a fight too. :)

Why not just:

bind 1 "in_restart"

That was my first attempt, but it didn't do nothing. As it did work when I typed in_restart in the console, I tried with the toggleconsole commands before and after (I'm guessing that releasing the pointer may be a part of it), but it only worked after I added the waits (I found about the wait trick when I made a bind to switch from the normal spec hud to comphud). Go figure.

Ain't gaming on Linux wonderful? :)

When you do:

bind [key] "in_restart"

..and press the key, does it output the in_restarted stuff to the console?

How does in_mouse behave on linux exactly? Both dinput (in_mouse 1 on windows) and wm_input (in_mouse 2) are like, microsoft/windows type things.

Also, is in_dgamouse effectual? Do you use the default or have you messed with it or?

Anyways you could shorten that particular script:

bind l "toggleconsole; wait; wait; wait; in_restart; wait; wait; wait; toggleconsole; print Input restarted."

bind I "toggleconsole ; wait 3 ; in_restart ; wait 3 ; toggleconsole ; print Input restarted"

Also I don't have the 'print' command on windows. The one I know of is 'echo', so like:

bind I "toggleconsole ; wait 3 ; in_restart ; wait 3 ; toggleconsole ; echo Input restarted"

Assuming in_mouse works on linux, you should be able to test its value with in_mouseMode as this is the verbose form of the current mouse input setting.

When you do:

bind [key] "in_restart"

..and press the key, does it output the in_restarted stuff to the console?

Yep, it does.

How does in_mouse behave on linux exactly? Both dinput (in_mouse 1 on windows) and wm_input (in_mouse 2) are like, microsoft/windows type things.

This thread explains it. Basically, under Linux, in_mouse only accepts 0 or 1 and enables/disables the mouse. in_dgamouse works, I had to turn it on for a while about a year ago after some Xorg update broke evdev. After that was fixed, I turned DGA off again. (See: https://bbs.archlinux.org/viewtopic.php?id=138322)

Anyways you could shorten that particular script (...)

Thanks for the tip. :)

Also I don't have the 'print' command on windows. The one I know of is 'echo' (...)

You should have the 'print' command on Windows too! It was introduced in the August 6th 2010 update. 'echo' prints to the console and 'print' to the chat log. AFAIK it is available in both OS'.

Assuming in_mouse works on linux, you should be able to test its value with in_mouseMode as this is the verbose form of the current mouse input setting.

Apparently, that cvar (like a few others) isn't available on Linux.

I definitely don't have 'print', and you don't have in_MouseMode. Wild.

So in_restart is buggy on the linux client :-(

Wish the community was allowed to participate in fixing these problems..

That's really weird. (That you don't have print, 'cause not having some feature in the Linux version is not unheard of.) Is it possible that you used the keyword as cvar or vstr somewhere and that's ghosting the command?

Actually, I can't say in_restart is buggy. I didn't go as far as to methodically try all possible input methods under X to the point of isolating and identifying the issue. I'll have to go there if I want to fix this eventually, but currently I just don't have the time, and that would take me to figure out how the X input system work againandIjustcantbearsedfuckit.

Yes, at least some form of public issue tracking system we can commit to and check if the issues were already reported, what workarounds people may have found, etc. Sending people to forums is so 1999.

Ok this is what happened.

I tried it like just loading a map and then disconnecting. Print doesn't exist then.

If I enter a map and use print then it works. Otherwise it reports "unknown command". I guess it's one of those cvars that doesn't exist until a map is entered (there are a few of them).

Well, at least that one's settled.

Print is a really very handy command. Of all people, I thought you'd know about it. :)

Print works for me.

I read "Input RETARDED" at first.

You're almost right! There are a lot of retarded things in the Linux client. ;)

i have a copy of windows you can have.

Thank you for your kind offer, but I have a few genuine copies myself. I just choose not to use them. :)

you like bugs ?

Of course not. That's why I stay away from MS crap.

Well, that's not true in the last ~10 years (XP + Win7) , but whatever. :>

I get this! I aim really well one day, then the next my sens feels totally different despite all my settings remaining the same. I use 400dpi so I'm going to give in_mouse -1 a try. It's so annoying not being able to have any kind of consistency with my aim.

cant play ql cuz of this bs

P L A C E B O
L
A
C
E
B
O

I would have thought the same thing but like I said I tested it. Went from onside of my mousepad until I did a full 360 went from there back to the side I started at and always was about 90 degrees either left or right of where i started.

I had this same issue. It was driving me crazy for a few months. Randomly mouse would feel like it was 1.5x faster like accel was stuck on and I am not using accel. Using in_mouse 2, no accel.

I fixed my issue by:
1) Setting up autoexec.cfg like this
-------------------------------------------
in_restart
exec settings.cfg <---- All cvars in this file, not in autoexec.cfg
-------------------------------------------

2) Issuing a reset from the web settings.

3) Entering a practice game and typing cvar_restart.

4) Exit game.

5) Join Another Practice Map and type exec autoexec.cfg in console.

The above seems ridiculous but it is what finally fixed my sens changes after months of frustration.