starred/shadPS4

Fork 0

mirror of https://github.com/shadps4-emu/shadPS4.git synced 2026-04-26 08:15:59 +03:00

[GH-ISSUE #3249] [GAME BUG]: Bloodborne screen render issue when "readback" is enabled in recent main WIP 0.10.1 update #1001

New issue

Closed

opened 2026-02-27 21:09:24 +03:00 by kerem · 8 comments

kerem commented

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

Owner

Originally created by @CAPYRUGANG on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3249

Checklist (we expect you to perform these steps before opening the issue)

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.
I have re-dumped the game and performed a clean install without mods and the issue is still present.
I have disabled all patches and cheats and the issue is still present.
I have all the required system modules installed.

Describe the Bug

In recent WIP main 0.10.1 build, when you enable "readback" from the config.toml file, Bloodborne got this issue like shown in the screenshot.
I'm not sure which version started this but the release version of main 0.10.0 doesn't have this problem.
I'm using a ROG Ally X with AMD 780M iGPU, 24GB shared ram with 10GB for GPU use.
This issue is not presented on my Nvidia GPU PC. So I assume it is only affecting AMD GPUs.

Reproduction Steps

Enable "readback" option in config.toml will create this issue.

Specify OS Version

Windows 11

CPU

AMD Z1E

GPU

AMD 780M

Amount of RAM in GB

24GB shared

Amount of VRAM in GB

10GB

Log File

shad_log.txt

Originally created by @CAPYRUGANG on GitHub (Jul 15, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3249 ### Checklist (we expect you to perform these steps before opening the issue) - [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. - [x] I have re-dumped the game and performed a clean install without mods and the issue is still present. - [x] I have disabled all patches and cheats and the issue is still present. - [x] I have all the required [system modules](https://github.com/shadps4-emu/shadPS4/wiki/I.-Quick-start-%5BUsers%5D#4-adding-modules) installed. ### Describe the Bug ![Image](https://github.com/user-attachments/assets/8531ac31-de80-4855-b7b8-3eee98aa31c3) In recent WIP main 0.10.1 build, when you enable "readback" from the config.toml file, Bloodborne got this issue like shown in the screenshot. I'm not sure which version started this but the release version of main 0.10.0 doesn't have this problem. I'm using a ROG Ally X with AMD 780M iGPU, 24GB shared ram with 10GB for GPU use. This issue is not presented on my Nvidia GPU PC. So I assume it is only affecting AMD GPUs. ### Reproduction Steps Enable "readback" option in config.toml will create this issue. ### Specify OS Version Windows 11 ### CPU AMD Z1E ### GPU AMD 780M ### Amount of RAM in GB 24GB shared ### Amount of VRAM in GB 10GB ### Log File [shad_log.txt](https://github.com/user-attachments/files/21239500/shad_log.txt)

kerem closed this issue

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

kerem commented

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

Author

Owner

@IceCreamTuna commented on GitHub (Jul 16, 2025):

Can confirm this issue on the most recent diegolix29 bbfork build with readback and fast readback enabled, this issue mostly happens during area transition or fast movement in area, doesn't happen as much during boss fights.

OS Version
Windows 11 24H2
CPU
AMD 5800x3D
GPU
AMD 7900XTX
RAM
32GB
VRAM
24GB

shad_log.txt

@IceCreamTuna commented on GitHub (Jul 16, 2025): Can confirm this issue on the most recent diegolix29 bbfork build with readback and fast readback enabled, this issue mostly happens during area transition or fast movement in area, doesn't happen as much during boss fights. OS Version Windows 11 24H2 CPU AMD 5800x3D GPU AMD 7900XTX RAM 32GB VRAM 24GB [shad_log.txt](https://github.com/user-attachments/files/21264578/shad_log.txt)

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Jul 16, 2025):

@IceCreamTuna We do not accept tests performed with forks, as we cannot validate the changes they make.
@CAPYRUGANG We do not accept tests with cheats or patches enabled, please retest with all patches (Skip Intro, Disable HTTP Requests, Unlock Game Region, and Resolution Patch (720p)) disabled.

@StevenMiller123 commented on GitHub (Jul 16, 2025): @IceCreamTuna We do not accept tests performed with forks, as we cannot validate the changes they make. @CAPYRUGANG We do not accept tests with cheats or patches enabled, please retest with all patches (Skip Intro, Disable HTTP Requests, Unlock Game Region, and Resolution Patch (720p)) disabled.

kerem commented

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

Author

Owner

@CAPYRUGANG commented on GitHub (Jul 17, 2025):

I tested again making sure there is no patches on at all. Same issue. Only on AMD.
The screen is rendered in half and looks like it has been shifted to the left with the right side of the screen blank/white.
This is the new log:

shad_log.txt

Thank you

@CAPYRUGANG commented on GitHub (Jul 17, 2025): I tested again making sure there is no patches on at all. Same issue. Only on AMD. The screen is rendered in half and looks like it has been shifted to the left with the right side of the screen blank/white. This is the new log: [shad_log.txt](https://github.com/user-attachments/files/21277330/shad_log.txt) Thank you

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Jul 17, 2025):

Thanks, looks like I'm able to reproduce this issue on my end too.
I'll do some digging to see if I can figure out where the regression comes from.

@StevenMiller123 commented on GitHub (Jul 17, 2025): Thanks, looks like I'm able to reproduce this issue on my end too. I'll do some digging to see if I can figure out where the regression comes from.

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Jul 17, 2025):

For reference (and to make this issue meet our reporting requirements), here's an image + log from me testing this.

CUSA00900.log

@StevenMiller123 commented on GitHub (Jul 17, 2025): For reference (and to make this issue meet our reporting requirements), here's an image + log from me testing this. <img width="1282" height="752" alt="Image" src="https://github.com/user-attachments/assets/cf35ee7f-de5c-4fb2-bb44-ea4f4086e52d" /> [CUSA00900.log](https://github.com/user-attachments/files/21277486/CUSA00900.log)

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Jul 17, 2025):

Seems like it's a regression from PR #3238

@StevenMiller123 commented on GitHub (Jul 17, 2025): Seems like it's a regression from PR #3238

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Jul 21, 2025):

@diegolix29 We've warned you numerous times about your fork promotion. Your fork advertisements continue to hide emulation bugs from us developers, due to the sheer number of people who swap to using these hacks instead of properly reporting issues.

Continue this behavior and you will be blocked.

@StevenMiller123 commented on GitHub (Jul 21, 2025): @diegolix29 We've warned you numerous times about your fork promotion. Your fork advertisements continue to hide emulation bugs from us developers, due to the sheer number of people who swap to using these hacks instead of properly reporting issues. Continue this behavior and you will be blocked.

kerem commented

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

Author

Owner

@StevenMiller123 commented on GitHub (Sep 1, 2025):

AMD might've fixed this on their end? I can't reproduce this bug anymore.
I'll close this for now. If anyone with the latest AMD drivers can still reproduce this bug (and provide a valid report of that), I'll reopen this.

@StevenMiller123 commented on GitHub (Sep 1, 2025): AMD might've fixed this on their end? I can't reproduce this bug anymore. I'll close this for now. If anyone with the latest AMD drivers can still reproduce this bug (and provide a valid report of that), I'll reopen this.

kerem referenced this issue

2026-02-27 21:14:17 +03:00

[PR #1001] [MERGED] vulkan: Add alternatives when nullDescriptor is not supported. #1873