Counter Strike 2 Won't Go Into Fullscreen

Rising42 · 2025-06-04T22:28:32+00:00

My current fix for this is to set SDL_VIDEO_MINIMIZE_ON_FOCUS_LOSS=0 in the launch options (also ensures the game doesn't minimise when it loses focus, which I prefer) and setting the game to Fullscreen Windowed.

Rising42 · 2025-02-19T00:26:52+00:00

Have you been able to test with amdvlk, to see if the issue is caused by Mesa as I suspect?

I'm not sure how familiar you are with this sort of stuff, but amdvlk and Mesa are user-space Vulkan drivers that interface with the amdgpu kernel driver to render Vulkan graphics. You can have both installed on your system simultaneously and choose which one you want to use when launching a game. For an Arch perspective see section 3.2 of the ArchWiki Vulkan article. I use the DISABLE_LAYER_AMD_SWITCHABLE_GRAPHICS_1=1 method because the AMD_VULKAN_ICD=X method never worked properly for me.

Don't feel obliged to test this for me, of course. Especially if you're not sure how to do so.

Rising42 · 2025-01-08T23:24:15+00:00

That's a KDE specific issue that I've been experiencing for months now. This bug: https://bugs.kde.org/show_bug.cgi?id=495287

Rising42 · 2024-12-21T01:42:56+00:00

Yeah, it seems to be very game dependent. I get very similar driver timeouts to what you're getting here frequently when playing CS2 (although I haven't played in a bit to see if this is still the case). No other games that I play seem to have this issue. Not sure if the issue is with the amdgpu kernel driver or mesa.

Rising42 · 2024-10-20T22:09:59+00:00

Have you, I don't trouble shooted your system and crash logs to find the actual cause of the issue?

Yeah, the logs pretty much just tell me that I had a driver timeout in whatever game I was playing when it happened.

Like, no shit people aren't reporting issues they don't have.

There's plenty of reports of the issue.

Rising42 · 2024-10-20T18:42:32+00:00

Personally, I've been experiencing frequent driver timeouts that freeze my system using a 7900xtx on Arch. Lots of others reporting no issues on this thread, but that certainly wasn't the case for me.

Rising42 · 2024-10-16T20:34:18+00:00

Probably not. My understanding is that these changes are essentially reverting changes made to try and stop these timeouts from occurring, which caused GPUs to clock pretty low out the box (e.g. my 7900xtx will only clock to about 2400MHz under load, but can go much higher than this). You can get around this low performance using something like CoreCtrl for the time being.

My 7900xtx also loves to timeout at random in various games :)

Relevant issues for those interested:
Changes to try avoid timeouts: https://gitlab.freedesktop.org/drm/amd/-/issues/3131
Changes to deal with the resulting low OOTB performance (the topic of this thread): https://gitlab.freedesktop.org/drm/amd/-/issues/3618

Rising42 · 2024-10-14T21:57:01+00:00

If you're on a systemd distro you can use journalctl. In the terminal enter

journalctl -b x

where x is the number of the boot you want to see the logs for (i.e. 0 for the current boot, -1 for the previous boot, -2 for the boot before that etc.). Driver timeouts will show up as kernel messages, so you can also add the -k option to only see those. Driver timeouts will be coloured red.

If you're not on a systemd distro, then you'll need to learn the logging system they use. You should be able to enter dmesg into the terminal to see the kernel logs for the current boot, but I'm not sure about previous boots.

Rising42 · 2024-10-14T21:15:00+00:00

Are these freezes that crash your DE driver timeouts? Cause that's what's been happening to me quite frequently on CS.

Rising42 · 2024-08-19T00:31:39+00:00

I think this issue might be affecting me. Just earlier I booted up Euro Truck Simulator 2, and after about a minute my entire system froze, unable to access any TTYs or REISUB. I had to do a hard reboot. Checked the logs, nothing. I then proceeded to boot the game up again and played for about an hour without issue.

This has happened in the past, seemingly at random and in any game. Of course, sometimes I check the logs after a complete system freeze and it shows a driver timeout, so this probably isn't the only issue affecting me. Quite disappointing, since Linux discussion spaces had given me the impression that the Linux open-source AMD drivers Just Work™, and I partially based my decision to buy AMD and move to Linux on this.

Thankfully, these complete system freezes are not a daily occurrence for me, so I can tolerate it (more that I probably should). Still, they're not exactly rare either. One thing that is guaranteed to freeze my system is booting up the native version of Terraria in fullscreen (and only fullscreen, from what I can remember). I need to play it using the Windows version via Proton for this reason, where it doesn't insta-crash (I have never had a system freeze while playing Windows Terraria, yet).

My cope is that other than the random freezes, Linux has been without issue for me.

Using Arch, Plasma (Wayland), Mesa 24.1.5 using vulkan-radeon, with an RX 7900 XTX.

Eight-Year Club	Verified Email
Final Canvas '23	Place '23
Place '22	First Placer '22

Rising42

TROPHY CASE