BLOODBORNE Get Bloodborne

Home › PC › Troubleshooting

Troubleshooting · Updated 2026-10-24

When the PC port will not boot

These are community-maintainer notes, not Sony support. First identify your fork and release, follow its game-version requirements, and check its Vulkan-driver requirements. A fix for one launcher is not a fix for every PC route.

Illustration of a brass lantern, field notes and an iron sword on a stone ledge
AI-generated field-notes illustration; not an in-game item or official artwork.
Illustration of a cloaked traveler facing a moonlit gothic cathedral
AI-generated site illustration; not an in-game screenshot or official artwork.

Mrsuss60 issue 163 reports a Python 3.12 DLL problem. On 23 October 2026, contributor HatsyRei suspected that the reporter was running Supermedo's fork and asked for confirmation. The comment does not establish a confirmed root cause.

First checks

The original bbport documents a 1.00 startup crash and requires 1.09. Supermedo's v1.9.4 README instead says 1.09 is required for community patches and other versions run at 30 FPS, while recommending a clean 1.09 setup. Check the selected project; do not generalize one crash report to shadPS4 or every fork.

Supermedo's troubleshooting note includes clearing the shader cache after crashes have left a stale pipeline cache. It is a context-specific step, not a universal cure. Keep a copy of your logs and match them to the exact build.

A narrowly scoped RDNA2 example

The cited Windows troubleshooting document describes version 1.6 on one Windows 11 machine with a Radeon RX 6900 XT and game 1.09. For its recorded GPU crashes it used BB_COPY_GPU_BUFFERS=1, the two-stage GPU pipeline off, BB_PREP_WORKERS=0 and object motion vectors off.

Those settings came from that environment and can affect speed or behavior. They are not a universal AMD fix or a tested recommendation for every newer release. Use the log signatures in the original note before applying them.

Questions

The screen stays black. What should I check?

Identify the exact fork and release first. Check its game-file and Vulkan requirements and its logs. Supermedo documents shader-cache clearing for a stale-cache crash scenario, not as a guaranteed fix for every black screen.

Was Mrsuss60 issue 163 caused by mixing forks?

A contributor suspected Supermedo's fork because the reported launcher file and tkinter use did not match the Mrsuss60 tree, and asked the reporter to confirm. The captured comment is a hypothesis, not a completed diagnosis.

Sources checked 2026-10-24

Related