Please mention whether you’re on stable, beta, or a different update channel. There’s a good chance most bugs on the stable update channel have been fixed already, so anyone on the beta update can let people know if the bug they’re facing is already fixed.

      • Ah! I actually meant to do that (saw that on another post), but the second to last Deck update broke Decky Loader’s injection sequence, so I forgot about it in the meantime.

        ETA: the latest Deck update corrected that issue, and Decky works fine, now.

  • The weird jumping/flickering animation when pressing play on a game in gaming mode and “Launching game…” appears.

    Doesn’t have any impact on actually launching the games but it’s just annoying.

    Thought it was Decky at first but I’ve tried disabling it and it still does it.

  • If you turn off your deck being online and then turn it on again somewhere with no internet access, sometimes it will not get past the “looking for updates” screen before loading steam. I’ve had that happen more than enough times. Only way to exit from that loop is connecting to internet, but that’s not always possible.

    • There was a bug with that, caused both by Decky Recorder and by having Valve’s own game recorder turned on. Uninstalling Decky Recorder and making sure the built in recorder is turned off before entering desktop mode seems to fix it.

  • On beta, the two bugs that annoy me the most are both related to docked play.

    • The first one is that pressing home + A on a controller to open the QAM will open it for just a moment before opening the full steam overlay instead. It’s acting like it’s counting it as two home presses.

    • Second one is that every SteamOS update somehow messes up my bluetooth pairing for controllers. The controllers are still listed, but won’t connect. Have to forget them and repair before they’ll work again.

      • Interesting. In my experience when on any Linux distribution I have to decide if I want good Audio quality and not use the microphone of the headset or if I want to use a worse audio code but activate the microphone. I thought this still was a widespread issue, or did I miss something?

        • This is a Bluetooth issue, not Linux or Deck specific. When microphone is enabled on a headset, Bluetooth will switch to a different audio codec. That codec supports one output channel (microphone) and one input channel, so it will be mono audio. The sound quality is good enough for audio calls but not for anything else. The only thing you can do is to disable the microphone. Or, you can do what people have done for couple decades now: complain at Bluetooth Special Interest Group until they improve the standard.

          • Yes it is not Deck specific, but Linux specific. It works on Windows / Android /IOS. And contrary to any other Linux installation, the deck is a commercial product. As a commercial product I want modern Headsets to work properly as they do on other systems. Proper Audio I/O is necessary for any multiplayer game.