COMMUNITY PC GUIDE

Troubleshoot the Bloodborne Native PC Port

Start by identifying your port and release, then match your symptom to the checks below. The checks cover Linux bbport 0.4, Supermedo Windows v1.5 and Mrsuss60 Windows v0.2. Use PC port projects if you need to identify your program, then update within that project before retesting an older fixed issue.

Match the symptom to your build

Symptom	Build to check	First action
SymptomStartup rejects the game files	Build to checkAll three bbport routes	First actionCheck your complete CUSA03173 v1.09 directory
SymptomWindows Play button produces no game window with Resolution scaling enabled	Build to checkMrsuss60 Windows	First actionTurn Resolution scaling off and repeat the launch
SymptomWindows shows code 255 / “was unexpected at this time” in a path containing spaces	Build to checkMrsuss60 Windows	First actionMove the complete program/game folder to a path without spaces, then select it again
SymptomWindows remains on a grey window	Build to checkMrsuss60 Windows	First actionSave the failure stage, error and available logs for the Windows project
SymptomIllegal-instruction error or exit code 132	Build to checkLinux, especially an older CPU	First actionRead the CPU requirement message in 0.4
SymptomStartup fails after a cache-writing crash or power loss	Build to checkOlder Linux build	First actionUpdate to 0.4 for the damaged-cache fix
SymptomCrash after character creation's Finalize button	Build to checkOlder Mrsuss60 build	First actionUpdate to v0.2
SymptomBlack window with FSR 4 on NVIDIA	Build to checkLinux	First actionSelect FSR 3 and try the same launch
SymptomDark rectangles, stripes or a reversed scene in sky/fog blur	Build to checkOlder Linux build with DoF	First actionUpdate to 0.4
SymptomCrash after enabling an experimental mode or adding a patch	Build to checkThe build you changed	First actionReturn that change to its previous state and repeat the same scene
SymptomSupermedo shows a black window	Build to checkSupermedo	First actionExit the game, then use Advanced → Clear shader cache
SymptomSupermedo crashes after the opening cutscene	Build to checkOlder Supermedo build	First actionUpdate to v1.5, which includes the v1.3 fix
SymptomSupermedo movement slows above 120 FPS	Build to checkSupermedo	First actionSet the frame-rate cap to 120 or below
SymptomRandom crash or freeze remains	Build to checkAll three bbport routes	First actionSave the error and logs, then use the report checklist

Before changing files, copy your current saves folder to a backup outside the port's data directory. For both Linux routes, check the launcher's selected Saves folder: the AppImage defaults to ~/.local/share/bbport/user, while a source build defaults to the repository's user/. Mrsuss60 uses user/ in the program/game directory. On Supermedo, open Game & effects → Saves folder → Open and back up that selected directory; its default is user/ beside Bloodborne.exe. Keep these folders intact because they contain saves as well as shader cache.

Startup and loading failures

Check the installation prerequisites first: operating system, CPU instructions, Vulkan 1.3, drivers and game files. Mrsuss60 Windows also needs Python 3.10+ for its launcher and patch compiler. Supermedo's packaged program includes its software components.

On Linux, the base game's 1.00 executable crashes at startup. Select the prepared CUSA03173 v1.09 folder and read the launcher's executable check. If it identifies an old version or missing files, finish the game-file check before trying graphics changes. Leave executable validation enabled.

For exit code 132 / an illegal-instruction fault, use Linux 0.4's CPU message. It identifies missing AVX, BMI1, MOVBE, LZCNT, POPCNT or SSE4.2 instructions. Updating improves the diagnosis; a CPU still missing the required instructions needs a different compatible machine.

If an older Linux installation stopped launching after a crash while writing its shader cache, update to 0.4. That release repairs the damaged-cache startup failure and changes how the cache is written. It also fixes the startup hang associated with BB_READBACKS=2.

Mrsuss60 Windows startup checks

If clicking Play / Launch Bloodborne produces no game window and Resolution scaling is enabled, turn Resolution scaling off and try once more. Record whether the game window now opens before changing another option.

For code 255 with “was unexpected at this time”, check whether the full program/game path contains spaces. After backing up your saves, close the launcher and move the complete folder to a path without spaces, such as C:\Games\CUSA03173. Reopen the launcher, select the new game path and try again. Keep the folder contents together when moving it.

For a persistent grey window, or a startup failure that remains after the applicable checks, save any out/crash_*.log created in the program directory. If there is no crash log, copy the displayed launcher error or take a screenshot of the launcher and game window. Record whether failure occurs just after clicking Play, before a game window appears, or at the grey-window stage. Send those details using the project-specific bug-report checklist.

Supermedo Windows startup checks

For a black window, exit the game and open Advanced → Clear shader cache. Launch again with the same settings. The first run rebuilds the cache and can briefly stutter; keep your saves folder intact.

If an old release has no sound or turns black after its first launch, update to v1.5, which includes the v1.1 fixes, then repeat the same launch. From v1.2 or later, use Update, or Advanced → Check for updates. From v1.0/v1.1, back up your saves, get the Supermedo program release and extract the new zip over the same program folder, keeping user/.

If an AMD GPU crashes while loading the world, collect the error and logs for Supermedo's support channel. Include the GPU model, driver, chosen upscaler and the area being loaded. Use the report steps below.

AppImage cannot mount

For the specific Cannot mount AppImage error when launching through Steam without FUSE, set the Non-Steam Game's launch options to:

TMPDIR=$HOME/.cache APPIMAGE_EXTRACT_AND_RUN=1 NO_CLEANUP=1 %command%

