-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
[Regression] Async + shader interpreter #16512
Comments
I confirm the issue. It is also present with |
I'll include the fix in #16501 |
Retest with #16501 when the build is ready. |
Seems to be working fine, just Azure pipelines checks saying waiting to report status. So I compiled and checked the async + shader interpreter setting and the shader interpreter only setting as working on my machine. |
Thanks for checking. |
I think the issue can be closed now that #16501 has been merged |
I found that |
This is a regression from the instancing PR and is caused by broken instancing behavior when interpreter is in use. Open a fresh ticket for it, as I'm working to fix it. |
Quick summary
Shader mode Async + shader interpreter now prevents games from booting when used.
Details
Build with regression
RPCS3 v0.0.34-17268-62701154
Attach two log files
17268.log
17267.log
Attach capture files for visual issues
N/A
System configuration
Windows 11
GTX 1660 Super
Ryzen 7 7700x
Other details
Other shader modes for example Async (Multi-threaded) work fine.
I only found this game easy for testing not that it is necessary to use the async + shader interpreter setting because it is not necessary.
The text was updated successfully, but these errors were encountered: