COMMUNITY PC GUIDE

Bloodborne Native Port vs shadPS4

Choose the native port for direct Windows or Linux installation if you have the required hardware and CUSA03173 v1.09 game folder. Keep a shadPS4 setup that already works for you. On a supported Apple Silicon Mac, shadPS4 is the available route here, with Bloodborne currently rated Ingame.

This page compares Supermedo Windows v1.5, Mrsuss60 Windows v0.2 and Linux bbport 0.4 with shadPS4. Use PC port projects to choose between native projects.

What changes between the routes?

Choice	Native Bloodborne ports	shadPS4
ChoicePurpose	Native Bloodborne portsA runtime made for Bloodborne	shadPS4A general PlayStation 4 emulator
ChoiceSystems	Native Bloodborne portsSeparate Windows and Linux projects	shadPS4Windows, Linux and supported Apple Silicon Macs
ChoiceLauncher	Native Bloodborne portsEach port supplies its own launcher	shadPS4Official QtLauncher, or an emulator launcher such as BBLauncher
ChoiceGame input	Native Bloodborne portsYour own decrypted CUSA03173 v1.09 folder	shadPS4Your own game data and required PS4 firmware modules; match the game's CUSA and operating system
ChoiceSetup focus	Native Bloodborne portsThe chosen project's game-data requirements, version and program release	shadPS4Hardware, emulator build and the game's compatibility record

The native ports run the original game's x86-64 CPU code through a dedicated runtime. Their graphics layer translates work to Vulkan with renderer and shader tools derived from shadPS4. You launch a Bloodborne-specific program; shadPS4 handles a wider range of PS4 games.

Which runs better?

On Linux with an RX 7800 XT, try bbport first for high frame rates. If shadPS4 already runs smoothly and reliably on your PC, keep that installation while testing the native port separately.

What matters to you	Native Bloodborne ports	shadPS4
What matters to youPerformance	Native Bloodborne portsLinux on an RX 7800 XT: about 90 FPS at 4K with FSR 4 Balanced, or about 150 FPS at 1440p with FSR 4 Quality. Supermedo and Mrsuss60 offer 30, 60, 90 and uncapped modes; start with 60 FPS. Keep Supermedo's frame-rate cap at 120 or below.	shadPS4Pick the emulator build from your matching compatibility record, then compare the same area at the same output resolution on your PC. Keep the route that gives you smoother movement and camera turns.
What matters to youStability	Native Bloodborne portsLinux is experimental. Start with its default memory mode; the new AMD mode can crash. On Windows, check that a new character saves and reloads before starting a long playthrough.	shadPS4The listed Bloodborne builds are Ingame, with game-breaking issues. Keep a build that already works for you while testing changes.
What matters to youEase of setup	Native Bloodborne portsWith your CUSA03173 v1.09 folder ready, use Supermedo's packaged `Bloodborne.exe`, Mrsuss60's `launcher.py` with Python 3.10+, or the Linux AppImage. The setup focuses on one game.	shadPS4Use QtLauncher, provide your game data and required PS4 firmware modules, and match the game ID, operating system and emulator build. This is the easier choice when you already have those pieces working.

FSR renders at a lower internal resolution and upscales to your selected output. Both Linux examples exceed 60 FPS: choose 1440p Quality when frame rate matters more, or try 4K Balanced for the higher output resolution on that GPU. For a fresh setup with the required native game folder already prepared, the native route has fewer setup pieces. On either route, test saving, reloading and the areas you want to play before moving your regular playthrough.

Compare hardware and systems

Requirement	Native ports	shadPS4
RequirementWindows	Native portsSupermedo: Windows 10 1903+ or 11, 64-bit. Mrsuss60: Windows 10/11, 64-bit	shadPS4Windows 10 or newer
RequirementLinux	Native portsx86-64 Linux	shadPS4Ubuntu 22.04 or newer
RequirementWindows/Linux CPU	Native portsMrsuss60 Windows: AVX2. Linux 0.4: AVX, BMI1, MOVBE, LZCNT, POPCNT and SSE4.2	shadPS4At least 4 cores and 6 threads, above 2.5 GHz, and x86-64-v3 support; Intel Haswell or AMD Excavator generation or newer
RequirementGraphics	Native portsVulkan 1.3; check the native installation table for project-specific Windows requirements	shadPS4At least 2 GB video memory and Vulkan 1.3 with `VK_KHR_swapchain` and `VK_KHR_push_descriptor`
RequirementExtra native software	Native portsSupermedo: the packaged program includes its components; no separate Python setup. Mrsuss60: Python 3.10+. Linux: use the AppImage	shadPS4Use the official Quickstart for your platform
RequirementAvailable memory	Native portsSupermedo: about 6 GB of free memory (RAM + pagefile), or 10 GB for 1440p/4K	shadPS4At least 8 GB RAM
RequirementCurrent Mac route	Native portsThe three bbport routes in our installation guide target Windows/Linux	shadPS4Apple M1 or newer, Rosetta 2 and macOS 26 or newer; Intel Macs are unsupported

If your CPU misses a required instruction set or the stated generation, choose a compatible machine. Switching from Windows to Linux does not add CPU instructions. Compare the Linux native list separately from shadPS4's x86-64-v3 requirement.

Bloodborne's current shadPS4 compatibility

The official list currently marks the following Bloodborne entries Ingame. That means the game reaches gameplay but has serious problems such as crashes, hangs or broken graphics/audio. Playable is the separate rating for games without major issues. If you want dependable full playthroughs, keep your working setup while testing another route.

Your game ID	System	Emulator version in the record	Status	Record
CUSA03173	Windows	0.16.0	Ingame	Windows entry
CUSA03173	Linux	0.15.0	Ingame	Linux entry
CUSA03173	macOS	0.19.0	Ingame	macOS entry
CUSA00900	Windows	0.15.0	Ingame	Windows entry
CUSA00900	Linux	0.17.0	Ingame	Linux entry
CUSA00900	macOS	0.19.0	Ingame	macOS entry

Swipe or use the arrow keys to see all columns.

These entries list Bloodborne version 1.09. Match your game ID, game version, operating system and emulator version to the record. For a newer build, read that entry's newer test comments before changing a working installation. These CUSA00900 emulator records do not change the CUSA03173 requirement for our three bbport setup routes: renaming a folder will not convert its executable.

What is BBLauncher?

rainmakerv3's BBLauncher is a shadPS4 launcher. It belongs to the emulator route. shadPS4's current official graphical launcher is QtLauncher; the emulator core itself has no GUI.

The native projects supply Supermedo's Bloodborne.exe, Mrsuss60's launcher.py and the Linux GTK4/AppImage launcher. Use the launcher for the project you chose. All three routes run without installing BBLauncher or the shadPS4 application.

Choose a route and protect your saves

Your situation	Choice or next step
Your situationWindows/Linux, matching native hardware and CUSA03173 v1.09, with direct Bloodborne installation as your goal	Choice or next stepFollow the native installation steps
Your situationApple M1 or newer with Rosetta 2 and macOS 26+	Choice or next stepTry shadPS4 with the matching Mac compatibility record above; keep a working PS4 setup if you want a reliable full playthrough
Your situationAn Intel Mac or a CPU outside the chosen route's requirements	Choice or next stepUse another compatible machine for these routes
Your situationYou already have a working shadPS4 installation	Choice or next stepKeep it and try the native port separately before replacing anything
Your situationCUSA00900 game data	Choice or next stepUse its matching emulator record for evaluation; our three bbport setup routes use CUSA03173
Your situationYou want to run other PS4 games too	Choice or next stepCompare those games' individual entries in the official compatibility list
Your situationA native port is installed but fails to run	Choice or next stepUse native troubleshooting
Your situationKeyboard input is your main concern	Choice or next stepRead the native controls guide

Before testing the native port, back up your existing emulator saves. On Linux, create a new folder and select it in the native launcher's Saves folder field. On Supermedo, choose a new test directory in Game & effects → Saves folder. On Mrsuss60, use a separate copy of your prepared game folder; its user/ stays with that program/game copy. Keep the original emulator data directory intact. Start a new test character, then compare the same area at the same output resolution on your computer.