Bug report + fix
KOTOR Academy on Steam Deck: working, with one Proton workaround for a controller crash
Hi! Thanks for KOTOR Academy, it's amazing. I got it running on a Steam Deck and wanted to share what I found, since it's untested there.
Setup:
- Steam Deck [LCD/OLED], SteamOS [version]
- Proton: [Proton Experimental / GE-Proton version]
- KOTOR Academy: latest alpha release
- Movie Duels Update 6 + Patch AIO
- Steam copies of KOTOR, KOTOR II and Jedi Academy, copied over from my Windows PC
How I launched it:
The launcher (play.ps1) can't run under Proton, so I added kjk.exe to Steam as a non-Steam game and set the KJK_KOTOR1, KJK_KOTOR2, KJK_JA, KJK_MOVIEDUELS and KJK_CAMPAIGN environment variables in its launch options myself, pointing at a copy of the jedi-academy folder the launcher made on Windows.
What happened:
1. WGPU_BACKEND=dx12: crashes on startup.
2. WGPU_BACKEND=vulkan: starts and runs fine, but crashes as soon as there's any controller input.
3. Fix: adding WINEDLLOVERRIDES="windows.gaming.input=d" to the launch options. With Windows.Gaming.Input disabled, the controller works and the game is playable.
Working launch options (KOTOR I):
WINEDLLOVERRIDES="windows.gaming.input=d" KJK_KOTOR1='Z:\path\to\swkotor' KJK_KOTOR2='Z:\path\to\kotor2' KJK_JA='Z:\path\to\jedi-academy' KJK_MOVIEDUELS='Z:\path\to\movie-duels' KJK_CAMPAIGN=k1 WGPU_BACKEND=vulkan %command%
So it looks like the gamepad code crashes on Proton's Windows.Gaming.Input implementation, but works through the fallback path. A couple of ideas, if they're useful:
- Falling back gracefully when Windows.Gaming.Input misbehaves, or using XInput by default
- A simple non-PowerShell launch option (a .bat or a documented list of the KJK_ variables) for Proton/Linux users
Happy to send kjk.log or a Proton log if that would help. Thanks again!