You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
5120×2160 (21:9) is now a native resolution, under Ultrawide or 16:10 in the launcher. It runs at 60 FPS in Central Yharnam on an M4 Max. It's heavy, so on Macs with less than 24 GB the launcher shows a memory warning.
The mouse cursor hides after 3 seconds without moving over the game window, and comes back as soon as you move or click.
5120×2160 (21:9) is now a native resolution, under Ultrawide or 16:10 in the launcher. It runs at 60 FPS in Central Yharnam on an M4 Max. It's heavy, so on Macs with less than 24 GB the launcher shows a memory warning.
The mouse cursor hides after 3 seconds without moving over the game window, and comes back as soon as you move or click.
Let me know how 5120×2160 looks on your display.
Written with Claude Code.
The game now crashes on startup while selecting 5120x2160 with version 0.5.10.
Warnings and errors before the cause (3 most recent)
23:12:44.887 WARN GPU [Render.Vulkan] <Warning> vk_pipeline_serialization.cpp:390 LoadPipelineStage: Cached permutation 0 of fs_fbe7c4b6 conflicts with index 1, skipping preload
23:12:44.896 WARN GPU [Render] <Warning> vk_pipeline_serialization.cpp:511 WarmUp: 1 cached pipelines could not be preloaded; they compile when used
23:12:50.245 WARN == Stall during rendering at flush 1
game-2026-10-27_23-12-42.log (76 lines around the cause)
23:12:50.171 INFO Runtime: guest thread 'CSChrThread2' is host thread 962556, handle 0x805c51a10 (affinity 0xf, prio 700)
23:12:50.171 INFO Runtime: guest thread 'CSChrThread3' created (stack=65536, prio=700)
23:12:50.171 INFO Runtime: guest thread 'CSChrThread3' affinity 0xf
23:12:50.171 INFO Runtime: guest thread 'CSChrThread3' is host thread 962557, handle 0x805c51810 (affinity 0xf, prio 700)
23:12:50.171 INFO Runtime: guest thread 'CSChrThread4' created (stack=65536, prio=700)
23:12:50.171 INFO Runtime: guest thread 'CSChrThread4' affinity 0x30
23:12:50.171 INFO Runtime: guest thread 'CSChrThread4' is host thread 962558, handle 0x805c51610 (affinity 0x30, prio 700)
23:12:50.171 INFO Runtime: guest thread 'CSChrThread5' created (stack=65536, prio=700)
23:12:50.171 INFO Runtime: guest thread 'CSChrThread5' affinity 0x30
23:12:50.171 INFO Runtime: semaphore id=66, attr=2, initial=0, max=1
23:12:50.171 INFO Runtime: semaphore id=67, attr=2, initial=0, max=1
23:12:50.171 INFO Runtime: guest thread 'CSChrThread5' is host thread 962559, handle 0x805c51410 (affinity 0x30, prio 700)
23:12:50.172 INFO Runtime: guest thread 'CSChrBackInitialize1' created (stack=65536, prio=700)
23:12:50.172 INFO Runtime: guest thread 'CSChrBackInitialize1' affinity 0x3e
23:12:50.172 INFO Runtime: guest thread 'CSChrBackInitialize1' is host thread 962560, handle 0x805c51210 (affinity 0x3e, prio 700)
23:12:50.172 INFO Runtime: semaphore id=68, attr=2, initial=0, max=1
23:12:50.172 INFO Runtime: semaphore id=69, attr=2, initial=0, max=1
23:12:50.172 INFO Runtime: guest thread 'CSClothThread0' created (stack=65536, prio=700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread0' affinity 0xf
23:12:50.172 INFO Runtime: guest thread 'CSClothThread0' is host thread 962561, handle 0x805c51010 (affinity 0xf, prio 700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread1' created (stack=65536, prio=700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread1' affinity 0xf
23:12:50.172 INFO Runtime: guest thread 'CSClothThread1' is host thread 962562, handle 0x805c50e10 (affinity 0xf, prio 700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread2' created (stack=65536, prio=700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread2' affinity 0xf
23:12:50.172 INFO Runtime: guest thread 'CSClothThread2' is host thread 962563, handle 0x805c50c10 (affinity 0xf, prio 700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread3' created (stack=65536, prio=700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread3' affinity 0xf
23:12:50.172 INFO Runtime: guest thread 'CSClothThread3' is host thread 962564, handle 0x805c50a10 (affinity 0xf, prio 700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread4' created (stack=65536, prio=700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread4' affinity 0x30
23:12:50.172 INFO Runtime: guest thread 'CSClothThread4' is host thread 962565, handle 0x805c50810 (affinity 0x30, prio 700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread5' created (stack=65536, prio=700)
23:12:50.172 INFO Runtime: guest thread 'CSClothThread5' affinity 0x30
23:12:50.172 INFO Runtime: guest thread 'CSClothThread5' is host thread 962566, handle 0x805c50610 (affinity 0x30, prio 700)
23:12:50.236 INFO Sampler: game uses min filter 0, mip filter 1, anisotropy 1x
23:12:50.236 INFO Sampler: game uses min filter 1, mip filter 2, anisotropy 1x
23:12:50.245 WARN == Stall during rendering at flush 1
23:12:51.006 INFO Runtime: open(/app0/dvdroot_ps4/map/m24/m24_9999.tpf.dcx) -> not found
23:12:51.419 INFO Runtime: open(/app0/dvdroot_ps4/map/m27/m27_9999.tpf.dcx) -> not found
23:12:52.043 CRIT Crash: the game crashed (signal 11 at guest offset 0x2166b8a)
23:12:52.043 INFO Guest fault (signal 11) at guest offset 0x2166b8a, address 0x38
23:12:52.043 INFO rax=0x8 rbx=0x800 rdi=0x70282a2710 rsi=0x7032c39338 rsp=0x806496d70
23:12:52.054 INFO #2 0x8064962c0
23:12:52.054 INFO #3 0x800ef6df5
23:12:52.054 INFO #4 0x800ef2b71
23:12:52.054 INFO #5 0x802869823
23:12:52.054 INFO #6 0x802b6e2dd
23:12:52.054 INFO #7 0x802b6e3a4
23:12:52.054 INFO #8 0x802b6e3a4
23:12:52.054 INFO #9 0x802b6e4f8
23:12:52.054 INFO #10 0x802ac9087
23:12:52.054 INFO #11 0x802ac95ed
23:12:52.054 INFO #12 0x800f297ed
23:12:52.054 INFO #13 0x801eee6a7
23:12:52.054 INFO #14 0x8013f7835
23:12:52.054 INFO #15 0x800fe7125
23:12:52.054 INFO #16 0x800f812b4
23:12:52.054 INFO #17 0x800f80892
23:12:52.054 INFO #18 0x80142c137
23:12:52.054 INFO #19 0x80142da49
23:12:52.054 INFO #20 0x80103d438
23:12:52.054 INFO #21 0x80103d2c1
23:12:52.054 INFO #22 0x801067579
23:12:52.054 INFO #23 0x80103deff
23:12:52.054 INFO #24 0x800f8a48c
23:12:52.054 INFO #25 0x800f88ceb
23:12:52.054 INFO #26 0x802018e74
23:12:52.054 INFO #27 0x801e4a6f5
23:12:52.054 INFO #28 0x8000000df
23:12:52.054 INFO #29 /Applications/Bloodborne.app/Contents/MacOS/bb-probe+0xaa3 (enter_on_stack)
23:12:52.054 INFO #30 /Applications/Bloodborne.app/Contents/MacOS/bb-probe+0x25ae7 (probe_main.cold.67)
23:12:52.054 INFO #31 /Applications/Bloodborne.app/Contents/MacOS/bb-probe+0x3af7 (probe_main)
23:12:52.054 INFO bbgpu-host: exiting: control port died (bb-probe exited)
23:12:52.054 INFO Exit: pipeline archive flushed in 0 ms
23:12:52.173 ERROR launcher: the game stopped with status 139 after 0 min 9 s
Update: the idle cursor hiding in 0.5.10 is confirmed working here. A still mouse pointer over the game window disappears after 3 seconds and comes back as soon as you move the mouse. If you get a chance, please let us know whether 5120x2160 works on your display.
5. 5120x2160 does not work, it either crashes or loads in with textures missing
unsure if directly related to 5120x2160 as other people have reported crashing also
You're going to need to supply logs, there is no way I can test or reproduce this as I don't have a monitor supporting that resolution,
Sorry, you did post a log. Thanks. It shows the game failing to create one of its own render textures while loading, which points to the game running out of graphics memory at 5120x2160. That fits the missing textures too. It loads and runs here on the same settings (90 FPS cap, fixed timing), so something in your setup needs more. Could you attach the full crash zip from ~/Library/Logs/Bloodborne/Reports (it has your settings and the whole log)? Also, does 3440x1440 work for you?
9. I posted the zip file above for you
yes it works on 3440x1440
but i would obviously want to run it at my native resolution if possible, also my monitor doesn't do anything past 60hz at 3440x1440 sadly
I got 36gb of ram that leaves about 24-26gb for the gpu
It's not your machine that's the issue, it's the game's own memory allocation. Allocating more VRAM does fix the render but the fps drops to 5 - 15fps a short while afterwards on my M4 Max / 48GB. I am looking into why.
10. > 9. I posted the zip file above for you
> yes it works on 3440x1440
> but i would obviously want to run it at my native resolution if possible, also my monitor doesn't do anything past 60hz at 3440x1440 sadly
> I got 36gb of ram that leaves about 24-26gb for the gpu
It's not your machine that's the issue, it's the game's own memory allocation. Allocating more VRAM does fix the render but the fps drops to 5 - 15fps a short while afterwards on my M4 Max / 48GB. I am looking into why.
After testing version 0.5.11 5120x2160 now boots and runs correctly, and looks amazing but on my machine a Mac studio m5 max with 36gb of ram it can only achieve a playable frame rate with all graphics options off and texture set to lowest I get about 55-70fps at that resolution
If I set graphics settings to the highest the game uses too much ram and runs at like 30fps, not sure if this can be further optimized
If I may request another ultrawide resolution 3840x1620 in the meantime, this would look great on this monitor and allow me to run at a higher FPS. This seems to be the popular middle ground for people using a 5k2k monitor.
Thank you so much for the work, Bloodborne is possibly my favourite game of all time. The work you have done here for Mac users is appreciated.
Thank you @brewboi, great to hear 5120×2160 works now, and thanks for the frame rate details. At that size with high settings the game needs about 9 GB of graphics memory on top of everything else, so on a 36 GB Mac lower texture settings are the realistic choice for now.
3840×1620 is a good suggestion, the natural middle size for 5K2K monitors. 0.5.12 was the last 0.5.x release (fixes only), so I've noted it for 0.6. I'll keep this issue open for it.
No community patch existed for this size, so it's Kyo's 5120×2160 patch with the width and height scaled down. Both sizes are exactly the same shape, so the camera and HUD values should carry over, but nobody has seen it on screen yet, so you're the first.
Download Bloodborne-macOS-0.5.16-test1.zip, unzip it, and drag Bloodborne.app into Applications (replacing the old one).
Clear the quarantine in Terminal: xattr -dr com.apple.quarantine /Applications/Bloodborne.app
In the launcher, choose 3840 × 1620 · 21:9 under Ultrawide or 16:10, then start the game and load your save.
Could you tell us:
Does the picture fill the screen without stretching or black bars?
Does the HUD (health, items, messages) sit in the right places?
Do the lock-on marker and enemy health bars appear over the right targets?
Roughly what FPS you get (⌘, shows it), at your usual settings.
A screenshot or two would help a lot. To go back, download 0.5.15 from the releases page. If it looks right, it goes into 0.5.16.
@brewboi 3840×1620 is in 0.5.16 (under Ultrawide or 16:10 in the launcher). It hasn't been seen on a real 5K2K screen yet, so please tell us how the picture, HUD and camera look when you start your playthrough.
Activity
Ultrawide: 5120x2160 (21:9) native resolution (#93)
Window: hide a still cursor over the game after 3 s (#93)
Wooloomooloo2 commentedon Oct 27, 2026
Both are in 0.5.10:
Let me know how 5120×2160 looks on your display.
Written with Claude Code.
brewboi commentedon Oct 28, 2026
The game now crashes on startup while selecting 5120x2160 with version 0.5.10.
Bloodborne for Mac 0.5.10: crash report
Warnings and errors before the cause (3 most recent)
game-2026-10-27_23-12-42.log (76 lines around the cause)
Wooloomooloo2 commentedon Oct 28, 2026
Update: the idle cursor hiding in 0.5.10 is confirmed working here. A still mouse pointer over the game window disappears after 3 seconds and comes back as soon as you move the mouse. If you get a chance, please let us know whether 5120x2160 works on your display.
brewboi commentedon Oct 28, 2026
5120x2160 does not work, it either crashes or loads in with textures missing
unsure if directly related to 5120x2160 as other people have reported crashing also
Wooloomooloo2 commentedon Oct 28, 2026
You're going to need to supply logs, there is no way I can test or reproduce this as I don't have a monitor supporting that resolution,
brewboi commentedon Oct 28, 2026
crash-2026-10-28_04-41-22.zip
Wooloomooloo2 commentedon Oct 28, 2026
Sorry, you did post a log. Thanks. It shows the game failing to create one of its own render textures while loading, which points to the game running out of graphics memory at 5120x2160. That fits the missing textures too. It loads and runs here on the same settings (90 FPS cap, fixed timing), so something in your setup needs more. Could you attach the full crash zip from
~/Library/Logs/Bloodborne/Reports(it has your settings and the whole log)? Also, does 3440x1440 work for you?brewboi commentedon Oct 28, 2026
I posted the zip file above for you
yes it works on 344 8000 0x1440
but i would obviously want to run it at my native resolution if possible, also my monitor doesn't do anything past 60hz at 3440x1440 sadly
I got 36gb of ram that leaves about 24-26gb for the gpu
Wooloomooloo2 commentedon Oct 28, 2026
It's not your machine that's the issue, it's the game's own memory allocation. Allocating more VRAM does fix the render but the fps drops to 5 - 15fps a short while afterwards on my M4 Max / 48GB. I am looking into why.
brewboi commentedon Oct 28, 2026
thanks for the effort
Ultrawide: 5120x2160 gets a bigger first graphics heap (#93)
README: 0.5.11 (5120x2160 draws the level, long-session crash fixed, #93
brewboi commentedon Oct 29, 2026
After testing version 0.5.11 5120x2160 now boots and runs correctly, and looks amazing but on my machine a Mac studio m5 max with 36gb of ram it can only achieve a playable frame rate with all graphics options off and texture set to lowest I get about 55-70fps at that resolution
If I set graphics settings to the highest the game uses too much ram and runs at like 30fps, not sure if this can be further optimized
If I may request another ultrawide resolution 3840x1620 in the meantime, this would look great on this monitor and allow me to run at a higher FPS. This seems to be the popular middle ground for people using a 5k2k monitor.
Thank you so much for the work, Bloodborne is possibly my favourite game of all time. The work you have done here for Mac users is appreciated.
Wooloomooloo2 commentedon Oct 31, 2026
Thank you @brewboi, great to hear 5120×2160 works now, and thanks for the frame rate details. At that size with high settings the game needs about 9 GB of graphics memory on top of everything else, so on a 36 GB Mac lower texture settings are the realistic choice for now.
3840×1620 is a good suggestion, the natural middle size for 5K2K monitors. 0.5.12 was the last 0.5.x release (fixes only), so I've noted it for 0.6. I'll keep this issue open for it.
brewboi commentedon Nov 8, 2026
thanks I'm waiting for that 3840x1620 resolution update before I truly start my play through, no rush of course!
Wooloomooloo2 commentedon Nov 12, 2026
@brewboi 3840×1620 is ready to try in a test build: 0.5.16-test1.
No community patch existed for this size, so it's Kyo's 5120×2160 patch with the width and height scaled down. Both sizes are exactly the same shape, so the camera and HUD values should carry over, but nobody has seen it on screen yet, so you're the first.
Bloodborne-macOS-0.5.16-test1.zip, unzip it, and dragBloodborne.appinto Applications (replacing the old one).xattr -dr com.apple.quarantine /Applications/Bloodborne.appCould you tell us:
A screenshot or two would help a lot. To go back, download 0.5.15 from the releases page. If it looks right, it goes into 0.5.16.
Written with Claude Code.
Wooloomooloo2 commentedon Nov 14, 2026
@brewboi 3840×1620 is in 0.5.16 (under Ultrawide or 16:10 in the launcher). It hasn't been seen on a real 5K2K screen yet, so please tell us how the picture, HUD and camera look when you start your playthrough.
Written with Claude Code.
Native ultrawide: 3840x1620 (21:9) for 5K2K monitors (Wooloomooloo2#93)