#Crash when DualSense controller is connected to system [Linux, Stable and Nightly b3138]

3 messages · Page 1 of 1 (latest)

placid temple
#

I am running YARG on Linux on a Steam Deck with stock SteamOS (Arch). I typically play my Steam Deck docked with an official Valve dock and play with a DualSense (PS5) controller connected via Bluetooth, launching games using the Steam Deck's Gaming Mode.

When I try to launch YARG with the DualSense connected via Bluetooth, it crashes on launch after the Unity splash screen.

If I don't have the DualSense controller connected and I launch the game, it will launch successfully. Then at any point if I turn on the DualSense controller and it connects via Bluetooth, the game pops up the "device connected" toast and then crashes immediately after that.

  • This happens in both the latest Stable and Nightly builds (latest one I tested is b3138) as of this post.
  • It happens regardless of what other input devices are connected or disconnected at the time.
  • It happens in both Gaming Mode and through the Steam app in Desktop Mode.
  • It happens with Steam Input enabled or disabled.
    • With Steam Input enabled, it happens regardless of what controller profile I have the DualSense set to.
  • It happens even when Steam is completely closed in Desktop Mode.
  • It happens when YARG is launched directly from its executable or from within the YARC Launcher.

I tried to be thorough but would be happy to perform any troubleshooting steps or testing and provide any logs or additional details as requested.

Thank you.

civic anchor
#

I had the exact same issue with my Steam Deck, same situation and everything. I no longer use the Steam Deck, but I have since switched over to a custom PC build running the latest version of Bazzite and still have the exact same issue. Both my DualSense controller and Wiitar (over Bluetooth) continue to crash the game after the Unity splash screen. As of me commenting this, the latest builds that I've tested are the current Stable build and Nightly b3347. I also checked the logs, and nothing shows an error.

acoustic bay
#

I have the exact same issue except with xbox controllers