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
In my HW it happens with Vulkan renderer and Shader Interpreter only shader. R3 immediately crashes with device lost when loading any chapter (black screen and freeze with device-lost logged in the GUI).
That report is more to troubleshoot the device-lost issue in case you can reproduce the issue with that given example I found on R3 while testing Shader Interpreter only shader.
the hang is also present on an AMD iGPU (my laptop). In that case the AMD control panel popups an error message asking to report the crash to AMD. There is no issue at all reported on the RPCS3's GUI. Don't know if you were able to reproduce the issue so you hopefully can fix the issue (maybe the root cause is the same of the general device-lost reported on different games)
I can reproduce. However this is not the same cause of the device lost error observed elsewhere. This is just a hang (shader end could not be found within X seconds so the driver kills it). An interpreter is a program that runs another program inside it so that's not totally unexpected. The same is not possible with a recompiled program though. If it had no exit the recompiler itself would have crashed. It's more likely some poorly implemented interpreter instruction wrecked the virtualized shader state.
Likely broken flow control. The GPU hangs for a few seconds then gets kicked by TDR.
The text was updated successfully, but these errors were encountered: