[GH-ISSUE #2983] [APP BUG]: 0.9.0 Release table isn't booting Bloodborne #947

New issue

Closed

opened 2026-02-27 21:09:05 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 21:09:05 +03:00

Owner

Originally created by @GabrielXP76 on GitHub (May 24, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2983

Checklist

I have searched for a similar issue in this repository and did not find one.
I am using an official build obtained from releases or updated one of those builds using its in-app updater.

Describe the Bug

I am trying to boot bloodborne on 0.9.0, did all the steps and it doesn't boot the game, i already put some time trying to solve this issue on the help section at the shadps4 discord, but unfortunally we couldn't solve it, if someone can help me i would apreciatte, i don't understand why this is happening, i still play on the 0.6.0 table and it still works

My specs:
Ryzen 5 5500 Six Core
RX 6600 8GB
16 GB RAM DDR4 3000mhz

Reproduction Steps

i tried multiple things, such as changing the log to async and back to sync, creating portable user folder, creating myself the play_time.txt, bcs the emulator ain't creating this file by itself, i did disable the Bloodborne game patches, reinstalled shadps4 from scratch, and none of this works,here are the shad log's

shad_log (2).txt
shad_log (1).txt
shad_log.txt

Expected Behavior

No response

Specify OS Version

Windows 10

CPU

Ryzen 5 5500 Six Core

GPU

RX 6600

Amount of RAM in GB

16 GB

Originally created by @GabrielXP76 on GitHub (May 24, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2983 ### Checklist - [x] I have searched for a similar issue in this repository and did not find one. - [x] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. ### Describe the Bug I am trying to boot bloodborne on 0.9.0, did all the steps and it doesn't boot the game, i already put some time trying to solve this issue on the help section at the shadps4 discord, but unfortunally we couldn't solve it, if someone can help me i would apreciatte, i don't understand why this is happening, i still play on the 0.6.0 table and it still works My specs: Ryzen 5 5500 Six Core RX 6600 8GB 16 GB RAM DDR4 3000mhz ### Reproduction Steps i tried multiple things, such as changing the log to async and back to sync, creating portable user folder, creating myself the play_time.txt, bcs the emulator ain't creating this file by itself, i did disable the Bloodborne game patches, reinstalled shadps4 from scratch, and none of this works,here are the shad log's [shad_log (2).txt](https://github.com/user-attachments/files/20421114/shad_log.2.txt) [shad_log (1).txt](https://github.com/user-attachments/files/20421113/shad_log.1.txt) [shad_log.txt](https://github.com/user-attachments/files/20421115/shad_log.txt) ### Expected Behavior _No response_ ### Specify OS Version Windows 10 ### CPU Ryzen 5 5500 Six Core ### GPU RX 6600 ### Amount of RAM in GB 16 GB

kerem closed this issue

2026-02-27 21:09:06 +03:00

kerem commented

2026-02-27 21:09:06 +03:00

Author

Owner

@Randomuser8219 commented on GitHub (May 24, 2025):

"Usu rio"
It looks like the characters in your user name are confusing shadPS4.

@Randomuser8219 commented on GitHub (May 24, 2025): "Usu rio" It looks like the characters in your user name are confusing shadPS4.

kerem commented

2026-02-27 21:09:06 +03:00

Author

Owner

@kalaposfos13 commented on GitHub (Jun 29, 2025):

There has been no activity on this for over a month. If the issue still stands and you haven't already joined, join our Discord server to resolve this.

@kalaposfos13 commented on GitHub (Jun 29, 2025): There has been no activity on this for over a month. If the issue still stands and you haven't already joined, join our [Discord server](https://discord.gg/bFJxfftGW6) to resolve this.

kerem commented

2026-02-27 21:09:06 +03:00

Author

Owner

@Randomuser8219 commented on GitHub (Aug 3, 2025):

Please test with the latest main, #3377 removed the assert

@Randomuser8219 commented on GitHub (Aug 3, 2025): Please test with the latest main, #3377 removed the assert