BLOODBORNE Get Bloodborne

Home › PC › Native port

Native port · Updated 2026-10-24

The native PC port, fork by fork

bbport is a community runtime, not an official PC release or a repack of the game. It runs the original x86-64 executable with replacement system libraries and a Vulkan graphics backend. Its forks have different requirements and release schedules.

Illustration of a cloaked traveler facing a moonlit gothic cathedral
AI-generated site illustration; not an in-game screenshot or official artwork.
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.

The comparison separates maintainer documentation from performance evidence. No build was run here, and neither a high frame-rate option nor a release tag establishes that every area can be completed.

Four projects, four release histories

The original deadinside28 Linux project had release 0.6 dated 19 October 2026. The checked Windows releases were Supermedo windows-v1.9.4 and Mrsuss60 v0.6.5, both published 21 October. The checked ayozetr Linux/Steam Deck application release was 0.51-linux.16, published 22 October. Dates here are UTC publication dates.

Supermedo's v1.9.4 README describes a launcher, DLSS and FSR, frame-rate controls and community online features. Mrsuss60 is a separate Windows tree. ayozetr packages an AppImage for Linux and Steam Deck. These are maintainer-described features, not an independent benchmark.

Start Supermedo windows-v1.9.4 on Windows

This bounded workflow follows the fixed v1.9.4 README. Before starting, you must already have the files you are permitted to use: the complete game folder with a clean 1.09 eboot.bin; this fork documents CUSA03173. Ownership alone is not a blanket authorization to copy or bypass protection. No acquisition or circumvention instructions are provided here.

Check the requirements page first: this build needs 64-bit Windows 10 1903+ or Windows 11 and Vulkan 1.3. The archive below contains the community tool, not Bloodborne.

  • 1. Open the linked windows-v1.9.4 release, not a floating latest-download page, and select its Bloodborne-Windows.zip tool archive.
  • 2. Extract the archive to its own folder and start Bloodborne.exe. Do not combine files from another Windows fork.
  • 3. Select your existing complete game folder containing the clean 1.09 eboot.bin. An executable by itself is not the complete game folder.
  • 4. Follow the launcher's first-start checks for your files, PC, picture settings and controls, then press PLAY. The displayed frame-rate goal is not a benchmark guarantee.
  • 5. If startup fails, use the launcher's Help checks and Save a report, then match the log to this fork's support channel. Back up saves before importing them or changing builds.

Game versions are fork-specific

The original bbport README requires 1.09 and documents a startup crash with 1.00. That crash statement belongs to that implementation. Mrsuss60 and ayozetr also request 1.09.

Supermedo's fixed windows-v1.9.4 README says 1.09 is needed for community patches and says other versions run at 30 FPS. Its setup still recommends a clean 1.09 executable. This is not a guarantee that other versions can complete the game.

The original README identifies CUSA03173 as European GOTY, CUSA00900 as US and CUSA03023 as Asian, and describes matching 1.09 executables. That is compatibility documentation from a maintainer, not a publisher certification. No game files are included.

Questions

Does the native port include Bloodborne?

No. Supply the game files required by the selected project. The original bbport requires 1.09; Supermedo v1.9.4 distinguishes the 1.09 community-patch requirement from other versions running at 30 FPS.

Which fork is the port?

There is no single interchangeable package. deadinside28, Supermedo, Mrsuss60 and ayozetr maintain distinct trees. Match the release, instructions and issue tracker.

Is performance or a full clear guaranteed?

No. This page has not run a benchmark or verified a complete playthrough. Frame caps and upscaler options are not measured frame rates.

Sources checked 2026-10-24

Related