[GH-ISSUE #1641] [Aggregate Issue] Bloodborne - Various bugs/Known problems on each platform #556

New issue

Open

opened 2026-02-27 21:06:53 +03:00 by kerem · 57 comments

kerem commented 2026-02-27 21:06:53 +03:00

Owner

Copy link

Originally created by @Hermiten on GitHub (Dec 1, 2024).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1641

This topic is updated regularly (Last one: 25.Sep.2025)

Welcome to the aggregate issue about Bloodborne.
The goal is to centralize all the issues that concern Bloodborne so as not to have dozens of open topics, to be able to more easily follow the resolution of this, also help newbies to understand and then ShadPS4 is not exclusively dedicated to Bloodborne.
Feel free to improve this one, if you have any suggestions, etc...

Caution

• This emulator is in alpha stage, it's unstable and a lot remains to be done
• We only support tests performed on builds downloadable here: https://github.com/shadps4-emu/shadPS4/actions

Every platform

Important

Using patches/mods can create in-game problems. We do not support their use and tests must be carried out without them.

• VRAM Overusage
• Dark spots (INTEL) #1594

Windows specific

• Crashes on Intel CPUs (12th gen and up) #3220

Compatibility thread: Click here

Linux specific

Compatibility thread: Click here

macOS specific

Bloodborne can now start with the latest commits but in a very early stage.

Compatibility thread: Click here

Unofficial Setup Guide

Guide: How to set up Bloodborne on ShadPS4

Originally created by @Hermiten on GitHub (Dec 1, 2024). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/1641 # _This topic is updated regularly (Last one: 25.Sep.2025)_ Welcome to the aggregate issue about Bloodborne. _The goal is to centralize all the issues that concern Bloodborne so as not to have dozens of open topics, to be able to more easily follow the resolution of this, also help newbies to understand and then ShadPS4 is not exclusively dedicated to Bloodborne. Feel free to improve this one, if you have any suggestions, etc..._ > [!CAUTION] > - This emulator is in alpha stage, it's unstable and a lot remains to be done > - We only support tests performed on builds downloadable here: https://github.com/shadps4-emu/shadPS4/actions ## Every platform > [!IMPORTANT] > Using patches/mods can create in-game problems. We do not support their use and tests must be carried out without them. - [ ] VRAM Overusage - [ ] Dark spots (INTEL) #1594 ## Windows specific - [ ] Crashes on Intel CPUs (12th gen and up) #3220 Compatibility thread: [Click here](https://github.com/shadps4-compatibility/shadps4-game-compatibility/issues?q=is%3Aissue%20state%3Aopen%20label%3Aos-windows%20Bloodborne) ## Linux specific Compatibility thread: [Click here](https://github.com/shadps4-compatibility/shadps4-game-compatibility/issues?q=is%3Aissue%20state%3Aopen%20label%3Aos-linux%20Bloodborne) ## macOS specific _Bloodborne can now start with the latest commits but in a very early stage._ Compatibility thread: [Click here](https://github.com/shadps4-compatibility/shadps4-game-compatibility/issues?q=is%3Aissue%20state%3Aopen%20label%3Aos-macOS%20Bloodborne) # Unofficial Setup Guide [Guide: How to set up Bloodborne on ShadPS4](https://docs.google.com/document/d/1o4g4bR7bPYKhlgKyKS4KsYn8YDxrllfwQMvo0r3pd6Q/edit?tab=t.0#heading=h.gjdgxs)

kerem added the

Bloodborne

label 2026-02-27 21:06:53 +03:00

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@GHU7924 commented on GitHub (Dec 1, 2024):

It was high time to do it))

Edit: @Hermiten It is also worth adding:
Builds downloaded from here are taken into account: https://github.com/shadps4-emu/shadPS4/actions

<!-- gh-comment-id:2509818543 --> @GHU7924 commented on GitHub (Dec 1, 2024): It was high time to do it)) Edit: @Hermiten It is also worth adding: Builds downloaded from here are taken into account: https://github.com/shadps4-emu/shadPS4/actions

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@GHU7924 commented on GitHub (Dec 1, 2024):

So, friends! I'm telling you about the fun of playing Bloodborne on Steam Deck OLED.
We all thought that the game did not work well on the Steam Deck, but we were deceived))
It turns out that there is just a problem that prevents the game from going normally,
you don't need mods for this, it's enough to do a few actions if you endure))

SteamOS Stable (recent updates).
Build: shadPS4 v0.4.1 WIP HEAD f658fc5

Emulator Settings:
Enable Fullscreen
Is PS4 Pro
Vblank Divider = 2

Patches:
Skip Intro
Disable Chromatic Aberration
Disable Motion Blur
Disable HTTP Requests
Force Enable Old Hunters DLC

This kind of thing meets me (lasts for several seconds, maybe 10), it changes every time I start))




then the gray screen for a couple of seconds, then there were video (Intro, but later I put a Skip Intro patch).

I started a new game, I don't remember the first time or the second time I got into the game... (there was a hang-up on character creation or not... I forgot).
When creating a character, the game seems to hang (it may actually happen), but in fact it may be a hoax,
the game loads for a long time, after maybe 20-30 seconds everything passes, Then a semblance of a character appears. You can set up and start the game.

At this stage, the game may freeze and close, but when we start the game again, we can continue.
We get to the clinic, there are no many walls, no enemies, etc., the FPS is very small, but I got to the lamp and fell into the hunter's dream.

Next, what I did in the game was pick up the initial weapon, then, ATTENTION, I took off my clothes and immediately put them on. (By the way, as you can see, the clothing icons are not displayed, although the equipment is there.) And our character is now updated. Then, perhaps this does not always happen, but walls, enemies and the rest began to appear.
So it looks like the initial problem is really related to the initial clothes of the character's clothes.
By the way, in the store you have the opportunity to buy a new suit, so its icons are displayed normally (if I remember correctly).

I also tried to move to Central Yarnam and the clinic.

For those who have a Steam Deck, check it out. As soon as you arrive at the clinic, immediately take off all your clothes and put them back on.
(If you then go to the main menu and boot up again, then everything seems to reset and you need to repeat the steps.)

I also uploaded my saves and here are screenshots from Forsaken Cainhurst Castle.
I appeared normally.

Then it happened.

I took the clothes off my torso and put them back on, but after a few seconds there was a malfunction.

I also attach a log file, there is an error at the end.

shad_log.txt

In general, it is necessary to repair the initial equipment or something related to it.
Or the problem is in the clothes that are put on the torso, because it is she who disappears.
If the game does not load after 30 seconds, then most likely it will close after another 20.

I seem to have said everything I wanted to say, if I haven't forgotten anything.

<!-- gh-comment-id:2510229352 --> @GHU7924 commented on GitHub (Dec 1, 2024): So, friends! I'm telling you about the fun of playing Bloodborne on Steam Deck OLED. We all thought that the game did not work well on the Steam Deck, but we were deceived)) It turns out that there is just a problem that prevents the game from going normally, you don't need mods for this, it's enough to do a few actions if you endure)) SteamOS Stable (recent updates). Build: shadPS4 v0.4.1 WIP HEAD f658fc5 Emulator Settings: Enable Fullscreen Is PS4 Pro Vblank Divider = 2 Patches: Skip Intro Disable Chromatic Aberration Disable Motion Blur Disable HTTP Requests Force Enable Old Hunters DLC This kind of thing meets me (lasts for several seconds, maybe 10), it changes every time I start))     then the gray screen for a couple of seconds, then there were video (Intro, but later I put a Skip Intro patch). I started a new game, I don't remember the first time or the second time I got into the game... (there was a hang-up on character creation or not... I forgot). When creating a character, the game seems to hang (it may actually happen), but in fact it may be a hoax, the game loads for a long time, after maybe 20-30 seconds everything passes, Then a semblance of a character appears. You can set up and start the game. At this stage, the game may freeze and close, but when we start the game again, we can continue. We get to the clinic, there are no many walls, no enemies, etc., the FPS is very small, but I got to the lamp and fell into the hunter's dream.    Next, what I did in the game was pick up the initial weapon, then, ATTENTION, I took off my clothes and immediately put them on. (By the way, as you can see, the clothing icons are not displayed, although the equipment is there.) And our character is now updated. Then, perhaps this does not always happen, but walls, enemies and the rest began to appear. So it looks like the initial problem is really related to the initial clothes of the character's clothes. By the way, in the store you have the opportunity to buy a new suit, so its icons are displayed normally (if I remember correctly).     I also tried to move to Central Yarnam and the clinic.     For those who have a Steam Deck, check it out. As soon as you arrive at the clinic, immediately take off all your clothes and put them back on. (If you then go to the main menu and boot up again, then everything seems to reset and you need to repeat the steps.) I also uploaded my saves and here are screenshots from Forsaken Cainhurst Castle. I appeared normally.  Then it happened.  I took the clothes off my torso and put them back on, but after a few seconds there was a malfunction.  I also attach a log file, there is an error at the end. [shad_log.txt](https://github.com/user-attachments/files/17970171/shad_log.txt) In general, it is necessary to repair the initial equipment or something related to it. Or the problem is in the clothes that are put on the torso, because it is she who disappears. If the game does not load after 30 seconds, then most likely it will close after another 20. I seem to have said everything I wanted to say, if I haven't forgotten anything.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@norbertkeri commented on GitHub (Dec 3, 2024):

There is an issue where most of the sound effects (weapons hitting, using blood vials, etc) stop playing if you force-quit the game without going to the main menu. I can reliably reproduce both the problem and the fix, so if you ever have an issue with disappearing sounds: start the game, and then quit to the (ingame) menu, and then close the emulator. The next time you start it, sounds will work again. I assume the problem is related to the warning message that pops up when you start the game if you haven't closed it properly.

The other problem I encountered is that the "item glow" from defeated mobs do not appear. When I walk over the corpse, the "press X to pick up loot" prompt appears and works, it's just the graphics that are missing. I have tried the Tess branch referred to in the first post, and it didn't work there either.

Apart from these two things, the game seems to run surprisingly well and stable with some minor glitches, but I only played up until the first boss.

<!-- gh-comment-id:2514572731 --> @norbertkeri commented on GitHub (Dec 3, 2024): There is an issue where most of the sound effects (weapons hitting, using blood vials, etc) stop playing if you force-quit the game without going to the main menu. I can reliably reproduce both the problem and the fix, so if you ever have an issue with disappearing sounds: start the game, and then quit to the (ingame) menu, and then close the emulator. The next time you start it, sounds will work again. I assume the problem is related to the warning message that pops up when you start the game if you haven't closed it properly. The other problem I encountered is that the "item glow" from defeated mobs do not appear. When I walk over the corpse, the "press X to pick up loot" prompt appears and works, it's just the graphics that are missing. I have tried the Tess branch referred to in the first post, and it didn't work there either. Apart from these two things, the game seems to run surprisingly well and stable with some minor glitches, but I only played up until the first boss.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@EmulaNoob commented on GitHub (Dec 3, 2024):

Dark&Light flickerings on screen, even the game UI keeps normal. Only happening on NVIDIA cards.
Below Ryzen 5 5600 RTX 3060 12GB, not concerns about vram usage, look like if skipping drawparam files or param files
That's explains why triggering R32SFloat error

https://github.com/user-attachments/assets/e4c98e31-05a5-4882-aefd-e0bc4262fd04

<!-- gh-comment-id:2514788217 --> @EmulaNoob commented on GitHub (Dec 3, 2024): Dark&Light flickerings on screen, even the game UI keeps normal. Only happening on NVIDIA cards. Below Ryzen 5 5600 RTX 3060 12GB, not concerns about vram usage, look like if skipping drawparam files or param files That's explains why triggering R32SFloat error https://github.com/user-attachments/assets/e4c98e31-05a5-4882-aefd-e0bc4262fd04

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@norbertkeri commented on GitHub (Dec 3, 2024):

There is an issue where most of the sound effects (weapons hitting, using blood vials, etc) stop playing if you force-quit the game without going to the main menu. I can reliably reproduce both the problem and the fix, so if you ever have an issue with disappearing sounds: start the game, and then quit to the (ingame) menu, and then close the emulator. The next time you start it, sounds will work again. I assume the problem is related to the warning message that pops up when you start the game if you haven't closed it properly.
The other problem I encountered is that the "item glow" from defeated mobs do not appear. When I walk over the corpse, the "press X to pick up loot" prompt appears and works, it's just the graphics that are missing. I have tried the Tess branch referred to in the first post, and it didn't work there either.
Apart from these two things, the game seems to run surprisingly well and stable with some minor glitches, but I only played up until the first boss.

First issue only happens with the 60fps with deltatime patch on, without any fps patch it doesn't happen.

The second issue is fixed by tessellation, you just need to wait for it to be worked on enough to be merged.

You are right, I should have disabled the patch before reporting. Them item glow is also fine on the current tesselation branch, I think I might have tried an older version before.

<!-- gh-comment-id:2515349313 --> @norbertkeri commented on GitHub (Dec 3, 2024): > > There is an issue where most of the sound effects (weapons hitting, using blood vials, etc) stop playing if you force-quit the game without going to the main menu. I can reliably reproduce both the problem and the fix, so if you ever have an issue with disappearing sounds: start the game, and then quit to the (ingame) menu, and then close the emulator. The next time you start it, sounds will work again. I assume the problem is related to the warning message that pops up when you start the game if you haven't closed it properly. > > The other problem I encountered is that the "item glow" from defeated mobs do not appear. When I walk over the corpse, the "press X to pick up loot" prompt appears and works, it's just the graphics that are missing. I have tried the Tess branch referred to in the first post, and it didn't work there either. > > Apart from these two things, the game seems to run surprisingly well and stable with some minor glitches, but I only played up until the first boss. > > First issue only happens with the 60fps with deltatime patch on, without any fps patch it doesn't happen. > > The second issue is fixed by tessellation, you just need to wait for it to be worked on enough to be merged. You are right, I should have disabled the patch before reporting. Them item glow is also fine on the current tesselation branch, I think I might have tried an older version before.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@noelmiller commented on GitHub (Dec 5, 2024):

I've managed to get Bloodborne running using Distrobox on Bazzite. I believe there is an issue with using the mesa drivers when just running the AppImage. The Distrobox I am using has the AMD Pro Drivers which don't seem to have the same issues as the Mesa drivers. Everything is pretty smooth minus the occasional hiccup on my machine.

Here is a gist of how I got it working for those that may want it: https://gist.github.com/noelmiller/97ee9c6d6279c311ddcfa455d41c64e3

<!-- gh-comment-id:2519154427 --> @noelmiller commented on GitHub (Dec 5, 2024): I've managed to get Bloodborne running using Distrobox on Bazzite. I believe there is an issue with using the mesa drivers when just running the AppImage. The Distrobox I am using has the AMD Pro Drivers which don't seem to have the same issues as the Mesa drivers. Everything is pretty smooth minus the occasional hiccup on my machine. Here is a gist of how I got it working for those that may want it: https://gist.github.com/noelmiller/97ee9c6d6279c311ddcfa455d41c64e3

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@noelmiller commented on GitHub (Dec 5, 2024):

So, friends! I'm telling you about the fun of playing Bloodborne on Steam Deck OLED. We all thought that the game did not work well on the Steam Deck, but we were deceived)) It turns out that there is just a problem that prevents the game from going normally, you don't need mods for this, it's enough to do a few actions if you endure))

SteamOS Stable (recent updates). Build: shadPS4 v0.4.1 WIP HEAD f658fc5

Emulator Settings: Enable Fullscreen Is PS4 Pro Vblank Divider = 2

Patches: Skip Intro Disable Chromatic Aberration Disable Motion Blur Disable HTTP Requests Force Enable Old Hunters DLC

This kind of thing meets me (lasts for several seconds, maybe 10), it changes every time I start)) then the gray screen for a couple of seconds, then there were video (Intro, but later I put a Skip Intro patch).

I started a new game, I don't remember the first time or the second time I got into the game... (there was a hang-up on character creation or not... I forgot). When creating a character, the game seems to hang (it may actually happen), but in fact it may be a hoax, the game loads for a long time, after maybe 20-30 seconds everything passes, Then a semblance of a character appears. You can set up and start the game.

At this stage, the game may freeze and close, but when we start the game again, we can continue. We get to the clinic, there are no many walls, no enemies, etc., the FPS is very small, but I got to the lamp and fell into the hunter's dream.

Next, what I did in the game was pick up the initial weapon, then, ATTENTION, I took off my clothes and immediately put them on. (By the way, as you can see, the clothing icons are not displayed, although the equipment is there.) And our character is now updated. Then, perhaps this does not always happen, but walls, enemies and the rest began to appear. So it looks like the initial problem is really related to the initial clothes of the character's clothes. By the way, in the store you have the opportunity to buy a new suit, so its icons are displayed normally (if I remember correctly).

I also tried to move to Central Yarnam and the clinic.

For those who have a Steam Deck, check it out. As soon as you arrive at the clinic, immediately take off all your clothes and put them back on. (If you then go to the main menu and boot up again, then everything seems to reset and you need to repeat the steps.)

I also uploaded my saves and here are screenshots from Forsaken Cainhurst Castle. I appeared normally. Then it happened. I took the clothes off my torso and put them back on, but after a few seconds there was a malfunction. I also attach a log file, there is an error at the end.

shad_log.txt

In general, it is necessary to repair the initial equipment or something related to it. Or the problem is in the clothes that are put on the torso, because it is she who disappears. If the game does not load after 30 seconds, then most likely it will close after another 20.

I seem to have said everything I wanted to say, if I haven't forgotten anything.

This has been my experience when running shadps4 on Bazzite even using ngoquang's fork on my Deck and on my PC. I think it has something to do with the AMD Mesa drivers not working the same way that the AMD Pro Driver do. Unfortunately, you can't run the pro drivers on a steam deck OLED as the graphics card doesn't support them. I'm not sure if maybe we should start a separate issue for this?

<!-- gh-comment-id:2519175134 --> @noelmiller commented on GitHub (Dec 5, 2024): > So, friends! I'm telling you about the fun of playing Bloodborne on Steam Deck OLED. We all thought that the game did not work well on the Steam Deck, but we were deceived)) It turns out that there is just a problem that prevents the game from going normally, you don't need mods for this, it's enough to do a few actions if you endure)) > > SteamOS Stable (recent updates). Build: shadPS4 v0.4.1 WIP HEAD [f658fc5](https://github.com/shadps4-emu/shadPS4/commit/f658fc58d10b6d86015d73bd90ab4f807b4ef28e) > > Emulator Settings: Enable Fullscreen Is PS4 Pro Vblank Divider = 2 > > Patches: Skip Intro Disable Chromatic Aberration Disable Motion Blur Disable HTTP Requests Force Enable Old Hunters DLC > > This kind of thing meets me (lasts for several seconds, maybe 10), it changes every time I start))     then the gray screen for a couple of seconds, then there were video (Intro, but later I put a Skip Intro patch). > > I started a new game, I don't remember the first time or the second time I got into the game... (there was a hang-up on character creation or not... I forgot). When creating a character, the game seems to hang (it may actually happen), but in fact it may be a hoax, the game loads for a long time, after maybe 20-30 seconds everything passes, Then a semblance of a character appears. You can set up and start the game. > > At this stage, the game may freeze and close, but when we start the game again, we can continue. We get to the clinic, there are no many walls, no enemies, etc., the FPS is very small, but I got to the lamp and fell into the hunter's dream.    > > Next, what I did in the game was pick up the initial weapon, then, ATTENTION, I took off my clothes and immediately put them on. (By the way, as you can see, the clothing icons are not displayed, although the equipment is there.) And our character is now updated. Then, perhaps this does not always happen, but walls, enemies and the rest began to appear. So it looks like the initial problem is really related to the initial clothes of the character's clothes. By the way, in the store you have the opportunity to buy a new suit, so its icons are displayed normally (if I remember correctly).     > > I also tried to move to Central Yarnam and the clinic.     > > For those who have a Steam Deck, check it out. As soon as you arrive at the clinic, immediately take off all your clothes and put them back on. (If you then go to the main menu and boot up again, then everything seems to reset and you need to repeat the steps.) > > I also uploaded my saves and here are screenshots from Forsaken Cainhurst Castle. I appeared normally.  Then it happened.  I took the clothes off my torso and put them back on, but after a few seconds there was a malfunction.  I also attach a log file, there is an error at the end. > > [shad_log.txt](https://github.com/user-attachments/files/17970171/shad_log.txt) > > In general, it is necessary to repair the initial equipment or something related to it. Or the problem is in the clothes that are put on the torso, because it is she who disappears. If the game does not load after 30 seconds, then most likely it will close after another 20. > > I seem to have said everything I wanted to say, if I haven't forgotten anything. This has been my experience when running shadps4 on Bazzite even using ngoquang's fork on my Deck and on my PC. I think it has something to do with the AMD Mesa drivers not working the same way that the AMD Pro Driver do. Unfortunately, you can't run the pro drivers on a steam deck OLED as the graphics card doesn't support them. I'm not sure if maybe we should start a separate issue for this?

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@C0rn3j commented on GitHub (Dec 7, 2024):

macOS should be able to run after https://github.com/shadps4-emu/shadPS4/pull/1683 gets merged and it also fixes/improves the VRAM situation.

<!-- gh-comment-id:2525275435 --> @C0rn3j commented on GitHub (Dec 7, 2024): macOS should be able to *run* after https://github.com/shadps4-emu/shadPS4/pull/1683 gets merged and it also fixes/improves the VRAM situation.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@C0rn3j commented on GitHub (Dec 8, 2024):

It may be handy to link the compat reports in this aggregate too, as they may have extra info - https://github.com/shadps4-emu/shadps4-game-compatibility/issues/71

There's a character creation crash issue reported here https://github.com/shadps4-emu/shadPS4/issues/1540

(which seems to affect me too) -> That was actually https://github.com/shadps4-emu/shadPS4/issues/1704 and not #1540

<!-- gh-comment-id:2526315846 --> @C0rn3j commented on GitHub (Dec 8, 2024): It may be handy to link the compat reports in this aggregate too, as they may have extra info - https://github.com/shadps4-emu/shadps4-game-compatibility/issues/71 There's a character creation crash issue reported here https://github.com/shadps4-emu/shadPS4/issues/1540 ~~(which seems to affect me too)~~ -> That was actually https://github.com/shadps4-emu/shadPS4/issues/1704 and not #1540

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@hgh32 commented on GitHub (Dec 11, 2024):

I think can be add hardware specific
like this #1739

<!-- gh-comment-id:2536171254 --> @hgh32 commented on GitHub (Dec 11, 2024): I think can be add hardware specific like this #1739

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@DeviousConundrum commented on GitHub (Dec 15, 2024):

Bloodborne CUSA00900 crashes with this error:

[Debug] <Critical> liverpool.cpp:ProcessGraphics:235: Unreachable code!
Unsupported PM4 type 0

I'm on shadPS4 v4.0.1 WIP main 0fd1ab6 on Windows 11

I have these patches enabled:

shad_log.txt

<!-- gh-comment-id:2544154499 --> @DeviousConundrum commented on GitHub (Dec 15, 2024): ### Bloodborne CUSA00900 crashes with this error: ``` [Debug] <Critical> liverpool.cpp:ProcessGraphics:235: Unreachable code! Unsupported PM4 type 0 ``` I'm on shadPS4 v4.0.1 WIP main 0fd1ab6 on Windows 11 ### I have these patches enabled:  [shad_log.txt](https://github.com/user-attachments/files/18139035/shad_log.txt)

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@rainmakerv3 commented on GitHub (Dec 17, 2024):

It's been confirmed by different users that the crashes occuring on intel 12th gen and newer CPUs when attacking or attacked by enemies only happen on Windows, and not on Linux. So it could be some sort of scheduling issue as previously suspected

<!-- gh-comment-id:2548282468 --> @rainmakerv3 commented on GitHub (Dec 17, 2024): It's been confirmed by different users that the crashes occuring on intel 12th gen and newer CPUs when attacking or attacked by enemies only happen on Windows, and not on Linux. So it could be some sort of scheduling issue as previously suspected

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Linear524 commented on GitHub (Dec 19, 2024):

Any Intel CPU's suffering from those *sfx crashes...
Tested on Intel Xeon E5 2680v3, Xeon E5 2690v4, Xeon E5 1650v3, Intel Core i7 8700, Core i7 11800, same crashes...
But when I test BB on AMD Ryzen 7800 or Ryzen 2400GE - no crashes...
OS Win10 22H2 and GeForce 1080Ti.

<!-- gh-comment-id:2554900416 --> @Linear524 commented on GitHub (Dec 19, 2024): Any Intel CPU's suffering from those *sfx crashes... Tested on Intel Xeon E5 2680v3, Xeon E5 2690v4, Xeon E5 1650v3, Intel Core i7 8700, Core i7 11800, same crashes... But when I test BB on AMD Ryzen 7800 or Ryzen 2400GE - no crashes... OS Win10 22H2 and GeForce 1080Ti.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@meijjaa commented on GitHub (Dec 23, 2024):

Can confirm crashing on enemy attack (no need to get hit, using healing item also crashes the game) on my Intel Ultra 7 265k + RTX3080. Running shadps4 in Windows 10 Proxmox VM.
The crash does not happen on the same system running Ubuntu 24.04 VM. Although the CPU performance is quite a lot worse.

On a different system running a i9 10850k + RTX 3080, Windows 11 bare metal, the crash doesn't happen.

<!-- gh-comment-id:2559375008 --> @meijjaa commented on GitHub (Dec 23, 2024): Can confirm crashing on enemy attack (no need to get hit, using healing item also crashes the game) on my Intel Ultra 7 265k + RTX3080. Running shadps4 in Windows 10 Proxmox VM. The crash does not happen on the same system running Ubuntu 24.04 VM. Although the CPU performance is quite a lot worse. On a different system running a i9 10850k + RTX 3080, Windows 11 bare metal, the crash doesn't happen.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@C0rn3j commented on GitHub (Dec 26, 2024):

@rainmakerv3 Ryzen 5 7600X on Arch Linux, instant guaranteed freeze when getting hit by this fella near the starting area... though I should probably test with no patches... brb

EDIT: Okay so perhaps that one is caused by one of the patches.

<!-- gh-comment-id:2562903119 --> @C0rn3j commented on GitHub (Dec 26, 2024): @rainmakerv3 Ryzen 5 7600X on Arch Linux, instant guaranteed freeze when getting hit by this fella near the starting area... though I should probably test with no patches... brb EDIT: Okay so perhaps that one is caused by one of the patches. 

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@matt35imulator commented on GitHub (Jan 2, 2025):

So, friends! I'm telling you about the fun of playing Bloodborne on Steam Deck OLED. We all thought that the game did not work well on the Steam Deck, but we were deceived)) It turns out that there is just a problem that prevents the game from going normally, you don't need mods for this, it's enough to do a few actions if you endure))

SteamOS Stable (recent updates). Build: shadPS4 v0.4.1 WIP HEAD f658fc5

Emulator Settings: Enable Fullscreen Is PS4 Pro Vblank Divider = 2

Patches: Skip Intro Disable Chromatic Aberration Disable Motion Blur Disable HTTP Requests Force Enable Old Hunters DLC

This kind of thing meets me (lasts for several seconds, maybe 10), it changes every time I start)) then the gray screen for a couple of seconds, then there were video (Intro, but later I put a Skip Intro patch).

I started a new game, I don't remember the first time or the second time I got into the game... (there was a hang-up on character creation or not... I forgot). When creating a character, the game seems to hang (it may actually happen), but in fact it may be a hoax, the game loads for a long time, after maybe 20-30 seconds everything passes, Then a semblance of a character appears. You can set up and start the game.

At this stage, the game may freeze and close, but when we start the game again, we can continue. We get to the clinic, there are no many walls, no enemies, etc., the FPS is very small, but I got to the lamp and fell into the hunter's dream.

Next, what I did in the game was pick up the initial weapon, then, ATTENTION, I took off my clothes and immediately put them on. (By the way, as you can see, the clothing icons are not displayed, although the equipment is there.) And our character is now updated. Then, perhaps this does not always happen, but walls, enemies and the rest began to appear. So it looks like the initial problem is really related to the initial clothes of the character's clothes. By the way, in the store you have the opportunity to buy a new suit, so its icons are displayed normally (if I remember correctly).

I also tried to move to Central Yarnam and the clinic.

For those who have a Steam Deck, check it out. As soon as you arrive at the clinic, immediately take off all your clothes and put them back on. (If you then go to the main menu and boot up again, then everything seems to reset and you need to repeat the steps.)

I also uploaded my saves and here are screenshots from Forsaken Cainhurst Castle. I appeared normally. Then it happened. I took the clothes off my torso and put them back on, but after a few seconds there was a malfunction. I also attach a log file, there is an error at the end.

shad_log.txt

In general, it is necessary to repair the initial equipment or something related to it. Or the problem is in the clothes that are put on the torso, because it is she who disappears. If the game does not load after 30 seconds, then most likely it will close after another 20.

I seem to have said everything I wanted to say, if I haven't forgotten anything.

Did you manage to solve the screen glitching when opening the game?

<!-- gh-comment-id:2567861809 --> @matt35imulator commented on GitHub (Jan 2, 2025): > So, friends! I'm telling you about the fun of playing Bloodborne on Steam Deck OLED. We all thought that the game did not work well on the Steam Deck, but we were deceived)) It turns out that there is just a problem that prevents the game from going normally, you don't need mods for this, it's enough to do a few actions if you endure)) > > SteamOS Stable (recent updates). Build: shadPS4 v0.4.1 WIP HEAD [f658fc5](https://github.com/shadps4-emu/shadPS4/commit/f658fc58d10b6d86015d73bd90ab4f807b4ef28e) > > Emulator Settings: Enable Fullscreen Is PS4 Pro Vblank Divider = 2 > > Patches: Skip Intro Disable Chromatic Aberration Disable Motion Blur Disable HTTP Requests Force Enable Old Hunters DLC > > This kind of thing meets me (lasts for several seconds, maybe 10), it changes every time I start))     then the gray screen for a couple of seconds, then there were video (Intro, but later I put a Skip Intro patch). > > I started a new game, I don't remember the first time or the second time I got into the game... (there was a hang-up on character creation or not... I forgot). When creating a character, the game seems to hang (it may actually happen), but in fact it may be a hoax, the game loads for a long time, after maybe 20-30 seconds everything passes, Then a semblance of a character appears. You can set up and start the game. > > At this stage, the game may freeze and close, but when we start the game again, we can continue. We get to the clinic, there are no many walls, no enemies, etc., the FPS is very small, but I got to the lamp and fell into the hunter's dream.    > > Next, what I did in the game was pick up the initial weapon, then, ATTENTION, I took off my clothes and immediately put them on. (By the way, as you can see, the clothing icons are not displayed, although the equipment is there.) And our character is now updated. Then, perhaps this does not always happen, but walls, enemies and the rest began to appear. So it looks like the initial problem is really related to the initial clothes of the character's clothes. By the way, in the store you have the opportunity to buy a new suit, so its icons are displayed normally (if I remember correctly).     > > I also tried to move to Central Yarnam and the clinic.     > > For those who have a Steam Deck, check it out. As soon as you arrive at the clinic, immediately take off all your clothes and put them back on. (If you then go to the main menu and boot up again, then everything seems to reset and you need to repeat the steps.) > > I also uploaded my saves and here are screenshots from Forsaken Cainhurst Castle. I appeared normally.  Then it happened.  I took the clothes off my torso and put them back on, but after a few seconds there was a malfunction.  I also attach a log file, there is an error at the end. > > [shad_log.txt](https://github.com/user-attachments/files/17970171/shad_log.txt) > > In general, it is necessary to repair the initial equipment or something related to it. Or the problem is in the clothes that are put on the torso, because it is she who disappears. If the game does not load after 30 seconds, then most likely it will close after another 20. > > I seem to have said everything I wanted to say, if I haven't forgotten anything. Did you manage to solve the screen glitching when opening the game?

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@C0rn3j commented on GitHub (Jan 2, 2025):

The linked (now fixed) sound issue was on every platform, not just Linux.

There is now a new sound issue, https://github.com/shadps4-emu/shadPS4/issues/2015, which so far only has two people affected on Linux, but could once again be an issue for everyone.

You seem to have accidentally melded together two issues - CPU overusage + VRAM overusage, now you have deleted the VRAM overusage link (the issue is fixed nowadays) but kept the CPU usage one.
So it incorrectly reads <UNFIXED> VRAM OVERUSAGE [CPU OVERUSAGE LINK]
EDIT: the CPU overusage was just closed too by the author as fixed

It would be helpful to note that resolution patches over 1080p cause frequent unloading issues (which seem to be present even without them, but rarely) and that there's a sound issue related to the FPS unlock patches that makes some sounds disappear but resolves if a person correctly exits the game.
The linked guide already has these, but it would be nice to track them here too.

And finally a MacOS -> macOS nitpick.

<!-- gh-comment-id:2567887319 --> @C0rn3j commented on GitHub (Jan 2, 2025): The linked (now fixed) sound issue was on every platform, not just Linux. There is now a new sound issue, https://github.com/shadps4-emu/shadPS4/issues/2015, which so far only has two people affected on Linux, but could once again be an issue for everyone. You seem to have accidentally melded together two issues - CPU overusage + VRAM overusage, now you have deleted the VRAM overusage link (the issue is fixed nowadays) but kept the CPU usage one. So it incorrectly reads \<UNFIXED\> VRAM OVERUSAGE \[CPU OVERUSAGE LINK\] EDIT: the CPU overusage was just closed too by the author as fixed It would be helpful to note that resolution patches over 1080p cause frequent unloading issues (which seem to be present even without them, but rarely) and that there's a sound issue related to the FPS unlock patches that makes some sounds disappear but resolves if a person correctly exits the game. The linked guide already has these, but it would be nice to track them here too. And finally a MacOS -> macOS nitpick.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@GHU7924 commented on GitHub (Jan 2, 2025):

Did you manage to solve the screen glitching when opening the game?

I haven't looked for a solution, but the problem still exists. It lasts about 18 seconds, then a gray screen appears for a second or two, and I find myself in the main menu of the game.

Now there are no more problems with the environment that I wrote about, and the performance is 10-20 frames per second, but mostly in the 15-20 range.

There is also a problem with the shadPS4 interface itself, because of the description, the window size changes, if there are 3 lines in the description - one window size, you point to another element with 4 lines of description, then the window size changes.

<!-- gh-comment-id:2567909781 --> @GHU7924 commented on GitHub (Jan 2, 2025): >Did you manage to solve the screen glitching when opening the game? I haven't looked for a solution, but the problem still exists. It lasts about 18 seconds, then a gray screen appears for a second or two, and I find myself in the main menu of the game. Now there are no more problems with the environment that I wrote about, and the performance is 10-20 frames per second, but mostly in the 15-20 range. There is also a problem with the shadPS4 interface itself, because of the description, the window size changes, if there are 3 lines in the description - one window size, you point to another element with 4 lines of description, then the window size changes.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@nr1971 commented on GitHub (Jan 3, 2025):

There is also a problem with the shadPS4 interface itself, because of the description, the window size changes, if there are 3 lines in the description - one window size, you point to another element with 4 lines of description, then the window size changes.

I noticed this too. It's very disorienting. What's weird is my son and I are both running Ubuntu 24.04 and I have this issue and he doesn't. Same version of shadps4 too.

<!-- gh-comment-id:2569379022 --> @nr1971 commented on GitHub (Jan 3, 2025): > There is also a problem with the shadPS4 interface itself, because of the description, the window size changes, if there are 3 lines in the description - one window size, you point to another element with 4 lines of description, then the window size changes. I noticed this too. It's very disorienting. What's weird is my son and I are both running Ubuntu 24.04 and I have this issue and he doesn't. Same version of shadps4 too.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@birthtothunder commented on GitHub (Jan 3, 2025):

VRAM overusage is definitely still an issue.

<!-- gh-comment-id:2569479695 --> @birthtothunder commented on GitHub (Jan 3, 2025): VRAM overusage is definitely still an issue.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@sunbthr commented on GitHub (Jan 4, 2025):

I noticed a flying mesh in Old Yharnam

Ubuntu 24.04 / X11 / gamescope
Intel Core i7 12700H
3060 Laptop GPU
32 GB VRAM

720p patch
60 fps with delta time patch
no chromatic/motion blur/no http

no face customization mod to prevent vertex explosions

<!-- gh-comment-id:2569986132 --> @sunbthr commented on GitHub (Jan 4, 2025): I noticed a flying mesh in Old Yharnam Ubuntu 24.04 / X11 / gamescope Intel Core i7 12700H 3060 Laptop GPU 32 GB VRAM 720p patch 60 fps with delta time patch no chromatic/motion blur/no http no face customization mod to prevent vertex explosions 

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Missake212 commented on GitHub (Jan 4, 2025):

I noticed a flying mesh in Old Yharnam

Ubuntu 24.04 / X11 / gamescope Intel Core i7 12700H 3060 Laptop GPU 32 GB VRAM

720p patch 60 fps with delta time patch no chromatic/motion blur/no http

no face customization mod to prevent vertex explosions

Pretty sure this is like that on ps4 and not an actual issue on shadPS4's end.

<!-- gh-comment-id:2569988592 --> @Missake212 commented on GitHub (Jan 4, 2025): > I noticed a flying mesh in Old Yharnam > > Ubuntu 24.04 / X11 / gamescope Intel Core i7 12700H 3060 Laptop GPU 32 GB VRAM > > 720p patch 60 fps with delta time patch no chromatic/motion blur/no http > > no face customization mod to prevent vertex explosions > >  Pretty sure this is like that on ps4 and not an actual issue on shadPS4's end.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@HearthstoneBugs commented on GitHub (Jan 4, 2025):

I noticed a flying mesh in Old Yharnam
Ubuntu 24.04 / X11 / gamescope Intel Core i7 12700H 3060 Laptop GPU 32 GB VRAM
720p patch 60 fps with delta time patch no chromatic/motion blur/no http
no face customization mod to prevent vertex explosions

Pretty sure this is like that on ps4 and not an actual issue on shadPS4's end.

I can confirm that this issue has been reported many times over the years because it is also present when playing on a PS4 or PS5 therefore it's not a problem with shadPS4.

In fact it's four floating statues that appear as one.

<!-- gh-comment-id:2571251771 --> @HearthstoneBugs commented on GitHub (Jan 4, 2025): > > I noticed a flying mesh in Old Yharnam > > Ubuntu 24.04 / X11 / gamescope Intel Core i7 12700H 3060 Laptop GPU 32 GB VRAM > > 720p patch 60 fps with delta time patch no chromatic/motion blur/no http > > no face customization mod to prevent vertex explosions > >  > > Pretty sure this is like that on ps4 and not an actual issue on shadPS4's end. I can confirm that this issue has been reported many times over the years because it is also present when playing on a PS4 or PS5 therefore it's not a problem with shadPS4. In fact it's four floating statues that appear as one.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@sunbthr commented on GitHub (Jan 4, 2025):

I noticed a flying mesh in Old Yharnam
Ubuntu 24.04 / X11 / gamescope Intel Core i7 12700H 3060 Laptop GPU 32 GB VRAM
720p patch 60 fps with delta time patch no chromatic/motion blur/no http
no face customization mod to prevent vertex explosions

Pretty sure this is like that on ps4 and not an actual issue on shadPS4's end.

I can confirm that this issue has been reported many times over the years because it is also present when playing on a PS4 or PS5 therefore it's not a problem with shadPS4.

In fact it's four floating statues that appear as one.

Thanks for the info. It’s been many years since I played the game on a PS4 and I have no way to compare.

<!-- gh-comment-id:2571252964 --> @sunbthr commented on GitHub (Jan 4, 2025): > > > I noticed a flying mesh in Old Yharnam > > > Ubuntu 24.04 / X11 / gamescope Intel Core i7 12700H 3060 Laptop GPU 32 GB VRAM > > > 720p patch 60 fps with delta time patch no chromatic/motion blur/no http > > > no face customization mod to prevent vertex explosions > > >  > > > > > > Pretty sure this is like that on ps4 and not an actual issue on shadPS4's end. > > I can confirm that this issue has been reported many times over the years because it is also present when playing on a PS4 or PS5 therefore it's not a problem with shadPS4. > > In fact it's four floating statues that appear as one. Thanks for the info. It’s been many years since I played the game on a PS4 and I have no way to compare.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@alicepachecoo commented on GitHub (Jan 7, 2025):

Don't know with how many people this has been happening but I have seen bloodborne crashing during some bossfights (Cleric Beast, Vicar Amelia, Blood-Starved Beast), this didn't happened with other bosses I've found so far (not even the ones from the chalice dungeons).

<!-- gh-comment-id:2574259252 --> @alicepachecoo commented on GitHub (Jan 7, 2025): Don't know with how many people this has been happening but I have seen bloodborne crashing during some bossfights (Cleric Beast, Vicar Amelia, Blood-Starved Beast), this didn't happened with other bosses I've found so far (not even the ones from the chalice dungeons).

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@GHU7924 commented on GitHub (Jan 8, 2025):

@matt35imulator PR #2095 this issue has been resolved, but now instead of these screen flickers, you will have a black screen for 18 seconds.

In Windows 11, it takes me 6-7 seconds to load up to the menu, on Steam Deck it takes about 22 seconds.

Patches:
Skip Intro
Disable Chromatic Aberration
Disable Motion Blur
Disable HTTP Requests
Force Enable Old Hunters DLC

<!-- gh-comment-id:2577567761 --> @GHU7924 commented on GitHub (Jan 8, 2025): @matt35imulator PR #2095 this issue has been resolved, but now instead of these screen flickers, you will have a black screen for 18 seconds. In Windows 11, it takes me 6-7 seconds to load up to the menu, on Steam Deck it takes about 22 seconds. Patches: Skip Intro Disable Chromatic Aberration Disable Motion Blur Disable HTTP Requests Force Enable Old Hunters DLC

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Missake212 commented on GitHub (Jan 11, 2025):

@Cloneus the reason you're crashing is the remaster project, please don't report "issues" like this here while using game patches and mods.

<!-- gh-comment-id:2585378841 --> @Missake212 commented on GitHub (Jan 11, 2025): @Cloneus the reason you're crashing is the remaster project, please don't report "issues" like this here while using game patches and mods.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Cloneus commented on GitHub (Jan 11, 2025):

@Cloneus the reason you're crashing is the remaster project, please don't report "issues" like this here while using game patches and mods.

Sorry, I'll redo testing without mods and patches.

<!-- gh-comment-id:2585391467 --> @Cloneus commented on GitHub (Jan 11, 2025): > @Cloneus the reason you're crashing is the remaster project, please don't report "issues" like this here while using game patches and mods. Sorry, I'll redo testing without mods and patches.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Cloneus commented on GitHub (Jan 11, 2025):

@Cloneus the reason you're crashing is the remaster project, please don't report "issues" like this here while using game patches and mods.

Sorry, I'll redo testing without mods and patches.

After testing again. Removing all mods and patches seemed to resolve the issue of crashing on attacks/being attacked, with the main culprit being the Remaster mod as you perscribed. Thank you for the help.

<!-- gh-comment-id:2585397387 --> @Cloneus commented on GitHub (Jan 11, 2025): > > @Cloneus the reason you're crashing is the remaster project, please don't report "issues" like this here while using game patches and mods. > > Sorry, I'll redo testing without mods and patches. After testing again. Removing all mods and patches seemed to resolve the issue of crashing on attacks/being attacked, with the main culprit being the Remaster mod as you perscribed. Thank you for the help.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@dante3732 commented on GitHub (Feb 5, 2025):

Hello, sometimes i have some flickering on R5 3600, 16 RAM, Vega 64, Windows 11 24H2.

https://github.com/user-attachments/assets/5be20e0f-b5a3-40b8-9627-e5679b05de67

Also i have rumble issue. Sometimes, when receiving a blow from an opponent, the right motor runs much longer than it should.

<!-- gh-comment-id:2637526205 --> @dante3732 commented on GitHub (Feb 5, 2025): Hello, sometimes i have some flickering on R5 3600, 16 RAM, Vega 64, Windows 11 24H2.    https://github.com/user-attachments/assets/5be20e0f-b5a3-40b8-9627-e5679b05de67   Also i have rumble issue. Sometimes, when receiving a blow from an opponent, the right motor runs much longer than it should.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Hermiten commented on GitHub (Feb 6, 2025):

@dante3732

<!-- gh-comment-id:2639618990 --> @Hermiten commented on GitHub (Feb 6, 2025): @dante3732 <img width="614" alt="Image" src="https://github.com/user-attachments/assets/213054e8-b4aa-4b30-8077-048d2ee7c25d" />

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@lmutig commented on GitHub (Feb 17, 2025):

The flash bug on Intel graphics cards such as A770 B580 should also be added.

<!-- gh-comment-id:2662973594 --> @lmutig commented on GitHub (Feb 17, 2025): The flash bug on Intel graphics cards such as A770 B580 should also be added.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@2mg commented on GitHub (Mar 1, 2025):

Part 1:
Regarding "CPU being greatly overworked in bloodborne on particular systems #1542":

So was it fixed?
I tried using Lasso to switch CCDs, disable SMT and so on, it's always this sort of approximately half the cores being underutilized.
Could be that the Core 0 is taxed so much it can't properly share the workload across all cores, but could be something else.

Part 2:
While BB can be made to run over 60/unlocked, or under 60 (ie 50 FPS limited for more consistent FPS if 60 is unstable), seems like emulator itself is under some sort of VSync, as lack of Vsync ought to cause screen tearing (speaking about non-VRR displays), but when tested with RTSS's FCAT with 2 bars there is no tearing (in this case above 60):

https://github.com/user-attachments/assets/da42bd90-3c8c-4abf-b996-45a33f203e12

Switching Vulkan to DXGI present method seems to lock FPS to half for some reason, and I can't get into DXGI nor Native persent methods with Special K to see what's happening, but again, I suspect Vsync is forced, or built-in, on the emulator itself.

<!-- gh-comment-id:2692457318 --> @2mg commented on GitHub (Mar 1, 2025): Part 1: Regarding "CPU being greatly overworked in bloodborne on particular systems #1542":  So was it fixed? I tried using Lasso to switch CCDs, disable SMT and so on, it's always this sort of approximately half the cores being underutilized. Could be that the Core 0 is taxed so much it can't properly share the workload across all cores, but could be something else. Part 2: While BB can be made to run over 60/unlocked, or under 60 (ie 50 FPS limited for more consistent FPS if 60 is unstable), seems like emulator itself is under some sort of VSync, as lack of Vsync ought to cause screen tearing (speaking about non-VRR displays), but when tested with RTSS's FCAT with 2 bars there is no tearing (in this case above 60): https://github.com/user-attachments/assets/da42bd90-3c8c-4abf-b996-45a33f203e12 Switching Vulkan to DXGI present method seems to lock FPS to half for some reason, and I can't get into DXGI nor Native persent methods with Special K to see what's happening, but again, I suspect Vsync is forced, or built-in, on the emulator itself.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@0xSovereign commented on GitHub (Mar 8, 2025):

I'm really not sure if I'm the only one here, but I'm missing a LOT of lighting effects, it's almost non existent. This happened on 0.5.0, 0.5.1, 0.6.0, 0.6.1 builds. I haven't tested any older ones. Please, tell me if I missed a guide or if it has been mentioned already. Version 1.09.

EDIT: Marked as resolved, since it turned out to be missing data files.

<!-- gh-comment-id:2708318466 --> @0xSovereign commented on GitHub (Mar 8, 2025): I'm really not sure if I'm the only one here, but I'm missing a LOT of lighting effects, it's almost non existent. This happened on 0.5.0, 0.5.1, 0.6.0, 0.6.1 builds. I haven't tested any older ones. Please, tell me if I missed a guide or if it has been mentioned already. Version 1.09.    EDIT: Marked as resolved, since it turned out to be missing data files.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@road0001 commented on GitHub (Apr 7, 2025):

There's random key incorrect in my game. I switch O and X in controller settings, now I can use O dodge and use X confirm. But sometimes X key incorrect, it make the character do emotions accidentally, the emotions also randomly. For example, you picked up a item, the item name displays in screen, you need to press X to close it, if you press X, it closed correctly, then your character may do a random emotion. If you are in battle, you can't fight back or dodge until emotion ends.

<!-- gh-comment-id:2781896410 --> @road0001 commented on GitHub (Apr 7, 2025): There's random key incorrect in my game. I switch O and X in controller settings, now I can use O dodge and use X confirm. But sometimes X key incorrect, it make the character do emotions accidentally, the emotions also randomly. For example, you picked up a item, the item name displays in screen, you need to press X to close it, if you press X, it closed correctly, then your character may do a random emotion. If you are in battle, you can't fight back or dodge until emotion ends.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@C0rn3j commented on GitHub (Apr 7, 2025):

@road0001

Bloodborne supports gestures via controller motion, last time I played, shad did not implement that perfectly and it was oversensitive at best.

<!-- gh-comment-id:2782911125 --> @C0rn3j commented on GitHub (Apr 7, 2025): @road0001  Bloodborne supports gestures via controller motion, last time I played, shad did not implement that perfectly and it was oversensitive at best.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@kalaposfos13 commented on GitHub (Apr 7, 2025):

@C0rn3j Can you confirm that motion controls are also too sensitive without patches? Currently it seems like this is not an issue with the emulator, but with the 60 FPS patch.

<!-- gh-comment-id:2782968648 --> @kalaposfos13 commented on GitHub (Apr 7, 2025): @C0rn3j Can you confirm that motion controls are also too sensitive without patches? Currently it seems like this is not an issue with the emulator, but with the 60 FPS patch.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@C0rn3j commented on GitHub (Apr 7, 2025):

@kalaposfos13 I cannot, it's been a while (month or two) since I played but I did use the high-FPS patches, so it might indeed be an issue with the patch itself.

<!-- gh-comment-id:2782973863 --> @C0rn3j commented on GitHub (Apr 7, 2025): @kalaposfos13 I cannot, it's been a while (month or two) since I played but I did use the high-FPS patches, so it might indeed be an issue with the patch itself.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@road0001 commented on GitHub (May 18, 2025):

When I use a third-party controller, the buttons don't behave correctly. The RB and LB correctly, the RT doesn't work, when I press LT, it triggers RT's feature. All of my third-party controller have this issue, and the behave is same, Betop, Flydigi, all of them. Only my old controller of XBOX Series S works correctly. All of my controller are working correctly in other Steam games.

<!-- gh-comment-id:2888980614 --> @road0001 commented on GitHub (May 18, 2025): When I use a third-party controller, the buttons don't behave correctly. The RB and LB correctly, the RT doesn't work, when I press LT, it triggers RT's feature. All of my third-party controller have this issue, and the behave is same, Betop, Flydigi, all of them. Only my old controller of XBOX Series S works correctly. All of my controller are working correctly in other Steam games.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@BryanRykowski commented on GitHub (Jul 15, 2025):

The Castle Cainhurst ghosts have skirts that disappear under certain circumstances. Always happens when they walk on stairs for me.

Fedora Linux 41 / Ryzen 3700X / Radeon RX5700 / 32GB RAM / 8GB VRAM

<!-- gh-comment-id:3071544910 --> @BryanRykowski commented on GitHub (Jul 15, 2025): The Castle Cainhurst ghosts have skirts that disappear under certain circumstances. Always happens when they walk on stairs for me. <img width="1280" height="752" alt="Image" src="https://github.com/user-attachments/assets/ee8f4dc9-b5a8-4f8c-b42d-33553b6d9d7f" /> Fedora Linux 41 / Ryzen 3700X / Radeon RX5700 / 32GB RAM / 8GB VRAM

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@seros022 commented on GitHub (Jul 15, 2025):

im having this problem crashes when i try to open the game cant get to the game menu

intel 13th, 4070 nvidia , 32 ram, windows 11

<!-- gh-comment-id:3075541144 --> @seros022 commented on GitHub (Jul 15, 2025): <img width="1466" height="702" alt="Image" src="https://github.com/user-attachments/assets/76d15523-15f1-4c68-91af-286f1b8096d3" /> im having this problem crashes when i try to open the game cant get to the game menu intel 13th, 4070 nvidia , 32 ram, windows 11

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@BryanRykowski commented on GitHub (Jul 15, 2025):

@seros022 Those errors aren't the cause. They're just unimplemented network stuff.

The same errors on my working install:

Kernel.Vmm] <Info> memory.cpp:249 sceKernelMapNamedFlexibleMemory: out_addr = 0x330f00000
[Lib.Net] <Error> net.cpp:1140 sceNetInit: (DUMMY) called
[Lib.Net] <Error> net.cpp:1220 sceNetPoolCreate: (DUMMY) name = FD4HttpMan size = 16384 flags = 0
[Lib.Ssl] <Error> ssl.cpp:697 sceSslInit: (DUMMY) called poolSize = 311296
[Lib.Http] <Error> http.cpp:264 sceHttpInit: (DUMMY) called libnetMemId = 0 libsslCtxId = 1 poolSize = 311296
[Lib.Http] <Error> http.cpp:118 sceHttpCreateTemplate: (STUBBED) called
[Lib.Http] <Error> http.cpp:421 sceHttpSetNonblock: (STUBBED) called
[Lib.Http] <Error> http.cpp:93 sceHttpCreateEpoll: (STUBBED) called
[Lib.Http] <Error> http.cpp:38 sceHttpAddRequestHeader: (STUBBED) called
[Lib.Ajm] <Info> ajm.cpp:137 sceAjmInitialize: called reserved = 0
[Lib.Ajm] <Info> ajm.cpp:199 sceAjmModuleRegister: called context = 1, codec_type = 1
[Lib.AudioOut] <Info> audioout.cpp:314 sceAudioOutOpen: id = 255 port_type = Main index = 0 length = 256 sample_rate = 48000 param_type = Float_8CH attr = None

You should probably disable any patches/cheats and reinstall the game.

If it still won't run, then attach the actual shad_log.txt from the log folder.

<!-- gh-comment-id:3075997671 --> @BryanRykowski commented on GitHub (Jul 15, 2025): @seros022 Those errors aren't the cause. They're just unimplemented network stuff. The same errors on my working install: ``` Kernel.Vmm] <Info> memory.cpp:249 sceKernelMapNamedFlexibleMemory: out_addr = 0x330f00000 [Lib.Net] <Error> net.cpp:1140 sceNetInit: (DUMMY) called [Lib.Net] <Error> net.cpp:1220 sceNetPoolCreate: (DUMMY) name = FD4HttpMan size = 16384 flags = 0 [Lib.Ssl] <Error> ssl.cpp:697 sceSslInit: (DUMMY) called poolSize = 311296 [Lib.Http] <Error> http.cpp:264 sceHttpInit: (DUMMY) called libnetMemId = 0 libsslCtxId = 1 poolSize = 311296 [Lib.Http] <Error> http.cpp:118 sceHttpCreateTemplate: (STUBBED) called [Lib.Http] <Error> http.cpp:421 sceHttpSetNonblock: (STUBBED) called [Lib.Http] <Error> http.cpp:93 sceHttpCreateEpoll: (STUBBED) called [Lib.Http] <Error> http.cpp:38 sceHttpAddRequestHeader: (STUBBED) called [Lib.Ajm] <Info> ajm.cpp:137 sceAjmInitialize: called reserved = 0 [Lib.Ajm] <Info> ajm.cpp:199 sceAjmModuleRegister: called context = 1, codec_type = 1 [Lib.AudioOut] <Info> audioout.cpp:314 sceAudioOutOpen: id = 255 port_type = Main index = 0 length = 256 sample_rate = 48000 param_type = Float_8CH attr = None ``` You should probably disable any patches/cheats and reinstall the game. If it still won't run, then attach the actual `shad_log.txt` from the log folder. 

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@emoose commented on GitHub (Aug 2, 2025):

FWIW with the crash issue on Intel 12th gen+: https://github.com/shadps4-emu/shadPS4/issues/3220 (issue is locked)

Clang-x64-Debug builds don't seem to have the crash problem, only Release, tried switching the build/optimization flags around with

     set(TEMP ${CMAKE_CXX_FLAGS_DEBUG})
     set(CMAKE_CXX_FLAGS_DEBUG ${CMAKE_CXX_FLAGS_RELEASE})
     set(CMAKE_CXX_FLAGS_RELEASE ${TEMP})

But the crash would still happen on Release while Debug was fine...

Might be related to runtime library being used, adding set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreadedDLL") does make the crash appear on Debug, but at that point that + the flag switch is pretty much using same config as Release.

Changing runtime library also affects _DEBUG define being set, unfortunately couldn't test setting that manually on Release build since that would also affect ITERATOR_DEBUG_LEVEL/RuntimeLibrary and cause issues with lib linking, doesn't seem shadps4 really uses that define much but wonder if any 3rd-party lib could be changing depending on it?

<!-- gh-comment-id:3146118736 --> @emoose commented on GitHub (Aug 2, 2025): FWIW with the crash issue on Intel 12th gen+: https://github.com/shadps4-emu/shadPS4/issues/3220 (issue is locked) Clang-x64-Debug builds don't seem to have the crash problem, only Release, tried switching the build/optimization flags around with ``` set(TEMP ${CMAKE_CXX_FLAGS_DEBUG}) set(CMAKE_CXX_FLAGS_DEBUG ${CMAKE_CXX_FLAGS_RELEASE}) set(CMAKE_CXX_FLAGS_RELEASE ${TEMP}) ``` But the crash would still happen on Release while Debug was fine... Might be related to runtime library being used, adding `set(CMAKE_MSVC_RUNTIME_LIBRARY "MultiThreadedDLL")` does make the crash appear on Debug, but at that point that + the flag switch is pretty much using same config as Release. Changing runtime library also affects _DEBUG define being set, unfortunately couldn't test setting that manually on Release build since that would also affect `ITERATOR_DEBUG_LEVEL`/`RuntimeLibrary` and cause issues with lib linking, doesn't seem shadps4 really uses that define much but wonder if any 3rd-party lib could be changing depending on it?

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Missake212 commented on GitHub (Aug 2, 2025):

