You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to reproduce:
add slippi launcher to steam
select vulkan or don't apply -no-sandbox to launch options
Launch slippi through gamemode/game ui
Steam Deck crashes
Suspected issue: perhaps the mesa/vulkan layers provided in the appimage is ancient and this issue may be mitigated by updating this (take with a grain of salt as I have personally never developed an appimage before)
The text was updated successfully, but these errors were encountered:
the same happen on my laptop with a Ryzen 5700, so I guess it s more a specific AMD issue on linux. I use the package available in the aur and I don't think I use the app image one. I can t active vulkan without crashing. wich wasn't happening on my fix where I had an Nvidia card but i don't remember if I run it with the no-sandbox parameters at least I did at one point
I use Vulkan on my steam deck, but it crashes about 70% of the time and it takes several tries in order for it to work.
When it does work the game runs smooth as butter.
Slippi works in desktop mode perfectly fine every time when running Vulkan.
OpenGL runs consistently in gaming mode, but I can't get a consistent framerate.
I am just glad someone else had the same issue as me lol.
From what i have seen and experience it may be related to wayland and windows manager and compositor. For me it carsh if i let the option full screen activated but if i force a resollution then when it s launch i put full screen then it work. IT may be related to default option for window that are in the garphic section. For me it s the automatic resolution that crash the whole things
Steps to reproduce:
add slippi launcher to steam
select vulkan or don't apply -no-sandbox to launch options
Launch slippi through gamemode/game ui
Steam Deck crashes
Suspected issue: perhaps the mesa/vulkan layers provided in the appimage is ancient and this issue may be mitigated by updating this (take with a grain of salt as I have personally never developed an appimage before)
The text was updated successfully, but these errors were encountered: