[CUSA03173] Bloodborne - [Debug] Critical and more

[GHU7924]

Build - shadPS4 v0.4.1 WIP main 75d2181

I have 2 characters. The first is the main one, the second is the test one.

In the main menu, I chose not to continue the game, but to load the game. As soon as I selected the test character I created yesterday for the test and clicked load, for some reason the emulator crashed, but without errors. I tried again, but the result was the same.

After some attempt, I was able to load the save. I switched between characters and loaded them several times, and I got a critical error.

I took a screenshot, but I forgot about the log file, I'm sorry.

I continued the experiment and was given another error. Here is a screenshot and a log file.

shad_log.txt

I started the game a few more times, and the second error was repeated. Who can test this for yourself, do you have any messages about a critical error.

There is also such a thing:

and the video version

2024-11-09.19-52-06_1.mp4

shad_log.txt

[GHU7924]

Next, I activated 60 fps and the graphic artifacts started:

There were actually more artifacts, but these are enough.

[KrisCris]

#1232
disabling face customization workarounds the issue for now: https://www.nexusmods.com/bloodborne/mods/109

[GHU7924]

#1232 disabling face customization workarounds the issue for now: https://www.nexusmods.com/bloodborne/mods/109

I've already finished the game on version 0.2.1, so mods are not important to me, I'm just testing builds with improvements and fixes in order to help identify problems and give feedback.

If I'm not mistaken, then in version 0.3.1 these problems seemed to have already been solved, I didn't have them, but after the release of 0.4.0 or 0.4.1 something went wrong apparently.

I upgraded to build 7ab8515

Forbidden Woods

2024-11-10.16-10-05.mp4

Shadow of Yharnam

After defeating the boss, a crash occurred and the emulator closed with an error,
I had to fight a second time.

Byrgenwerth

Maybe something is wrong with AJM, I did not understand the pattern, but some of the sounds were gone, here is an example in the video.

2024-11-10.16-27-04.mp4

Forsaken Cainhurst Castle

The cutscene with an error, restarting the emulator, the cutscene with an error, everything is fine for the third time, I got to the location.

In general, after the release of 0.4.0, my performance dropped quite a lot, 2 weeks ago (on version 0.3.1) everything was fine.

[Linear524]

More effects are being discovered and emulated in latest versions, and a lot of new bug cases was discovered as well... Of course it is an early stages of PS4 emulation glory, DEVs just need more time to fix all that stuff.
I see a lot "out of memory" bugs and memory corruption issues as well. Speed is not important right now - only emulation accuracy must be with the top priority. (Speed optimization can always be done later)
Try to disable all the mods (they often breaks some native things, and sfx skipping/changing mods breaks some GPU effects, even if they solve sound/sfx freezing) and test only geometry rendering.

[GHU7924]

Recently, an issue was closed where it was said that the trophies did not appear, I decided to help, so I activated patches in an attempt to recreate the problem on my PC, but I failed to do this, everything was fine and the trophies appeared, but along with this the above problems appeared.

There was a problem with saving, it happened suddenly, I couldn't load the save because it was hanging. On the third time, the save loaded. I was able to continue the game. Then other errors started, so I created this theme.

Now I'm playing without cheats and patches and with a new save (I made a backup copy of the old save and deleted it from the emulator, so now I have a new save created by the emulator), there have been no critical errors so far, but graphical glitches and FPS is sagging (This is the first time this has happened to me.).

2024-11-14.19-19-46.mp4

2024-11-14.19-33-30_1.mp4

These videos are from Build v0.4.1 WIP main 7be35c3.
There are more videos, but they are about the same content, but the graphical errors look different.