github Mrsuss60/bloodborne_pc_windows_port v0.6.5
bloodborne_pc_windows_port v0.6.5

3 hours ago

Bloodborne PC Windows Port v0.6.5

This update brings a completely redesigned launcher with a built-in diagnostics dashboard and setup checker, allows binding the Shift key on its own for sprinting or dodging, and delivers major stability fixes that resolve startup and in-game crashes on older CPUs and memory-constrained systems.

Changelog

  • Complete Launcher Overhaul & Diagnostics Dashboard

    • New Tabbed Interface: The launcher is now organized into dedicated tabs for Home, Display & Visuals, Mouse & Controls, Patches & Effects, and Advanced Settings. Tabs load on demand, making the launcher open faster.
    • Setup Audit: The home screen now checks your setup before launching and clearly tells you if your game path, Vulkan graphics driver, or CPU instructions are ready.
    • One-Click Diagnostics: Added a "Copy Diagnostics" button that collects your system specs, GPU driver, and configuration to make bug reporting quick and simple.
    • Live Log Viewer: Watch the game log in real time with filters for errors, warnings, Vulkan events, or fast-path imports.
    • Deeper Visual & Engine Controls: Added direct toggles for FSR 4.1.1, upscaler quality presets, Model LOD bias, and individual post-processing passes (SSAO, dynamic shadows, reflections, and motion blur). All choices automatically sync with your bbport.ini.
  • Standalone Shift Key Binding (PR #154)

    • Fixed an issue where the launcher prevented you from binding the Shift key by itself.
    • You can now bind Left Shift or Right Shift directly to actions like sprinting, rolling, or dodging.
    • Combinations like Shift + Left Click still work properly when holding Shift down.
    • Credits: @HatsyRei / PR #154.
  • Startup & Memory Crash Fixes

    • Fixed an issue where running low on virtual memory caused silent allocation failures and instant crashes during startup.
    • The memory system now logs the exact operation, size, and reason whenever an allocation fails so problems can be diagnosed immediately.
    • Addresses #148, #151, #155.
  • Older CPU Instruction Fixes (Non-BMI1)

    • Fixed a bug where older processors without BMI1 support misidentified instruction lengths during startup, causing the game to execute data as code and crash.
    • Scanned every instruction with a disassembler to ensure all 406 bit-counting sites patch cleanly with their true length, including rare multi-prefix variants.
    • Addresses #148, #151, #155.
  • Assertion Crash Fixes & Clearer Exit Codes

    • Non-fatal game assertions now log diagnostic details and let the game continue running (matching retail PS4 behavior), instead of crashing out with a generic code.
    • Replaced confusing exit codes with distinct failure numbers:
      • 140: Missing memory or null pointer dereference.
      • 141: Engine panic abort trap.
      • 142: Manual assertion stop (when debugging with BB_GAME_ASSERT_STOP=1).
    • Ref #149.
  • Improved Crash Dumps

    • Crash logs now display the exact machine code instructions where the game stopped, provide a genuine stack unwind, and report active memory usage to make community troubleshooting much faster.

Requirements

  • OS: Windows 10 or Windows 11 (64-bit)
  • GPU: Vulkan 1.3 capable graphics card (NVIDIA GTX 10-series+, AMD RX 400-series+, Intel Arc)
  • CPU: 64-bit x86 processor supporting AVX 1.0 or SSE4.2 (older CPUs without BMI1 are supported)
  • Game Dump: Decrypted Bloodborne PS4 dump (CUSA03173, version 1.09) with eboot.bin and sce_module/libc.prx

Installation

  1. Extract the release archive to a folder.
  2. Run BloodborneLauncher.exe (or run.bat).
  3. Confirm your decrypted 1.09 eboot.bin path on the Home dashboard.
  4. Pick your GPU Adapter, game language, graphics settings, and controls.
  5. Click Launch Bloodborne.

In-Game Hotkeys

  • F1: Lock or unlock the mouse cursor.
  • Insert or L3 + R3: Open the in-game settings menu.
  • F11: Show or hide the FPS and performance display.

Troubleshooting

  • If the game freezes on startup or crashes when moving between areas, set prep_workers=1 or prep_workers=2 in the launcher or bbport.ini. Higher values use more CPU threads at once, which can overwhelm 4-core and 6-core processors.
  • If the game crashes during intense combat, cap your frame rate to 60 FPS in the launcher. Higher frame rates work well on high-end hardware, but they increase physics and particle load.
  • Avoid enabling conflicting frame rate mods at the same time. If you run into issues, try launching with only "Skip Intro" enabled first.
  • If you notice visual glitches or crashes after an update, delete the cache folder in user/cache/CUSA03173/ so the game can rebuild shaders cleanly.

Note

  • When reporting a crash, please click "Copy Diagnostics" on the launcher's Home tab and attach the latest bblauncher.log and crash log from the out folder.

Discord Server

Join the Discord for updates, bug reports, and discussions about the Bloodborne PC Windows Port:
https://discord.gg/JdZsJ2ArZ2

Don't miss a new bloodborne_pc_windows_port release

NewReleases is sending notifications on new releases.