The AppImage unpacks itself into ~/.cache/appimage_extracted_* and reuses that copy. Allow about 2 GB for it. Add --play after %command% if you want to skip the launcher window once setup is complete.

Crashes during play

Mrsuss60 character creation: v0.2 fixes the Finalize crash and associated save-data and name-handling problems. Install v0.2 before repeating character creation. It also adds a video-buffer allocation fallback for memory pressure during cutscene transitions.

Supermedo opening cutscene: update to v1.5, which includes the v1.3 fix for a crash when the opening cutscene finishes. If it still fails, record whether it crashes during the video or as gameplay begins.

Supermedo character creation: a blank character preview is a known issue; you can still create the character and see it in the game. For name entry, use the centered dialog, press Enter to accept or Esc to cancel, then release and press your gameplay buttons again.

Linux after enabling the new memory model: open Mode → New memory and translation model, turn it off, restart, and try the same location. Keep the default mode while diagnosing the crash. The experimental mode is available for AMD GPUs; use the default mode on NVIDIA.

If a crash still happens with the same build and settings, capture its exact point: loading an area, taking a hit, returning to the Hunter's Dream, or a cutscene transition. Repeat with recently added changes disabled, then report the remaining failure with its log. Include the error code and the action immediately before it.

Stutter, resource use and visual problems

Situation	Check	What to do next
SituationSupermedo movement slows above roughly 120 FPS	CheckCheck the frame-rate cap	What to do nextSet it to 120 or below, then repeat the same movement
SituationLinux video memory (VRAM) keeps rising across area changes on an old build	CheckUse 0.4, which includes the 0.3 texture-cache recycling changes	What to do nextEnable Frame statistics in the log or `BB_FRAME_STATS=1`; include its `Memory:` lines if growth continues
SituationOlder Linux build repeatedly compiles shaders after a driver/profile change	CheckUpdate to 0.4, which includes the 0.2 cache-rebuild change	What to do nextRepeat the same route and save the log if the stutter remains
SituationLinux camera movement produces smeared or ghosted scenery	CheckUpdate to 0.4's motion-vector fixes	What to do nextRecord the area, upscaler and preset if it persists
SituationLinux DoF blur shows dark blocks, stripes or an inverted scene	CheckUpdate to 0.4	What to do nextRepeat the same view and include a screenshot if it persists
SituationLinux on NVIDIA shows a black window with FSR 4	CheckSelect FSR 3	What to do nextRepeat the launch; collect Vulkan driver information if it stays black
SituationSteam Deck slows after a resolution/preset change	CheckUse FSR 3, 1280×720, and leave live resolution changes off	What to do nextUse Apply and restart the game after changing output or preset
SituationAn Intel CPU produces excessively dark tone mapping on an old Linux build	CheckUpdate to 0.4, which includes the 0.3 Intel CPU fix	What to do nextInclude the CPU model and affected area if the image remains dark

Treat CPU/GPU percentages as observations to attach to the problem. Record the scene, resolution, frame-rate mode and memory information alongside them. Change one setting at a time so the result tells you which change mattered.

For Linux AppImage driver information, run this from the directory containing the program:

./Bloodborne-bbport-x86_64.AppImage --vulkan-info 2>&1 | tee bbport-vulkan.log

Attach bbport-vulkan.log when reporting a driver or Vulkan startup problem.

Problems after a patch or modification

On Linux, disable the recently added loose-file mods and third-party patches in the launcher, restart, and repeat the same scene. If the symptom disappears, restore one item at a time and retest. Later mods override conflicting files, so record their load order too.

On Linux, if you enabled Free Camera and Enemy Control together, disable one: those options conflict. If startup names missing or empty debug fonts, disable the debug-menu patch before trying the regular game again.

On Mrsuss60 v0.2, click All XML Patches... in the main launcher window. In the XML Patch Manager, turn off one newly enabled patch and click Save & Apply. Restart the game and repeat the same scene. Record whether the symptom changes before testing another patch; include that result in your report.

Send a useful bug report

For Linux bbport, use the project's bbport Discord. For Mrsuss60's Windows port, use its GitHub Issues. For Supermedo, use its Windows port Discord.

On Mrsuss60 v0.2, collect out/crash_*.log from the program directory when it exists. If startup produced no crash log, attach the displayed error or a screenshot and state the failure stage described above. On Linux, copy the complete launcher Log output and any crash/watchdog report it prints. Include the Vulkan diagnostic file for driver problems.

For Supermedo v1.5, collect the output from the launch that actually failed:

If you clicked PLAY in the launcher, use Log → Copy for that session.
If you used Play Bloodborne.exe or --play, open Game & effects → Saves folder → Open and look for that run's last_run.log. The default is user/last_run.log beside Bloodborne.exe; a custom saves folder changes the location. Check the file's modification time against the failed run before attaching it.
If the file is missing or belongs to an earlier run, attach the current error or a screenshot and describe the failure stage. If you repeat the fault through the launcher, copy its new Log output.

Use this checklist:

Project and release tag, or the commit if you built from source.
Operating system, CPU, GPU and driver version.
Your actual game ID and version; for example, CUSA03173 / 1.09.
The action and location that trigger the failure, plus steps to repeat it.
Exact error text and relevant logs.
Active mods, patches, upscaler and experimental-mode setting.
What you changed for a single-item test and whether the symptom remained.

Share diagnostic text and screenshots of the fault. Keep game files out of the report.

For keys that stop responding while a menu is open, use the input checks. For a clean first setup, return to Bloodborne PC installation.