this issue disappeared for me after uninstalling and reinstalling the game 🙃

I've found that using env --unset SDL_VIDEODRIVER %command% for the launch options fixes this, at least in my case. Probably this issue is due to running the game under Wayland as I use sway.

@spiwocoal no issues with either sway or plasma wayland, the game launches normally without any extra parameters, but in my case I could verify that that environment variable wasn't set to anything anyway. Running echo $SDL_VIDEODRIVER in your terminal should let you know if your system is defining some value to it.

@simifor in my case, SDL_VIDEODRIVER is set to wayland, which according to https://wiki.libsdl.org/SDL2/FAQUsingSDL is the appropriate driver when running under a Wayland compositor.

I get these artifacts whenever I switch virtual desktops on GNOME or exit fullscreen mode through Alt+Tab:

Playing the game in windowed mode and resizing the window whenever it happens fixes it (at least temporarily). Attempting to run the game with gamescope makes it crash on launch, just like mentioned in this issue. Artifacts are not present when the launch options are set to love Balatro.exe; echo %command%.

Tried with the following Proton versions, all of them have this issue on my system:

• Proton Hotfix
• Proton Experimental
• Proton 10.0-1 (beta)
• GE-Proton-9-27

As for system details:

• GPU: RTX 3060
• Video driver version: 570.144, open-dkms
• Kernel version: 6.12.27-1-lts
• Desktop environment: GNOME 48.1 under Wayland, might check if it also happens on GNOME X11, KDE or Hyprland soon and report back
• Full system information: gist

Edit: did some more testing, the artifacts are not present when running under Hyprland - however the game takes a really long time to load (i'd say a solid minute in a black screen). this did not happen on GNOME

@kisak-valve, Yeah, I guess it did start happening after I installed my second GPU. I'll look into it!

@kisak-valve - This works!

My 3090 is actually my G1 GPU, not my G0 GPU (the RTX 5090 GPU). Once I added __NV_PRIME_RENDER_OFFLOAD_PROVIDER=NVIDIA-G1 to the launch settings, it started working!

Incidentally, Vulkan games seem to work fine without any manual tuning... I guess all of my OpenGL games are affected though...

Actually,

NVIDIA-G1 doesn't seem to be listed by xrand, though NVIDIA-G0 does... Using NVIDIA-G0 didn't work but NVIDIA-G1 did, so that's a win, I guess? The "Provider 1" GPU is definitely the sink though.

xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x1b7 cap: 0x1, Source Output crtcs: 4 outputs: 8 associated providers: 1 name:NVIDIA-0
Provider 1: id: 0x358 cap: 0x2, Sink Output crtcs: 4 outputs: 7 associated providers: 1 name:NVIDIA-G0

I've found that using env --unset SDL_VIDEODRIVER %command% for the launch options fixes this, at least in my case. Probably this issue is due to running the game under Wayland as I use sway.

Dude I love you

@kisak-valve - This works!

My 3090 is actually my G1 GPU, not my G0 GPU (the RTX 5090 GPU). Once I added __NV_PRIME_RENDER_OFFLOAD_PROVIDER=NVIDIA-G1 to the launch settings, it started working!

Thanks! that helped for me too - also dual GPU setup, after launching the window looked like some broken screenshot of steam page.

Note for further readers, I had to enter this into launch options (including the command part):

__NV_PRIME_RENDER_OFFLOAD_PROVIDER=NVIDIA-G1 %command%

My output from xrandr (also no G1):

$ xrandr --listproviders
Providers: number : 2
Provider 0: id: 0x1b7 cap: 0x1, Source Output crtcs: 4 outputs: 8 associated providers: 1 name:NVIDIA-0
Provider 1: id: 0x34c cap: 0x2, Sink Output crtcs: 4 outputs: 7 associated providers: 1 name:NVIDIA-G0