CS2 - Linux i3wm 4:3 exclusive fullscreen issue

[SolsticeSpectrum]

Your system information

• System information from steam: system info gist
• Have you checked for system updates?: Yes

Please describe your issue in as much detail as possible:

There is an small issue when it comes to the Linux build of CS2 running on i3 window manager. If you set the game to 4:3 exclusive fullscreen mode (not the windowed one) and restart the game, the game starts windowed next time. My best guess is that it fails to call the correct fullscreen handler? This doesn't happen with CS:GO, the game does correctly starts as fullscreen.

Now this issue has one big problem with it. When I then press mod+F to fullscreen the window, all text gets pixelated, the game starts rendering in a weird way. This also has effect to mouse input as in match it is very choppy and laggy propably due to the mouse pointer technically running outside the window or something. To fix it I always have to go to settings and quickly switch from exclusive to windowed and back or change the refresh rate back and forth to update the fullscreen mode and only then it sets correctly.

Again this wasn't happening in CS:GO so there must be some tiny incompatibility with tiling window managers. Thank you for reading this issue and I hope it will get fixed soon.

Steps for reproducing this issue:

1. Set resolution to 4:3
2. Set fullscreen (not windowed fullscreen)
3. Restart the game

[SolsticeSpectrum]

@kisak-valve Not sure if the bugfix which makes CS2 prefer X11 over Wayland should have an effect on this issue but I wanna report that this is still a problem, adding to that another person seems to have same issue https://github.com/ValveSoftware/csgo-osx-linux/issues/3454

[k4rli]

Same issue, 4:3 800x600 as windowed or fullscreen in CSGO settings is unplayable after mod+F fullscreen. Mouse movements are absolutely broken.
Only way is to play 2560x1440@144 fullscreen (native). That doesn't launch really as fullscreen either and I need to manually set with mod+F. It launches with slightly offset to top of screen, moving it down slightly will be "fullscreen windowed" so only mod+F fixes the launch.

[SolsticeSpectrum]

Same issue, 4:3 800x600 as windowed or fullscreen in CSGO settings is unplayable after mod+F fullscreen. Mouse movements are absolutely broken. Only way is to play 2560x1440@144 fullscreen (native). That doesn't launch really as fullscreen either and I need to manually set with mod+F. It launches with slightly offset to top of screen, moving it down slightly will be "fullscreen windowed" so only mod+F fixes the launch.

mod+f breaks mouse movement. You're better off switching between refresh rates. When applying, it forces the game to go fullscreen properly. Do that until you see the buttons and fonts become smooth. Then you know it's proper fullscreen and mouse will work correctly.

[k4rli]

mod+f breaks mouse movement. You're better off switching between refresh rates. When applying, it forces the game to go fullscreen properly. Do that until you see the buttons and fonts become smooth. Then you know it's proper fullscreen and mouse will work correctly.

Truly a case where game can be blamed for shots missing. That way does get proper fullscreen and it's sad they've broken it with this CS2 beta release, previously CSGO worked perfectly with 1.5x FPS.

[day-mon]

Is there any update on this?

[SolsticeSpectrum]

Is there any update on this?

No

[day-mon]

Is there any update on this?

No

Lol so just so I understand i3 users can only play native or is there a workaround?

[k4rli]

Looks like they just fixed it, for me it starts in actual fs by default now.

[SolsticeSpectrum]

Still not fixed on i3wm on Arch Linux 😩😩

[SolsticeSpectrum]

@kisak-valve Can I do something on my side in order to provide more info and help the dev team in evaluating the issue? It seems like this issue has been fixed in some window managers but probably not tiling ones. I can post my entire DE setup or something, are there some logs that would be helpful?

[SolsticeSpectrum]

This is what the console says when I force fullscreen by switching between refreshrates. Explanation: The game doesn't run in fullscreen when launched but changing video settings (not the fullscreen settings) seem to cause the game to call the fullscreen function again and it somehow works this time. It just doesn't work when launching the game.

It would be useful if the game had some logging during startup to figure out what exactly fails there. The console also throws these errors, maybe some of this causes fullscreen issues? I will create separate issue for this because it could cause different issues too

[k4rli]

Looks like they just fixed it, for me it starts in actual fs by default now.

Ok this was only because when game is started with i3bar hidden, then it will be able to take up full screen space. A small bit still leaks onto the 2nd monitor though and switching 144->120->144hz ingame fixes it.

[SolsticeSpectrum]

@kisak-valve They fixed it with latest update, fucking finally!

@k4rli @day-mon can you guys confirmed? If yes, I'll close this issue!

[k4rli]

For me it still launches like this without being actual fullscreen so I still need to change 144->120->144hz to fix it https://i.imgur.com/3xpdokW.png

Launch options: %command% -sdlaudiodriver pipewire -novid +rate 128000 -freq 144 -refresh 144 -nojoy -fullscreen -w 2560 -h 1440. Removing -fullscreen -w 2560 -h 1440 doesn't change anything

[SolsticeSpectrum]

For me it still launches like this without being actual fullscreen so I still need to change 144->120->144hz to fix it https://i.imgur.com/3xpdokW.png

Launch options: %command% -sdlaudiodriver pipewire -novid +rate 128000 -freq 144 -refresh 144 -nojoy -fullscreen -w 2560 -h 1440. Removing -fullscreen -w 2560 -h 1440 doesn't change anything

Try using SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 %command%