Bug #774

Mouse movement not working

Added by Lammert almost 5 years ago. Updated over 3 years ago.

Status:Fixed% Done:

100%

Priority:ImmediateSpent time:-
Assignee:-
Category:Client
Target version:2.75
OS: Arch:

Description

In some cases it seems that the mouse movement is not working.
This only happens ingame (as spectator aswell as player). In menu it is working.
Mouse click works when this problem appears.

Already found out that restarting sometimes solves the issue, but not always.

Also there is a report that ALT+TAB solved the issue.


Related issues

Related to ET: Legacy Development - Bug #781: Aiming latency problem Invalid 14.01.2015
Duplicated by ET: Legacy Development - Bug #768: ETLegacy Windows 8 weird bug Invalid 10.01.2015
Duplicated by ET: Legacy Development - Bug #808: Mouse inresponsive after install of new release Invalid 04.02.2015

Associated revisions

Revision d30f8662
Added by Jacker almost 5 years ago

client: set the windows process affinity on startup

Revision dcf19e86
Added by Spyhawk over 4 years ago

client: force at least 1 frame_msec value, refs #774

Thanks to Razish (Qtz) for the fix and Ensiform for being awesome

Revision 6bfdd80d
Added by Spyhawk over 4 years ago

general: disabled win32 cpu affinity code, fixes #774

Revision c803e027
Added by Jacker over 4 years ago

properly disabled the affinity code, refs #774

History

#1 Updated by Spyhawk almost 5 years ago

  • Priority changed from Normal to Immediate
  • Target version changed from 2.72 to 2.78

#2 Updated by Spyhawk almost 5 years ago

Responsible commit seems to be d098af23d187f016d8efc752e33e0cad2f752c08.

(Don’t take it as granted, as the issue is quite random and I might have misbisected).

#3 Updated by Spyhawk almost 5 years ago

Setting CPU affinity to the last core only (CPU3 on my quadcore) seems to solve the issue.

#5 Updated by Spyhawk almost 5 years ago

  • Related to Bug #781: Aiming latency problem added

#6 Updated by Spyhawk almost 5 years ago

  • Target version changed from 2.78 to 2.74

#7 Updated by Spyhawk almost 5 years ago

  • Duplicated by Bug #768: ETLegacy Windows 8 weird bug added

#8 Updated by Spyhawk almost 5 years ago

  • Duplicated by Bug #808: Mouse inresponsive after install of new release added

#9 Updated by Spyhawk almost 5 years ago

So I have a good and a bad news.

The good news is that bug doesn’t seem directly related to the code. I was having that bug constantly, with the mouse being stuck after about a minutes of play. Since about ten days ago (5-6 of February), I cannot reproduce this problem. It went from "being always there" to "completely fixed". I tried to bisect the issue without success. I even tried the 2.72 official release (was buggy for me, although it was a bit better than 2.71a) and it works as expected. The fix seems somewhat unrelated to the code.

The bad news is, of course, that I have no single idea why it works now. As far as I remember, when it was buggy I tried to launch etl.exe specifically on 1 single core with a shortcut (with affinity 1), which didn’t really worked. After that, launching etl.exe directly (not through shortcut) was still buggy... and then it suddenly worked the next few days.

tldr: fixed on ma machine, but I don’t know why

#10 Updated by Mateos almost 5 years ago

Under Windows with a Microsoft mouse ? May be a Microsoft Mouse & Keyboard Center update?

Tried to reset the CFG file and try with a new one?

Maybe the OS was hanging and selected to disconnect temporarily the mouse? (happens to me from time to time)

#11 Updated by Spyhawk almost 5 years ago

Mateos wrote:

Under Windows with a Mircosoft mouse ? May be a Microsoft Mouse & Keyboard Center update?
Tried to reset the CFG file and try with a new one?

I’ve always used a new config file. This shouldn’t be hardware dependent, since it happens with my integrated touchpad (no mouse!) and that I haven’t done any drivers update recently.

Maybe the OS was hanging and selected to disconnect temporarily the mouse? (happens to me from time to time)

Maybe.... what could cause this issue?

#12 Updated by The_Loko almost 5 years ago

I still have this bug on Linux

#13 Updated by Spyhawk almost 5 years ago

The_Loko wrote:

I still have this bug on Linux

Could give details about your issue? You’re the first person to have it under Linux, so I suspect this is another bug..

#14 Updated by The_Loko almost 5 years ago

Spyhawk wrote:

The_Loko wrote:

I still have this bug on Linux

Could give details about your issue? You’re the first person to have it under Linux, so I suspect this is another bug..

I think it’s the same, first time It happened was the day this bug was reported.
Most of times, when connecting to a server mouse movement doesn’t work. Alt Tab doesn’t fix it, restarting the game does.
As this one, mouse click works and movement works on menu too.

Also, after playing in a server a lot of maps (around 10), mouse stops working too when loading a new map.

#15 Updated by Spyhawk almost 5 years ago

  • OS deleted (Windows)

#16 Updated by The_Loko almost 5 years ago

I tried 2.72 on my Windows 7 machine and I have the same issue.

#17 Updated by Anonymous almost 5 years ago

Hello,

I am following this issue since the day it was first reported, because I have the same issue too, on Win 8 64-bit.
Some thoughts:
The issue only occures when I update to 2.72. With 2.71a the bug is not there. Maybe I am wrong but the bug must happen somewhere between 2.71a and 2.72.
There are not too much changes between 2.71a and 2.72. Can anyone who can reproduce the bug test 2.71a exe instead of 2.72 exe?
I can’t compile ETLegacy, but if someone could, than it might not be to hard to exactly find out where the bug first occurs (around 24/12/2014 to 08/01/2015, maybe: https://github.com/etlegacy/etlegacy/commit/857efa2ab65adb701906071797561149fdcc67b8)
Hmm, I have no idea if my assumptions are correct, I simply thought maybe this information will help you a bit.

Kind Regards,
ToKu

#18 Updated by Saukko almost 5 years ago

I have been wondering why there haven’t been any investigations after the problem occured.

-*S

#19 Updated by Spyhawk almost 5 years ago

ToKu> The exact commit is known (see #774#note-2 above), but it is still unclear why the bug happens, and why it can suddenly disappear on the very same machine with the very same code (see #774#note-9).

#20 Updated by pisek almost 5 years ago

Spyhawk wrote:

ToKu> The exact commit is known (see #774#note-2 above), but it is still unclear why the bug happens, and why it can suddenly disappear on the very same machine with the very same code (see #774#note-9).

In my case the problem shows up only when running the game with the omni-bots mode. In vanilla etlegacy the mouse works OK.

The mouse works at first OK, but after a minute of play, stops. The problem however is not with the mouse itself because when ESC is pressed, the cursor can be moved; when going back to game the mouse stops...
When I "disconnect" from the server and connect/create it again, it goes again (1min ok, then bump)

I am using:
Windows 7 64bit (clean system)
ET Legacy 2.72

#21 Updated by Spyhawk almost 5 years ago

In my case the problem shows up only when running the game with the omni-bots mode.

Very interesting. I can’t reproduce the issue anymore, but I had the exact same issue as you. could you tell us a bit more about this issue? Were you using a local server, or an online server? Did you use the "launch ETL with bots" shortcut? etc.

#22 Updated by Anonymous almost 5 years ago

@Spyhawk> I had a look at the code (#774#note-2 above). I can’t see anything which seems wrong with that commit, thought I won’t argue against you, you might know more than I, I’m not that skilled and I am no ET Legacy developer. So it is guaranteed that this commit causes the bug?

I can confirm what Pisek wrote: mouse movement will stop working with omnibots enabled (tested on local server, no shortcut).

@Pisek> I’m not sure but to me it seems it mostly happens right after 1st respawn after I was killed for the first time, can you confirm this?

#23 Updated by Spyhawk almost 5 years ago

ToKu wrote:

@Spyhawk> I had a look at the code (#774#note-2 above). I can’t see anything which seems wrong with that commit, thought I won’t argue against you, you might know more than I, I’m not that skilled and I am no ET Legacy developer. So it is guaranteed that this commit causes the bug?

Yes, it is the commit where the bug appears. However, it doesn’t mean that code is directly responsible for it. Likely, it made it appear by triggering something else in another part of the code. Hopefully I’ll be able to reproduce it with playing with OB settings.

#24 Updated by IR4T4 almost 5 years ago

To all players getting this bug:

If this issue occures open console (if that works) and enter:

cvarlist
condump mousebug.txt

You’ll find the mousebug.txt file in fs_homepath. Please attach this file here. Don’t forget to anonymise before (name, GUID etc)

#25 Updated by pisek almost 5 years ago

Unfortunatelly i have it reproduced on non-bot game as well... so no hint here...
But... I have just changed the sensitivity property to some other value and saved the profile, restarted game and mouse worked - so then just changed the sensitivity back to normal.
If the error will happen again i will surely dump the logs:)

#26 Updated by pisek almost 5 years ago

ToKu wrote:

@Pisek> I’m not sure but to me it seems it mostly happens right after 1st respawn after I was killed for the first time, can you confirm this?

In my case the mouse problem was fully random: once just in the beginning as spectator, sometimes after 1min of playing etc so no rule here:/

#27 Updated by belstgut almost 5 years ago

  • Target version deleted (2.74)
  • OS set to Windows
  • Arch set to 64-bit

#28 Updated by Spyhawk almost 5 years ago

  • Target version set to 2.74
  • OS deleted (Windows)
  • Arch deleted (64-bit)

#29 Updated by IR4T4 over 4 years ago

belstgut, your condump on hastebin is gone please attach it as text file.

#30 Updated by Spyhawk over 4 years ago

I can finally reproduce the issue, on Windows only and with other mods than Legacy (reproduced on silent and nitmod so far).
This is not the exact same issue I was facing previously (mouse working but stopping about 1 minute later - as described by pisek above) but it is the one described by many other people (mouse not working at all on connect, and a few /reconnect can solve the issue).

Unlike the previous mouse issue I had, it doesn’t show up in localhost, but does on online servers. However, a new bisect showed that the same commit is also responsible for this issue, so it is certainly the same bug, or a variant of it.

com_minimized and com_unfocused were both set to 0 when this bug happened.

#31 Updated by Spyhawk over 4 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 50

Possible fix pushed in dcf19e86b653df21eb3c62f942a7b9bc3ade5808. Feedback welcome!

Thanks to Razish (QtZ) for the fix and Ensiform for the help!

Note: I’m not sure if the affinity change (d30f8662) is still necessary.

#32 Updated by Zecklar over 4 years ago

The fix is correct.

What happens is division by 0 in CL_Keystate. If frame_msec = 0, in CL_Keystate the line val = (float)msec / frame_sec calculates the result as #IND ( indeterminate ) and in consequence of that, the viewangles ( cl.viewangles ) will be also #IND and so player can’t look around anymore.

#33 Updated by IR4T4 over 4 years ago

  • % Done changed from 50 to 80

#34 Updated by Spyhawk over 4 years ago

  • Status changed from Feedback to Fixed
  • % Done changed from 80 to 100

#35 Updated by watchdog over 4 years ago

Hello,
my mouse didn’t working.

How can i fix the problem

#36 Updated by Mateos over 4 years ago

Either compile the source or wait for the next release

#37 Updated by watchdog over 4 years ago

Mateos wrote:

Either compile the source or wait for the next release

How can I compile the source?

#38 Updated by Spyhawk over 4 years ago

See README file in the github repo. Also, next time please ask question on forums instead of in the bug tracker.

#39 Updated by LenusikAnop about 4 years ago

  • Subject changed from Mouse movement not working to кровь на туалетной бумаге после кала
  • Description updated (diff)
  • Category changed from Client to General
  • Assignee set to Odal
  • Target version changed from 2.74 to 2.78
  • OS set to Pandora
  • Arch set to 64-bit

#40 Updated by belstgut about 4 years ago

  • Subject changed from кровь на туалетной бумаге после кала to Mouse movement not working
  • Description updated (diff)
  • Category changed from General to Client
  • Assignee deleted (Odal)
  • Target version deleted (2.78)
  • OS deleted (Pandora)
  • Arch deleted (64-bit)

#41 Updated by IR4T4 over 3 years ago

  • Target version set to 2.75

Also available in: Atom PDF