-
Notifications
You must be signed in to change notification settings - Fork 69
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crosshair sticks into ground with libinput and wayland #1248
Comments
Is CSGO a native Wayland window or does it use XWayland? Could not test it myself because i am using Gnome and the Nvidia driver which does not support Wayland at the moment. With Gnome you can check that by doing ALT+F2 -> "lg". But i guess you are using KDE because you listed Plasma. |
@OlliC Well i'm running steam/csgo inside Plasma Wayland environment, so i guess csgo is still using XWayland. I'll provide later full log when i run csgo from konsole. |
Here is the full log https://gist.github.com/tpgxyz/5c333c4b96ce1c4975615e2c9b7f5e0b |
Found very similar bug on FD.O https://bugs.freedesktop.org/show_bug.cgi?id=84644 |
This is not a Valve's issue, but rather a missing functionality in Plasma. But you can try with GNOME 3.22, it should work. |
Looks like this is pure kwin 5.8.4 ssue as it does not support "pointer constraints" and "ConfinedPointer" features. Looks like future release will do support these. |
I think there must be a lot of performance lose because when I am running csgo/dota under wayland it cause CPU boost to 90°C+, while Xorg 80°C and windows 75°C in same options.… |
When csgo match is running i can not move my crosshair as it is always sticked to the ground.
Move in any direction only spins on left or right, and crosshair is still stuck on ground.
I've noticed that when i enable in-game mouse acceleration, i can move my crosshair, but it strongly leans toward up or bottom, hard to center it.
My system (https://openmandriva.org) is up to date:
Mesa 13.0.2
libinput 1.5.3
Wayland 1.12.0
SDL 2.0.5
Plasma 5.8.4
Kernel 4.8.12
Xorg 1.19.0
The text was updated successfully, but these errors were encountered: