[Solved] Booting the game up causes Steam to crash/deck to reboot

[Sykes]

EDIT: Solution was Steam OS Beta causing the crashes (not client, but OS). Switching OS to Stable fixes it for now.
---
I was playing the game just fine recently. I played a little bit back on my desktop PC, but otherwise I've done nothing to my Deck. I booted it up the next day and now KH3 causes the whole Steam Deck to restart, and in Desktop mode it simply crashes Steam.

I have tried 3 different Proton versions, I've tried reinstalling the game, I have cleared the shader cache and compatdata, I have tried the Preview and Stable channels for the Deck and nothing has worked so far. (Editor's note: I was wrong about this, I tried the client NOT the OS Stable version)

Is anyone able to play it normally right now? Was there a recent update like, yesterday, that is causing this? Or is this familiar to anyone? I searched tons of threads but this particular crash I couldn't find info on.

[Ranko]

Similar issue is happening to me and I think it related to a steam update. Because I tried it in desktop similar to you and got the same issue

[Ark1anux]

same here kh3 and 0.2 wont start

[Ark1anux]

The solution is switch to stable version of steam os this solve the problem. It works for me :)

[Sykes]

Originally posted by Ark1anux:

The solution is switch to stable version of steam os this solve the problem. It works for me :)

Yeah I had tried setting Steam Client to stable, but I had indeed forgot to switch the OS back to Stable. That fixed it for now. It must have been a very recent Beta update that broke it, so hopefully it gets fixed soon.

[crash fan razer63]

is it just me, or did this game update recently, have 2 mods and did not crash even without the mod that prevents crashing on steam version.

[Sykes]

Originally posted by crash fan razer63:

is it just me, or did this game update recently, have 2 mods and did not crash even without the mod that prevents crashing on steam version.

a Steam Client update is causing it. Reverting the client (or OS) to Stable should fix it. It might have been fixed already but I am sticking to stable and it works for me now.