mirror of
https://github.com/shadps4-emu/shadPS4.git
synced 2026-04-27 16:56:03 +03:00
[GH-ISSUE #2119] [GAME BUG]: Apple M4 Pro - CUSA03173 Bloodborne - Crashes after a few seconds into gameplay (Possible hotfix using terminal?) #735
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#735
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 @sdk417 on GitHub (Jan 10, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2119
Checklist (we expect you to perform these steps before opening the issue)
Describe the Bug
First of all, sorry if this a duplicate of a known issue, but aside of the crashing bug, I will detail how I managed to get prolonged sessions of gameplay on MacOS for Bloodborne using an M4 series chip.
Without any resolution patches applied, the game will crash after a few seconds into gameplay.
With the 720p or 626p resolution patch enabled, the session can last for about one minute before crashing.
While testing different environment variables using the MacOS' Terminal, I found that using "export MVK_CONFIG_RESUME_LOST_DEVICE=1" helps the emulator avoid those previous crashes and let the gameplay continue for about 10-15 minutes before completely crashing.
However, this will result in textures and lights start to flicker like crazy after a few crashes avoided. The player model or some NPCs textures can be distorted (similar behavior like the vertex explosion issue).
Reproduction Steps
In-game crash. No patches enabled (just HTTP disabled for the sake of cleaner logs).
https://github.com/user-attachments/assets/65019bb3-8c7b-435c-9914-81613edbf3aa
no patches enabled.txt
720 patch enabled. Enviroment variables used:
export MVK_CONFIG_LOG_LEVEL=4
export MVK_CONFIG_RESUME_LOST_DEVICE=1
./shadps4.app/Contents/MacOS/shadps4
Terminal debug logs can be seen on the left side of the screen.
You can see how the game tries to crash at several moments (different "[MKV-warn] errors" appear on the logs)
https://github.com/user-attachments/assets/2d5b6048-3755-46f7-aed1-f9cdd4c77f94
I was able to prolong the session for 14 minutes before the game finally crashed.
I was able to finish the Hemwick area, teleport to Hunter's Dream and do the whole Central Yharnam level until the Cleric Beast boss arena.
https://github.com/user-attachments/assets/94af3058-96c8-4390-bd93-7c2b911a1624
720p patch enabled + variables.txt
I also tested the game with those variables and no resolution patches and could get around 7 minutes of gameplay without crashing.
Note that this is not 100% consistent and that some times it could result in fewer session time.
Whenever there are visual bugs, a quick save and reload can fix some of these.
variables enabled without patches.txt
Specify OS Version
MacOS 15.3
CPU
Apple M4 Pro
GPU
Apple M4 Pro
Amount of RAM in GB
24GB RAM shared with CPU/GPU
Amount of VRAM in GB
24GB RAM shared with CPU/GPU
Log File
no patches enabled.txt
720p patch enabled + variables.txt
@squidbus commented on GitHub (Feb 4, 2025):
This may be fixed by
github.com/shadps4-emu/shadPS4@b879dd59c6(I don't seem to be getting a lot of device loss crashes anymore with it), can you check the latest main build?@sdk417 commented on GitHub (Feb 4, 2025):
I have updated to latest main and played for about 15-20 minutes without any crashes.
I will do a long play session later on today to keep testing, but seems to be solved 🙏
@sdk417 commented on GitHub (Feb 4, 2025):
I managed to get about one hour of gameplay before crashing. After that, the next one happened about 15 minutes into gameplay. Crashes are substantially less frequent now.
m4 crashes.txt
@sdk417 commented on GitHub (Feb 16, 2025):
This has been solved. Played through the whole game (doing long gameplay sessions) and didn't have any more VK_ERROR_DEVICE_LOST crashes with the latest 0.6.1 PRs.