-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
TROPHY CRASH Reappeared Bloodborne #1511
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
Comments
Also Is there any way to quick reset my trophies for testing? |
And hello again)) It seems that this is not the problem, but this build has many other problems that I wrote about (and will add) in #1509. 2024-11-09.21-30-27.mp4I really don't know what your problem might be related to, but maybe you have something with the save file? Try to start a new game and create a new character with a different name, defeat the Cleric Beast, you can use cheats to speed up the process. |
Try deactivating the Resolution Patch (2560x1080) (21:9 2.37). |
I updated to build 7ab8515 On the boss of Shadow of Yharnam, after the victory, there was a crash and the emulator closed with an error, I had to go through the boss a second time, the trophy did not display, but at the same time I received it (I may have received it for the first time, but due to a glitch it didn't display). Next, I had these trophies: 2024-11-10.16-29-15.mp42024-11-10.16-50-21.mp4What do you have here? I don't remember about the values highlighted in red, whether this is an error or not. |
Uh oh!
There was an error while loading. Please reload this page.
Hello again, I setted up latest ver of shadps4 and found out how I can reproduce trophy crash: gaming without 30 fps fix causes crash, but when i lock fps on 30 with fix game feels good and I can obtain trophy without crash.

So Im curious is it my personal hardware problem(8700k +gtx1080) or i can somehow run game without that issue? Log seems to be the same
shad_log.txt
Also I recently got recommended sys_modules but it doesnt change anything.
The text was updated successfully, but these errors were encountered: