Skip to content
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

Wayland SDL shows cursor and hits window limits #3856

Open
VolRen-ShYK opened this issue Oct 9, 2024 · 12 comments
Open

Wayland SDL shows cursor and hits window limits #3856

VolRen-ShYK opened this issue Oct 9, 2024 · 12 comments
Labels

Comments

@VolRen-ShYK
Copy link

VolRen-ShYK commented Oct 9, 2024

Your system information

  • System information from steam (Steam -> Help -> System Information) in a gist:
  • Have you checked for system updates?: Yes

I'm using CS 2 natively under wayland. After the last big update it became unplayable. Before this update I was playing quietly for almost a year.

Steps for reproducing this issue:

  1. Go to the game folder and modify cs2.sh. Specifically change x11 to wayland
  2. Go to any server
  3. Sad. :(

UPDATE

This has been happening since the last 4GB CS 2 update, which was released on October 3. When logging into the server I now have a cursor on the screen at all times that restricts mouse movement, meaning I can't turn the mouse further than the cursor, once the cursor touches the edge of the screen there is no way to turn further.

I tried to play on xwayland, but there I often drop fps, also the scope in the game behaves strangely, as if it floats.

2024-10-09-15-29-11_aUgSwhsj.mp4
@VolRen-ShYK VolRen-ShYK changed the title [CS] Wayland problem. [CS2] Wayland problem. Oct 9, 2024
@kisak-valve
Copy link
Member

Hello @VolRen-ShYK, sorry, but you haven't effectively communicated what the issue is that makes the game unplayable for you. Please adjust your opening post to clarify what issue you're seeing and use a more descriptive title, then give me a ping to re-evaluate.

In general, altering cs2.sh and using SDL's wayland backend is not expected to be supported at this time.

@kisak-valve kisak-valve closed this as not planned Won't fix, can't repro, duplicate, stale Oct 9, 2024
@VolRen-ShYK
Copy link
Author

@kisak-valve

@kisak-valve kisak-valve changed the title [CS2] Wayland problem. Wayland SDL shows cursor and hits window limits Oct 9, 2024
@kisak-valve kisak-valve reopened this Oct 9, 2024
@kisak-valve
Copy link
Member

Hello @icculus, this issue report might be interesting to you, but I don't know the internal details to confirm.

@firashacker
Copy link

i had the same issue where the game keeps the cursor on the screen inside the match and you can't exceed screen border limits while you try turning around because the cursor gets blocked by the screen edges

@ZeroYamaoka
Copy link

ZeroYamaoka commented Oct 11, 2024

@kisak-valve hes mean this

Wayland.mp4

@VolRen-ShYK reminder
Zrzut ekranu_20241011_122924
That means Source 2 still didnt support wayland in 100 %

@VolRen-ShYK
Copy link
Author

@ZeroYamaoka Yeah, I realize that. But I wouldn't have written about it if this problem hadn't come up recently. I've been playing smoothly for the whole of this year.

@ParadoxLeon
Copy link

I'm having the same issue.
before the armory update I had no issues using wayland.

playing on x11 is garbage having 200fps and it feels like 60

@dyingwillow
Copy link

same here, KDE Plasma 6.2 on Fedora 40. when switched to Wayland from X11, cursor is visible and stuck in the window limits, but the X11 performance is so flaky that it's still unplayable (for me, atleast)

@Fxzzi
Copy link

Fxzzi commented Oct 13, 2024

Can confirm this issue. With Wayland enabled since one of the recent updates, mouse cursor is visible in game and mouse can hit the limits of the window and block further movements, stopping you from looking around fully.

Edit: for now, I've opted to use gamescope with SDL video driver set to x11. This allows me to use stretched resolution correctly without black bars.

@firashacker
Copy link

i have this issue as well

this need to be fixed since wayland works way better than x11 for some users

@VolRen-ShYK
Copy link
Author

@kisak-valve I apologize for the inconvenience, but wanted to ask you if there has been any progress in resolving this error?

@firashacker
Copy link

@kisak-valve I apologize for the inconvenience, but wanted to ask you if there has been any progress in resolving this error?

its still the same

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants