-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[Bug] Time Crisis 4 (from Time Crisis Razing Storm collection) gets stuck in the end of "Building SPU cache" screen #15474
Comments
Hi, how to fix this problem?? |
I reproduce this issue since few builds already, on Linux. Dev branch. Last tested on |
If it's a regression, it needs to be reported as such, otherwise the chances of the ticket being picked up are low. Needs to follow the regression issue template instead if that's the case. |
Didn't know it was a regression, it was my first time trying to play this game. |
I have got this issue too, and I have to remove the SPU cache every time to get into the game. |
Issue seems fixed. Tested on |
Nope, the issue is still there. I've just deleted the cache, I was wrong. I'll make a proper report when I get the time. |
Quick summary
When Time Crisis 4 (from Time Crisis Razing Storm collection) is loading, it gets stuck in the end of "Building SPU cache" screen.
Details
When using PS Move, 50 fps limit and Write Color Buffer is ON, Time Crisis 4 (from Time Crisis Razing Storm collection) gets stuck in the end of "Building SPU cache" screen. Deleting the cache will make the game start, but it is impractable to wait loading time everytime.
Edit: I tested with default configuration and then went ticking the options. If my assertion is right, PS Move is to blame in the problem I'm having. Testing every other configuration without PS Move ON didn't result in problem.
Attach a log file
RPCS3.log.gz
Attach capture files for visual issues
No response
System configuration
Windows 11
RTX 3050
i7 11800h
8gb RAM
Other details
Edit: I tested with default configuration and then went ticking the options. If my assertion is right, PS Move is to blame in the problem I'm having. Testing every other configuration without PS Move ON didn't result in problem.
The text was updated successfully, but these errors were encountered: