mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-26 16:25:58 +03:00
[GH-ISSUE #3589] [GAME BUG]: Bloodborne water regression #1071
Labels
No labels
Bloodborne
bug
contributor wanted
documentation
enhancement
frontend
good first issue
help wanted
linux
pull-request
question
release
verification progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/shadPS4#1071
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Missake212 on GitHub (Sep 13, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/3589
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
There's been a regression with water in Bloodborne for a bit now, no one has decided to open an issue about it so I decided to do it, I'm not sure if it's GPU vendor or OS specific either since no one shares information about it but you can take a look at the video to see what it's about.
https://github.com/user-attachments/assets/0a7b8d20-4d2b-4f34-81b0-6a5f90e52a0f
Reproduction Steps
Just need to go to an area with water and it should appear (in my case I was in Byrgenwerth). I'm not 100% sure about this but I believe the issue is related to reflections, since it doesn't happen on every single body of water in the game in my quick testing.
Specify OS Version
Windows 11
CPU
Intel Core I9 13900K
GPU
Nvidia RTX 4090
Amount of RAM in GB
32 GB
Amount of VRAM in GB
24 GB
Log File
CUSA03173.log
@RuskyDed commented on GitHub (Sep 13, 2025):
Known issue with Nvidia since #3447. Turtle is aware, but thanks for opening this as a reminder.
@squidbus commented on GitHub (Sep 13, 2025):
Linking to relevant comment: https://github.com/shadps4-emu/shadPS4/pull/3447#issuecomment-3218510274
@StevenMiller123 commented on GitHub (Feb 16, 2026):
I believe this regression has been fixed?
Correct me if I'm wrong, and I can reopen this.