alexhultman
Reactions
Comments
-
Have been trying the game under XFCE on my slow machine (and the new), and they don't get the input bugs in XFCE. However, once I shoot the game crashes every time. So basically the game is still useless and unplayable, unstable. I think it's strang…
-
Will try when I get back to the low end system. I wonder what version of gnome murray used, since old versions had much lower performance for games and thus more likely to trigger the bug (it's much harder to trigger the bug on my high end system, s…
-
Interesting. I wonder if Killing Floor is well written or not. Might be a bug in Gnome (strange, but plausible), but then I'm still left with the crash-once-I-shoot bug.
If the developers could dump their usage of the SDL2 keyboard input… -
Yep but I don't have any other environment and I can't switch to metacity since it's deprecated since gnome 3.6.
Also - it won't be a "solution" since I'm not going to use fluxbox. All other games works and all other software works. Othe… -
cat /var/log/Xorg.0.log | grep mieq
cat /var/log/Xorg.0.log | grep overflow
cat /var/log/Xorg.0.log | grep warning
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
Here is the warning hit:
… -
I have an Intel i7 with Ivy Bridge graphics and NVIDIA GT 650M through Optimus (the game runs through primusrun). Since my other computer doesn't have Optimus but just a regular NVIDIA discrete card the bugs are not dependant on having Optimus. But …
-
The fact that some hits are not registered explains why I'm getting this stuttering when building / running. The game misses that I'm still holding the Shift key down so I stop to run only to start running again when the next key is registered. Ever…
-
Typing in the chat doesn't give duplicated letters but some letter are not registered. If I type the alphabet some letters are missing. It seems very random. If I hit W with regular interval it registers 6 hits, one miss, 9 hits one miss, 3 hits one…
-
I have missed the question on chatting, will test it soon. Sorry for missing that, I think you have edited you message and I have missed it. Here is my system information from Steam:
Processor Information:
Vendor: GenuineIntel
I get the same "auto walking" / messed up keyboard input bugs on my brand new Intel i7 high end system with clean reinstall of Fedora 20 and latest proprietary NVIDIA drivers. So there you have it - I have now reproduced this set of bugs on two comp…I don't have any keyboard emulation software. Can't try US layout since I'm not at the computer now and won't be for a while.Also - I'm using non US keyboard layout. I'm using Swedish keyboard layout.If you have a super computer you could try debugging using Valgrind. I use Valgrind myself and it can be very useful for finding non deterministic bugs that depends on eg uninitialized memory. Hint hint.I run vanilla Fedora 19 updated. Nvidia proprietary drivers as stated above (dont know thr version number off my head). Steam client on Gnome shell 3.8 (all that is vanilla for a Fedora user). I think I'm on kernel 3.11, again vanilla for a Fedora u…Thank you for hinting about using something other than gnome shell. Will try when I have some some time. This sounds like a plausible fix.I tried the game again now and I found antoher major issue. All keys seems to send pairs of DOWN and UP all the time. If I hold W to move forward, or hold E to build, the game behaves as if I was clicking the key repeatedly instead of holding it dow…(Quote)
Yeah similar bugs are often solved by just clicking the key again but in NS2 I cannot do that. It's completely messed up once it happens. Haven't been able to finish the first training mission because I can't walk to the aliens and…There is nothing wrong with my computer and everything else works perfectly. Other games work as they should (Dota 2, Metro: Last Light, Left 4 Dead 2, etc..). None of them have any issues regarding keyboard input (or any other issues for me). It's …