The Linux field guide
Bloodborne Port Linux Setup Guide
Choose your Bloodborne port Linux route before installing anything. The original bbport documents a Linux runtime and AppImage workflow; bbhost is a separate option with different configuration and executable checks.
Read the guideBefore you begin
For the original bbport, check x86-64 Linux, Vulkan 1.3 and compatible updated game data. Use the selected release’s AppImage instructions or its source-build instructions. Keep Windows launchers and commands out of this native Linux workflow.
Chapter I
Bloodborne port Linux requirements
A Bloodborne port Linux setup depends on the runtime, graphics driver and game files together. Vulkan support is a baseline, while an optional upscaler can need additional GPU features. Start with conservative documented settings rather than selecting every enhancement.
| Item | What to check |
|---|---|
| System | Original bbport documents x86-64 Linux |
| Graphics | Vulkan 1.3 and a suitable current driver |
| Game | Your own compatible files with the required 1.09 executable |
| Program | An AppImage release or a completed source build |
| Storage | Writable runtime data location; independent save backup |
Chapter II
Use a Bloodborne port Linux release
For an AppImage, download the asset from the original project’s release page and read the notes for that file. Apply executable permission if required by your distribution, then open the launcher and select the requested game folder.
Your Bloodborne port Linux package is separate from your game dump. Select the directory that actually contains the expected executable and data, not an outer folder containing the archive. If the AppImage cannot open, launching that same trusted file from a terminal can expose a useful error message.
A Bloodborne port Linux startup error may involve the package environment before the game is reached. Follow your distribution’s guidance for any named dependency; do not replace system libraries or copy unrelated Windows DLLs into the installation.
Chapter III
Build the original bbport from source
Choose this Bloodborne port Linux workflow only if you intend to compile the program. The README lists the required compiler, build tools and libraries. Cloning without submodules or skipping the build does not produce a runnable installation.
The example CUSA03173 path is a placeholder, not a directory to create empty or a reason to rename your edition. Use the real location of your compatible game data. Do not apply these commands to bbhost, which has its own build and setup documentation.
git clone --recursive https://github.com/deadinside28/bloodborne_pc.git bbport
cd bbport
bash build.sh
BB_GAME_DIR=/path/to/CUSA03173 bash run.shChapter IV
Validate your Bloodborne port Linux session
For the first Bloodborne port Linux launch, disable optional mods and use the runtime’s defaults. Check controller or keyboard input, sound, saving and reloading. Keep this initial test short and repeatable before exploring graphics options.
- Confirm the selected game directory and normal file-validation result.
- Check that the intended GPU and driver are being used.
- Test a short session without extra patches or overlays.
- Exit normally and confirm your save loads again.
- Record the build and settings before changing one option.
Chapter V
Bloodborne port Linux troubleshooting
If your Bloodborne port Linux setup reports a wrong game version, resolve the game files before tuning rendering. A missing executable, an incompatible revision and a graphics initialization failure are different problems.
For a later crash, preserve the log, project revision, distribution, GPU and driver version. Compare a clean baseline with the modified setup. A Linux bug report is more useful when it identifies the exact runtime and failing stage.
Questions, answered
Frequently asked questions
Does a Bloodborne port Linux guide also cover Steam Deck?
The original project provides Steam Deck-related documentation, but handheld support and performance depend on the build and settings. Follow its current device guidance; this page does not promise a frame rate.
Should I use Proton for Bloodborne port Linux setup?
The workflows here use native Linux programs. A Windows build through a compatibility layer is a different route with different troubleshooting. Do not mix the two when diagnosing a failure.
Where does the original Bloodborne port Linux runtime save data?
For the documented source-build workflow, saves and shader cache default to user/. The AppImage section instead documents ~/.local/share/bbport as its data directory. Launcher settings can change the location; verify yours before backing up or updating.
Follow the evidence
Sources & verification
These primary sources support the project-specific details above. Maintainer documentation can change; check your release before applying instructions.
How this site checks its sources