-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Downloaded shader cache crashes Mario Kart 8 on Linux with AMD GPU (RADV) #57
Comments
Same on windows with newest LDM Ryujinx and also with Smash Bros Ultimate Cache. Terminal window says: |
Same for me on the Windows build of Ryujinx 1.1.665 for the latest cached shaders for Mario Kart 8 and Mario Party Superstars. Used to work just yesterday, but refreshing the shaders (for Mario Kart it went from ~34K to ~30K) broke things. |
Running into the same issue on arch (Ryujinx 1.1.625) and my m1 macbook air (Ryujinx 1.1.0-macos1) both Mario Kart 8 deluxe and Super Smash Bros Ultimate |
any fix? |
broken shader cache has been deleted from the server |
Tried this a few moments ago and still seeing a crash Running Mac os Ventura |
same here on macbook air m1, ventura |
deleted mk8 from mac and ssbu from mac and pc |
mk8 still broken on Mac, I noticed the pc one got reset tho |
same error on macbook air m1, ventura |
with me: in latest public build of ryujinx. using VULKAN, on windows, gpu gtx 960 2gb, cpu amd ryzen 1600 af. Shader cache works fine in OpenGL only. |
mk8, smash ultimate, mario party superstars, super mario party broken on ryzen3400g+rx580 vulkan in debian 12 |
Had the same just happen on Windows with MK8. |
The provided shader cache for MK8D crashes Ryujinx LDN during shader compilation on Linux using an AMD GPU (Vega 64) with Mesa's RADV vulkan driver. Possibly a similar situation to #40 ?
Possibly relevant from log:
Full log: Ryujinx_1.1.0-ldn3.1.0_2023-03-09_23-38-54.log
Shader cache works fine in OpenGL mode.
After deleting the cache, Vulkan works again.
Arch Linux
kernel 6.2.2
mesa 22.3.6
ryujinx ldn 3.1.0
The text was updated successfully, but these errors were encountered: