SteamOS VS GlosSI

Create a support ticket and reference this GitHub thread. https://github.com/ValveSoftware/SteamOS/issues/1257 it doesn’t effect everyone but it does effect multiple users

Similar discussions: https://github.com/ValveSoftware/SteamOS/issues/1257 https://github.com/ValveSoftware/SteamOS/issues/1281

It happened to me too a few times, mostly with hogwart’s legacy. Maybe it is software related though according to this https://github.com/ValveSoftware/SteamOS/issues/1257, so I have hope to not RMA my deck

Edit: Valve should be aware of this issue by now: https://github.com/ValveSoftware/SteamOS/issues/1235

This is a known issue with the WiFi cards in the OLED. It looks like the chip itself has poor Linux driver support. See here.

Another issue I saw in 3.5 and before was crackling sound (in some games), after sleep/resume. I saw this in Elden Ring and couple of other games. Looks like resetting pipewire program seems to fix this issue. You may have to add a terminal program to steam, switch to "Nested Desktop" or use decky plugin to execute following bash commands.

From the thread on github with bug report you can see two things:

Steam in home streaming does not work with the Deck, in either direction (from the Deck to another PC/phone or from a PC to the Deck) (https://github.com/ValveSoftware/SteamOS/issues/1148)

Try installing glossi on your host system and running it though that https://github.com/Alia5/GlosSI

GlosSI

If it’s a “non-steam” game, like Diablo IV, I use https://github.com/Alia5/GlosSI to act as the non-steam game for the launcher.

Download GlosSI installer from https://github.com/Alia5/GlosSI (when asked to during installation, install ViGEM driver as well)

Check out GloSI and it's Playnite extension, might be easier to assign input per game from Playnite

There are apps that act as middleware between Steam and these 3rd party launchers that can help. I use GlosSI.

You simply can't because there are no Drivers for it and Steam.exe is acting like the driver itself so that even projects like https://github.com/Alia5/GlosSI are piggybacking on Steam.exe's existence. You may try combining that GlosSI + SteamCMD (command line version) for a minimal impact on your system but you can't avoid installing Steam.

Now I assume you are running it through steam to make use of steam input. The workaround to run the launcher independently and still use steam input is to use glossi . Here’s a YouTube video on how to set it up: youtube .