@emoose I tested this on my end and it's the same result, no crashes on debug, unfortunately I don't think anyone looks at the comments on this issue (to be honest it's not like issues are checked on anyway it seems), it might be nice to open a new one with all the information you can give so that more people could see it and hopefully someone can find a fix, or you could share your progress more easily if you're thinking about taking a deeper look into it.

<!-- gh-comment-id:3146374761 --> @Missake212 commented on GitHub (Aug 2, 2025): @emoose I tested this on my end and it's the same result, no crashes on debug, unfortunately I don't think anyone looks at the comments on this issue (to be honest it's not like issues are checked on anyway it seems), it might be nice to open a new one with all the information you can give so that more people could see it and hopefully someone can find a fix, or you could share your progress more easily if you're thinking about taking a deeper look into it.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@bigol83 commented on GitHub (Aug 2, 2025):

yeah, Bloodborne crash when enemies hit with Intel 12th up cpus doesn't happen on debug build. Release and Release with debug info crash

<!-- gh-comment-id:3146426996 --> @bigol83 commented on GitHub (Aug 2, 2025): yeah, Bloodborne crash when enemies hit with Intel 12th up cpus doesn't happen on debug build. Release and Release with debug info crash

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@emoose commented on GitHub (Aug 2, 2025):

Not much luck finding anything in shadps4, but tried taking a look in ghidra:

038ce7b0 is func in game that crashes, patching out faulting insns at 38ce9b5 just causes a crash in different func, patching func to `ret` gets rid of crash but causes graphical issues
03ac4270 calls func above, patching that to `ret` gives same gfx issues as above
038f83e0 calls the func above twice, patching that to `ret` gets rid of crash without gfx issue

So guess 038ce7b0 must be doing something weird, a lot of rsp/stack accesses there, afaik faulting insn comes from reading a ptr from rsp which is 0 and trying to deref that ptr (even though func should be setting that ptr to something that isn't 0?)

Patching 038f83e0 to ret seems to work but might just be the same as deleting sfx folder though (iirc I used to still get crashes even with sfx deleted on 12th gen, haven't seen any crash with this yet but hadn't played that long with it), possible it could disable some other non-crashing effects though.

Here's patch xml if anyone wants to try

    <Metadata Title="Bloodborne" Name="Intel 12th Gen+ Hack" Note="" Author="emoose" PatchVer="1.0" AppVer="01.09" AppElf="eboot.bin" isEnabled="true">
        <PatchList>
            <Line Type="byte" Address="0x02CF83E0" Value="c3"/>
        </PatchList>
    </Metadata>

<!-- gh-comment-id:3146656166 --> @emoose commented on GitHub (Aug 2, 2025): Not much luck finding anything in shadps4, but tried taking a look in ghidra: ``` 038ce7b0 is func in game that crashes, patching out faulting insns at 38ce9b5 just causes a crash in different func, patching func to `ret` gets rid of crash but causes graphical issues 03ac4270 calls func above, patching that to `ret` gives same gfx issues as above 038f83e0 calls the func above twice, patching that to `ret` gets rid of crash without gfx issue ``` So guess 038ce7b0 must be doing something weird, a lot of rsp/stack accesses there, afaik faulting insn comes from reading a ptr from rsp which is 0 and trying to deref that ptr (even though func should be setting that ptr to something that isn't 0?) Patching 038f83e0 to ret seems to work but might just be the same as deleting sfx folder though (iirc I used to still get crashes even with sfx deleted on 12th gen, haven't seen any crash with this yet but hadn't played that long with it), possible it could disable some other non-crashing effects though. Here's patch xml if anyone wants to try ``` <Metadata Title="Bloodborne" Name="Intel 12th Gen+ Hack" Note="" Author="emoose" PatchVer="1.0" AppVer="01.09" AppElf="eboot.bin" isEnabled="true"> <PatchList> <Line Type="byte" Address="0x02CF83E0" Value="c3"/> </PatchList> </Metadata> ```

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@bigol83 commented on GitHub (Aug 2, 2025):

Not much luck finding anything in shadps4, but tried taking a look in ghidra:

038ce7b0 is func in game that crashes, patching out faulting insns at 38ce9b5 just causes a crash in different func, patching func to `ret` gets rid of crash but causes graphical issues
03ac4270 calls func above, patching that to `ret` gives same gfx issues as above
038f83e0 calls the func above twice, patching that to `ret` gets rid of crash without gfx issue

So guess 038ce7b0 must be doing something weird, a lot of rsp/stack accesses there, afaik faulting insn comes from reading a ptr from rsp which is 0 and trying to deref that ptr (even though func should be setting that ptr to something that isn't 0?)

Patching 038f83e0 to ret seems to work but might just be the same as deleting sfx folder though (iirc I used to still get crashes even with sfx deleted on 12th gen, haven't seen any crash with this yet but hadn't played that long with it), possible it could disable some other non-crashing effects though.

Here's patch xml if anyone wants to try

    <Metadata Title="Bloodborne" Name="Intel 12th Gen+ Hack" Note="" Author="emoose" PatchVer="1.0" AppVer="01.09" AppElf="eboot.bin" isEnabled="true">
        <PatchList>
            <Line Type="byte" Address="0x02CF83E0" Value="c3"/>
        </PatchList>
    </Metadata>

well, it works without crashing but i couldn't say if it removes some effects just like removing sfx folder

<!-- gh-comment-id:3146673725 --> @bigol83 commented on GitHub (Aug 2, 2025): > Not much luck finding anything in shadps4, but tried taking a look in ghidra: > > ``` > 038ce7b0 is func in game that crashes, patching out faulting insns at 38ce9b5 just causes a crash in different func, patching func to `ret` gets rid of crash but causes graphical issues > 03ac4270 calls func above, patching that to `ret` gives same gfx issues as above > 038f83e0 calls the func above twice, patching that to `ret` gets rid of crash without gfx issue > ``` > > So guess 038ce7b0 must be doing something weird, a lot of rsp/stack accesses there, afaik faulting insn comes from reading a ptr from rsp which is 0 and trying to deref that ptr (even though func should be setting that ptr to something that isn't 0?) > > Patching 038f83e0 to ret seems to work but might just be the same as deleting sfx folder though (iirc I used to still get crashes even with sfx deleted on 12th gen, haven't seen any crash with this yet but hadn't played that long with it), possible it could disable some other non-crashing effects though. > > Here's patch xml if anyone wants to try > > ``` > <Metadata Title="Bloodborne" Name="Intel 12th Gen+ Hack" Note="" Author="emoose" PatchVer="1.0" AppVer="01.09" AppElf="eboot.bin" isEnabled="true"> > <PatchList> > <Line Type="byte" Address="0x02CF83E0" Value="c3"/> > </PatchList> > </Metadata> > ``` well, it works without crashing but i couldn't say if it removes some effects just like removing sfx folder

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Missake212 commented on GitHub (Aug 2, 2025):

Not much luck finding anything in shadps4, but tried taking a look in ghidra:

038ce7b0 is func in game that crashes, patching out faulting insns at 38ce9b5 just causes a crash in different func, patching func to `ret` gets rid of crash but causes graphical issues
03ac4270 calls func above, patching that to `ret` gives same gfx issues as above
038f83e0 calls the func above twice, patching that to `ret` gets rid of crash without gfx issue

So guess 038ce7b0 must be doing something weird, a lot of rsp/stack accesses there, afaik faulting insn comes from reading a ptr from rsp which is 0 and trying to deref that ptr (even though func should be setting that ptr to something that isn't 0?)

Patching 038f83e0 to ret seems to work but might just be the same as deleting sfx folder though (iirc I used to still get crashes even with sfx deleted on 12th gen, haven't seen any crash with this yet but hadn't played that long with it), possible it could disable some other non-crashing effects though.

Here's patch xml if anyone wants to try

    <Metadata Title="Bloodborne" Name="Intel 12th Gen+ Hack" Note="" Author="emoose" PatchVer="1.0" AppVer="01.09" AppElf="eboot.bin" isEnabled="true">
        <PatchList>
            <Line Type="byte" Address="0x02CF83E0" Value="c3"/>
        </PatchList>
    </Metadata>

Tested the game for a bit with the patch, not crashes on my end and all the sfx I looked at worked as expected, you could PR that to the shadPS4 patches and cheats repo https://github.com/shadps4-emu/ps4_cheats.

I don't like to insist on things but I think opening a new issue would help you have more visibility on this work you've done, I'll also see if the Intel issue can be unlocked or not.

EDIT: the issue has been unlocked if you want to move the convo there, your call.

<!-- gh-comment-id:3146721110 --> @Missake212 commented on GitHub (Aug 2, 2025): > Not much luck finding anything in shadps4, but tried taking a look in ghidra: > > ``` > 038ce7b0 is func in game that crashes, patching out faulting insns at 38ce9b5 just causes a crash in different func, patching func to `ret` gets rid of crash but causes graphical issues > 03ac4270 calls func above, patching that to `ret` gives same gfx issues as above > 038f83e0 calls the func above twice, patching that to `ret` gets rid of crash without gfx issue > ``` > > So guess 038ce7b0 must be doing something weird, a lot of rsp/stack accesses there, afaik faulting insn comes from reading a ptr from rsp which is 0 and trying to deref that ptr (even though func should be setting that ptr to something that isn't 0?) > > Patching 038f83e0 to ret seems to work but might just be the same as deleting sfx folder though (iirc I used to still get crashes even with sfx deleted on 12th gen, haven't seen any crash with this yet but hadn't played that long with it), possible it could disable some other non-crashing effects though. > > Here's patch xml if anyone wants to try > > ``` > <Metadata Title="Bloodborne" Name="Intel 12th Gen+ Hack" Note="" Author="emoose" PatchVer="1.0" AppVer="01.09" AppElf="eboot.bin" isEnabled="true"> > <PatchList> > <Line Type="byte" Address="0x02CF83E0" Value="c3"/> > </PatchList> > </Metadata> > ``` Tested the game for a bit with the patch, not crashes on my end and all the sfx I looked at worked as expected, you could PR that to the shadPS4 patches and cheats repo https://github.com/shadps4-emu/ps4_cheats. I don't like to insist on things but I think opening a new issue would help you have more visibility on this work you've done, I'll also see if the Intel issue can be unlocked or not. EDIT: the issue has been unlocked if you want to move the convo there, your call.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Missake212 commented on GitHub (Sep 19, 2025):

I think it would be better from now on to only have the current issues show up and delete the ones that are fixed imo.

<!-- gh-comment-id:3312140574 --> @Missake212 commented on GitHub (Sep 19, 2025): I think it would be better from now on to only have the current issues show up and delete the ones that are fixed imo.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Missake212 commented on GitHub (Sep 27, 2025):

@Hermiten I think you should remove the "Pthread Assertion failed" and the "Rog ALLY crash" issues from here, they're not Bloodborne related (you will also need to remove the Bloodborne label from the Rog ALLY crash one).

<!-- gh-comment-id:3342004170 --> @Missake212 commented on GitHub (Sep 27, 2025): @Hermiten I think you should remove the "Pthread Assertion failed" and the "Rog ALLY crash" issues from here, they're not Bloodborne related (you will also need to remove the Bloodborne label from the Rog ALLY crash one).

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@RuneFFF commented on GitHub (Jan 9, 2026):

Lighting in the chalice dungeons does not work correctly, everything is very bright. This happens for all chalice dungeons, regardless of area.

Arch Linux / Ryzen 5 3600 / Radeon RX6800XT / 32GB RAM

<!-- gh-comment-id:3730481025 --> @RuneFFF commented on GitHub (Jan 9, 2026): Lighting in the chalice dungeons does not work correctly, everything is very bright. This happens for all chalice dungeons, regardless of area. Arch Linux / Ryzen 5 3600 / Radeon RX6800XT / 32GB RAM

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@1vanK commented on GitHub (Feb 14, 2026):

Is this known issue?

I see something similar after every death and even without deaths at random moments in time

I tried different versions, including the nightly build.

<!-- gh-comment-id:3901340947 --> @1vanK commented on GitHub (Feb 14, 2026): Is this known issue? I see something similar after every death and even without deaths at random moments in time <img width="1282" height="752" alt="Image" src="https://github.com/user-attachments/assets/ee1b0f43-9756-42b6-be66-d739b2a8e833" /> I tried different versions, including the nightly build.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@StevenMiller123 commented on GitHub (Feb 19, 2026):

@1vanK Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions.

@nyomen Please avoid promoting mods/patches for Bloodborne. This is an issue about emulation issues, and these mods are workarounds to the problem.

<!-- gh-comment-id:3927558651 --> @StevenMiller123 commented on GitHub (Feb 19, 2026): @1vanK Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions. @nyomen Please avoid promoting mods/patches for Bloodborne. This is an issue about emulation issues, and these mods are workarounds to the problem.

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@1vanK commented on GitHub (Feb 19, 2026):

@1vanK Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions.

with this the game freezes or crashes

<!-- gh-comment-id:3927602913 --> @1vanK commented on GitHub (Feb 19, 2026): > [@1vanK](https://github.com/1vanK) Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions. with this the game freezes or crashes

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@Ambear1337 commented on GitHub (Feb 22, 2026):

@1vanK Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions.

with this the game freezes or crashes

Confirming
Enabled readbacks settings and game's performance halved
Saw in #1232 issue that there is way to fix performance issue with enabled readbacks. Is it possible for common user to do?

<!-- gh-comment-id:3940485849 --> @Ambear1337 commented on GitHub (Feb 22, 2026): > > [@1vanK](https://github.com/1vanK) Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions. > > with this the game freezes or crashes Confirming Enabled readbacks settings and game's performance halved Saw in #1232 issue that there is way to fix performance issue with enabled readbacks. Is it possible for common user to do? <img width="1141" height="515" alt="Image" src="https://github.com/user-attachments/assets/c3d04e8b-c604-4931-9874-361fbc1bcc0e" />

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@evill33t commented on GitHub (Feb 22, 2026):

@1vanK Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions.

with this the game freezes or crashes

Confirming Enabled readbacks settings and game's performance halved Saw in #1232 issue that there is way to fix performance issue with enabled readbacks. Is it possible for common user to do?

this seems to break the game

[Debug] <Critical> (shadPS4:GpuCommandProcessor) page_manager.cpp:69 operator(): Assertion Failed! Not enough watchers

<!-- gh-comment-id:3940600755 --> @evill33t commented on GitHub (Feb 22, 2026): > > > [@1vanK](https://github.com/1vanK) Bloodborne requires enabling the readbacks setting, that will fix the vertex explosions. > > > > > > with this the game freezes or crashes > > Confirming Enabled readbacks settings and game's performance halved Saw in [#1232](https://github.com/shadps4-emu/shadPS4/issues/1232) issue that there is way to fix performance issue with enabled readbacks. Is it possible for common user to do? > > <img alt="Image" width="1141" height="515" src="https://private-user-images.githubusercontent.com/11291587/553157974-c3d04e8b-c604-4931-9874-361fbc1bcc0e.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NzE3NTM4NjYsIm5iZiI6MTc3MTc1MzU2NiwicGF0aCI6Ii8xMTI5MTU4Ny81NTMxNTc5NzQtYzNkMDRlOGItYzYwNC00OTMxLTk4NzQtMzYxZmJjMWJjYzBlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjAyMjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwMjIyVDA5NDYwNlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWM2NjFhNGJkOWE4OGYxODk1YzZkZWE5NTAzZDQ5YWMwZWM4MDE1MjZhOWNjOWJmMGNjYWM3OTA4N2I4NGIyZmMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.QOBeSE37qEGA4GaYNitpHsxbjZ2UQT7GWDWeu4j89ko"> this seems to break the game `[Debug] <Critical> (shadPS4:GpuCommandProcessor) page_manager.cpp:69 operator(): Assertion Failed! Not enough watchers`

kerem commented 2026-02-27 21:06:54 +03:00

Author

Owner

Copy link

@CyberDreamer666 commented on GitHub (Feb 22, 2026):

Hello, I don't know if anyone else has asked this or if this is a known issue... Allies' names are not positioned above the character themselves on different resolution patches. I tested them on 560p, 720p, and 900p. I'm attaching the logs if it helps. My specs: CPU i7 8750H, 32GB RAM, 6GB VRAM (1060). I've noticed a trend: if you don't select a resolution patch, the name will display normally, but the game will lag. Is there a way or advice on how to fix this at the resolutions listed above or at least 720p ? In the logs, the last thing I tested was 720p.

560p.bmp
720p.bmp
900p.bmp
shad_log.txt
shadPS4Launcher.log

<!-- gh-comment-id:3941650509 --> @CyberDreamer666 commented on GitHub (Feb 22, 2026): Hello, I don't know if anyone else has asked this or if this is a known issue... Allies' names are not positioned above the character themselves on different resolution patches. I tested them on 560p, 720p, and 900p. I'm attaching the logs if it helps. My specs: CPU i7 8750H, 32GB RAM, 6GB VRAM (1060). I've noticed a trend: if you don't select a resolution patch, the name will display normally, but the game will lag. Is there a way or advice on how to fix this at the resolutions listed above or at least 720p ? In the logs, the last thing I tested was 720p. [560p.bmp](https://github.com/user-attachments/files/25472096/560p.bmp) [720p.bmp](https://github.com/user-attachments/files/25472097/720p.bmp) [900p.bmp](https://github.com/user-attachments/files/25472100/900p.bmp) [shad_log.txt](https://github.com/user-attachments/files/25472098/shad_log.txt) [shadPS4Launcher.log](https://github.com/user-attachments/files/25472099/shadPS4Launcher.log)

kerem referenced this issue 2026-02-27 21:13:21 +03:00

[PR #556] [MERGED] Handle PM4 type-2 packets #1631

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

trophies_and_saves

user_and_settings

0.15.1branch_part6

Pre-release-shadPS4-2026-04-24-737d23b28b4ea9bea299f4a399e88d6926cdbe6e

v.0.15.0

Pre-release-shadPS4-2026-02-26-19d2027105679d751328357d7c85cd83a84c9758

v.0.14.0

v.0.13.0

v.0.12.5

v.0.12.0

v.0.11.0

v.0.10.0

v.0.9.0

v.0.8.0

v.0.7.0

v.0.6.0

v.0.5.0

v.0.4.0

v.0.3.0

v.0.2.0

0.1.0

v0.0.3

v0.0.2

v0.0.1

Labels

Clear labels   

Bloodborne

  

bug

  

contributor wanted

  

documentation

  

enhancement

  

frontend

  

good first issue

  

help wanted

  

linux

  

pull-request

Mirrored from GitHub Pull Request

  

question

  

release

  

verification progress

No labels

Bloodborne

bug

contributor wanted

documentation

enhancement

frontend

good first issue

help wanted

linux

pull-request

question

release

verification progress

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/shadPS4#556

No description provided.