Scaling / using 4:3 on 16:9 Screen

[NickTheOnlyNeko]

When i try to use 4:3(Stretched) resolution on my 16:9(1080P) screen the scaler or something makes it look like someone just smeared Vaseline all across my Monitor, on CS:GO it worked perfectly fine but in CS2 there's a weird issue where the GUI and Scaling looks as if it's having Astigmatism and everything is double vision, I really don't know how to explain it because it's a really weird bug/glitch/issue, oddly enough it does get fixed by using GameScope but then I end up having mouse and keyboard input lag and other unwanted side effects

[zFgVn-1]

x11 or wayland?

[NickTheOnlyNeko]

x11 or wayland?

so far i've only tested it on Wayland cause i'm using KDE on Fedora and by Default Fedora uses Wayland

[zFgVn-1]

Cs2 is natively x11 for now, you can change to wayland session via cs2 launch options type SDL_VIDEO_DRIVER=wayland %command%

[NickTheOnlyNeko]

Cs2 is natively x11 for now, you can change to wayland session via cs2 launch options type SDL_VIDEO_DRIVER=wayland %command%

the issue still kinda persists, the text is less "Crisp" and more blurred if that makes any sense, in CSGO it didn't turn Blurry from what i remember.

(4:3)

(16:9)

[rsalus]

Cs2 is natively x11 for now, you can change to wayland session via cs2 launch options type SDL_VIDEO_DRIVER=wayland %command%

You used to be able to do this but the video driver is currently hardcoded to x11. @NickTheOnlyNeko, look for a file called cs2.sh. Look for the line that says export SDL_VIDEO_DRIVER=x11 and change x11 to wayland. See my gist for more info. This should fix the input lag you're noticing.

[NickTheOnlyNeko]

Replying to #4280 (comment)

Hi, I'll give it a try tomorrow or some time later cause I'm away from PC for now.

Also honestly I still wonder why no one has attempted to create a GUI for gamescope, like a simple and easy to use GUI that let's you select the Game, Resolution, etc and once you're done and ready you just save the settings and press play, something like Lutris how it has its per-game settings and how you can configure things like DXVK versions and what none, I'd make it my self but to be honest and fair my C/C++ Skills are very weak and when it comes to using something like the QT Tool Kit or GTK Tool Kit I'll end up being lost😕

[zFgVn-1]

Replying to #4280 (comment)

It's not hardcoded I literally changed to wayland like that in launch options and it works SDL_VIDEO_DRIVER=wayland %command%

[rsalus]

Replying to #4280 (comment)

Sorry, but you're wrong. See #1470 and this thread. You can check your cs2.sh file yourself.

[zFgVn-1]

Replying to #4280 (comment)

There is Wayland support in SDL but a recent (7/30/2025) attempt at
allowing SDL to default to Wayland caused a number of customer issues so
keep the default at X11 for now. Don't override any user setting so
people can easily use Wayland if they want.

if [ "$UNAME" == "Linux" ]; then
	if [ -z "$SDL_VIDEO_DRIVER" ]; then
		export SDL_VIDEO_DRIVER=x11
	fi
fi

[rsalus]

Replying to #4280 (comment)

Yes? Exactly my point? The launch options are not user settings, thus the script overrides them.

[zFgVn-1]

Replying to #4280 (comment)

Yes? Exactly my point? The launch options are not user settings, thus the script overrides them.

So why i play in wayland if i didn't change in cs2.sh x11 to wayland?

[rsalus]

Replying to #4280 (comment)

Yes? Exactly my point? The launch options are not user settings, thus the script overrides them.

So why i play in wayland if i didn't change in cs2.sh x11 to wayland?

I suspect you aren't 😃
Most distros have x11 installed as a legacy fallback.

[sand-r]

Replying to #4280 (comment)

Sorry, but you're wrong. See #1470 and this thread. You can check your cs2.sh file yourself.

No they aren't wrong. Lunch options override whatever is set there.
SDL_VIDEO_DRIVER=wayland %command% works still.

[rsalus]

Replying to #4280 (comment)

Sorry, but you're wrong. See #1470 and this thread. You can check your cs2.sh file yourself.

No they aren't wrong. Lunch options override whatever is set there. SDL_VIDEO_DRIVER=wayland %command% works still.

Don't know what to tell you, running xeyes and xprop tools both show x11 is being used without editing the cs2.sh even with that launch command. You can clearly see the export is hardcoded and the OOP suggests that script overwrites launch commands.