Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[GAME BUG]: Bloodborne crashes when playing certain cutscenes #2034

Open
5 tasks done
brad0demx opened this issue Jan 3, 2025 · 9 comments
Open
5 tasks done

[GAME BUG]: Bloodborne crashes when playing certain cutscenes #2034

brad0demx opened this issue Jan 3, 2025 · 9 comments

Comments

@brad0demx
Copy link

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

When creating a new character, some hardware experiences consistent crashing using any build on main branch sicne commit 48c51bd. I say "some hardware" as with my testing, this crash has been 100% consistent. However Missake and Rainmaker don't seem to have the same consistency in their tests.
In my testing, this crash doesn't occur on Linux.

Reproduction Steps

Main branch from 48c51bd to 345d556
(Latest at time of writing) and clicking new save. Crash occurs as the cut scene begins.

Specify OS Version

Windows 11

CPU

5600X

GPU

NVIDIA 2080 SUPER

Amount of RAM in GB

32GB

Amount of VRAM in GB

8GB

Logs

shad_log(1).txt

@hspir404
Copy link
Contributor

hspir404 commented Jan 3, 2025

Fairly consistent crashes as soon as I open the FMV. I am seeing a variety of stack traces, but mostly all resolving down to some variation of null pointer dereference in locking code or thread local storage, as well as being related to SDL audio.

Ryzen 5950x, 3080 10GB VRAM, 64GB RAM, Windows 10.

I did a git bisect, and this commit seemed to be the start of this problem for me: 48c51bd

@Missake212
Copy link

I get a lot of crashes on character creation on these new builds but they're not 100% consistent, I also noticed the audio crackling a bit recently on BB.

13900k, 4090, 32Gb RAM, Windows 11 24h2

shad_log.txt

@MouseManSpecOps
Copy link

From what others have said on this forum, Nvidia graphic cards do not gel well with ShadPS4 at the moment. I'm still trying to figure out what can be done to get me to play beyond Character Creation.

@GHU7924
Copy link

GHU7924 commented Jan 6, 2025

Apparently the error is "floating?", there were these last lines in the log:

[Lib.AvPlayer] avplayer_source.cpp:EnableStream:221: Audio stream 2 enabled
[Lib.AvPlayer] avplayer_source.cpp:GetStreamInfo:113: Stream 3 language = und
[Lib.AvPlayer] avplayer_source.cpp:GetStreamInfo:137: Stream 3 is an audio stream.
[Lib.AvPlayer] avplayer_source.cpp:GetStreamInfo:113: Stream 4 language = und
[Lib.AvPlayer] avplayer_source.cpp:GetStreamInfo:

or

[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue bac

or

[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (66560 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (77312 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (66560 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (74240 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (74240 queued, 65536 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AvPlayer] avplayer_source.cpp:DemuxerThread:463: EOF reached in demuxer. Exiting.
[Lib.AvPlayer] avplayer_source.cpp:AudioDecoderThread:779: Audio Decoder Thread exited normally
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (66560 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.
[Lib.AudioOut] sdl_audio.cpp:Output:64: SDL audio queue backed up (65536 queued, 61440 threshold), clearing.

All this happens only in the first video, then everything is fine.
In the latter case, there was a black screen and a broken sound.

@Masterno25
Copy link

Masterno25 commented Jan 8, 2025

I always crash after doing the basic settings in the main screen, however I did manage to make it past this a single time and I had a black screen with a weird sound.

i7-9700k, 2070 SUPER, 32GB Ram, AtlasOS 0.3.2
on 39cbfed
And from my testing, I pretty much always get the same last lines in the log files as the person above me

shad_log.txt
shad_log.txt

@brad0demx
Copy link
Author

Those logs, and that commit you referenced are both from unofficial forks. Please test again on latest main 65f9bbb .
Kind of weird you get the crash on Linux, with my testing I didnt experience it on there at all

@Missake212
Copy link

After some more digging it looks like the crashes happen during certain cutscenes, and all of those cutscenes are in the same folder (the movie folder in the game files, also all those cutscenes are .mp4 instead of the regular .dcx for the cutscenes in the remo folder). There's 4 of them, one plays when you're afk on the main menu, one when you start a new game and two are credits that show up for different endings, I've tried them all and they all can cause this crash, also for some reason it seems like you're more prone to crash when downloading a new build rather than using one you've updated (this could be rng tbh). Here are some logs (tho they don't show a clear critical crash, you can notice Lib.avplayer appears before all those crashes) of the cutscene you get when afk on menu and the credit one:
CRASH BB INTRO shad_log.txt
CRASH BB CREDITS shad_log.txt

@brad0demx brad0demx changed the title [GAME BUG]: Bloodborne crashes at the cutscene when starting new save. [GAME BUG]: Bloodborne crashes when playing certain cutscenes Jan 12, 2025
@C4RTYP4NTS
Copy link

C4RTYP4NTS commented Jan 13, 2025

Take this fix with a grain of salt BUT Try putting in a save file in. Not 100% sure but I got my brother's Bloodborne working so far (or at least past the starting cutscene and character screens. You can save files on Nexus mods I will put them down below. For my brother, I had to take the save file I had going on my working bloodborne and copy and paste mine on his. I was lucky and didn't encounter any issues so I could get past the screens easily. I will also put a save file in if you wanna go for it. brand new run bttw so no progress. Just a few more levels put into strength.

All Class Save Files (TRIED) only tried male file btw so female file might work
https://www.nexusmods.com/bloodborne/mods/190

Bloodborne NG Plus Save (Encrypted and Decrypted) get decrypted for ShadPS4 (TRIED) NEW GAME FILE KNOW
https://www.nexusmods.com/bloodborne/mods/26

Save file after character creator (didn't TRY)
https://www.nexusmods.com/bloodborne/mods/95

My save file if none of those worked. This would be for version 1.0.9 (WORKED FOR ME)
Savefile Bloodborne.zip

Anyway**, I tried a couple of saves and it said his version was unsupported**. His Game is on version 1.0.9 same as mine so I just yoinked my save file on my PC and put it on his and it worked perfectly for the 30 seconds I saw. As soon as it was working I wanted to write this to see if I could help anyone. It has been at least half an hour and his game is still running good in the room. Sorry don't know names haven't played a lot of Bloodborne.

Real Quick how to get to ur userdatafile!
shadps4-win64-qt-0.5.0\user\savedata\1*CUSA00900*### SPRJ0005

Go into the file that corresponds ur Bloodborne (for me the text in the bold may be the same may be different) one you navigate to the file that has your userdata1-10 files and stuff just copy the save file YOU installed on the website or from me and PASTE all of the files into that last file over there in the bold and hopefully slightly bigger. Start up the game and pray. If you won't pray I will pray for you. Goodluck!!! Also I do not endorse installing random files from some random github user I just wanna try to help anyone willing to take that risk.

sorry if this looks rushed cause it very much is. sorry sorry wish u luck and I'm praying for yall.

@brad0demx
Copy link
Author

brad0demx commented Jan 13, 2025

That isn't a fix, that is a workaround for one aspect of the issue. Using other save files skips past the starter cutscene to avoid that crash, but doesn't account for Missake's discovery that the crash occurs on other cutscenes in the game. This issue was made to be added to the Aggregate Issue, so that people could verify the status of the problem, and that it is known until it's properly fixed by the developers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants