Bloodborne for Windows 1.8.0-beta.6

A native Windows build of the Bloodborne PS4 port. The download contains no game files; see the README for features, requirements and install steps. This is a beta: copy your user folder before you try it.

New in 1.8.0-beta.6

• Install HelixSR now installs HelixSR 2.0.0 by lonewolf0622. By HelixSR's notes, upscaling takes about 15 to 18 percent less GPU time at DLAA and Ultra Quality. The 1.9.1 download the previous builds asked for is gone from HelixSR's releases, so those builds can no longer install it.
• HelixSR 2.0 keeps its DLL in a HelixSR-fsrfg folder. The launcher and the game find it there, and an existing 1.9.x copy is offered as Update HelixSR.
• The launcher downloads NVIDIA's DLSS 310.7.0 DLL itself (about 56 MB, checked by SHA-256), hands it to HelixSR's setup and deletes it after the build. The setup is no longer told to answer yes to everything: in HelixSR 2.0 that would also install HelixSR into every other game on your PC.
• The launcher no longer fails to start with invalid literal for int() after Browse… on the Play page (from 1.8.0-beta.5, which was never published). A settings file that already has the bad value is repaired.

What to test

1. Advanced > Performance: press Install HelixSR (or Update HelixSR). It should finish without an error, and no other game on your PC should change.
2. Play for a few minutes with HelixSR on and say which graphics card you have. Send user\last_run.log if anything goes wrong.

Known issues

• HelixSR 2.0.0 has not been run in this game yet, on any card.

Updating

The launcher offers this version when Beta versions is on (Advanced > Launcher). Saves and settings stay.

SHA-256 of bbport-windows.zip: 1fcc4d273e6a3d6c4b8fa9f2ce537837b51324274292e21a0ed4b1a34986b9e1

Bloodborne for Windows 1.8.0-beta.3

A native Windows build of the Bloodborne PS4 port. The download contains no game files; see the README for features, requirements and install steps. This is a beta: copy your user folder before you try it.

New in 1.8.0-beta.3

• Install HelixSR works again. HelixSR replaced its 1.9.0 download with a slightly different file, and the launcher still asked for the old one, so installs and reinstalls failed with an error. The launcher downloads the current file now.
• A HelixSR copy built from an older download is recognized: Update HelixSR replaces it instead of rebuilding what you already have.
• Install HelixSR no longer builds HelixSR's frame generation, which this port does not use. The setup skips it and no longer downloads its about 400 MB of NVIDIA files.

What to test

1. Advanced > Performance: press Install HelixSR (or Update HelixSR if you already have an older copy). It should finish without an error and HelixSR should still work in the game.
2. Say which graphics card you have. AMD cards are the ones nobody has tested HelixSR on in this game yet.

Known issues

• HelixSR has not been run in this game on an AMD card yet.

Updating

The launcher offers this version when Beta versions is on (Advanced > Launcher). Saves and settings stay.

SHA-256 of bbport-windows.zip: b9f5575e9e6463359c6789e6e8a866878c1c2630c7eba701cbae1e5de3491fca

Bloodborne for Windows 1.8.0-beta.2

A native Windows build of the Bloodborne PS4 port. The download contains no game files; see the README for features, requirements and install steps. This is a beta: copy your user folder before you try it.

New in 1.8.0-beta.2

• Install HelixSR now installs HelixSR 1.9.0 by lonewolf0622: sharper images, an experimental int8 network that HelixSR turns on by itself on AMD RDNA 2 and newer, and experimental Radeon Vega support. If you already use HelixSR, press Reinstall HelixSR in Advanced; the launcher then uses the newest HelixSR-* folder. HelixSR 1.9.0 is under the HelixSR Freeware License, which allows this download of the official, unmodified release.
• After the in-game menu or the name entry closed, every gamepad button stayed ignored until all of them were released, so a button pressed right after closing did nothing. Only the buttons still held from the menu are ignored now.

What to test

1. Advanced > Performance > Reinstall HelixSR, then play a few minutes with HelixSR selected. Say which graphics card you have; AMD cards (RDNA 2 and newer, Vega) are the ones nobody has tried yet.
2. Open the in-game menu with a gamepad, close it, and press a button at once: it should act.

Send user\last_run.log with any report.

Known issues

• HelixSR 1.9.0 has not been run in this game on an AMD card yet.

Updating

The launcher offers this version when Beta versions is on (Advanced > Launcher). Saves and settings stay. The helixsr folder stays too; Reinstall HelixSR adds 1.9.0 next to 1.8.1.

SHA-256 of bbport-windows.zip: a5aae0d63e7632d8d44e16b3afa936994d0028fb8645f025e2dcb177f8ec5235

Bloodborne for Windows 1.8.0-beta.1

Bloodborne for Windows, a native port of the PS4 game. The download contains no game files; see the README for features, requirements and install steps. This is a beta: copy your user folder somewhere safe before you try it.

New in 1.8.0-beta.1

• HelixSR (experimental). HelixSR by lonewolf0622 runs NVIDIA's DLSS network on cards that cannot run DLSS, mainly AMD. The port runs it through a Direct3D 12 bridge next to its Vulkan renderer. In the launcher, open Advanced and press Install HelixSR: it asks before NVIDIA's DLSS DLL is downloaded, then fetches and builds HelixSR (about a minute) and selects it. Nothing from HelixSR or NVIDIA is in this zip.
• Quit from the controller. Hold L3+R3 for 1.5 seconds for a small "Quit to desktop?" box. A short tap still opens the in-game menu. The menu also has a Quit to desktop button.
• The in-game menu no longer runs off the bottom of a 1080p screen.

What to test

1. AMD cards: Install HelixSR, choose it, play for 10 minutes. Does it run, and how does it look and perform next to FSR 3.1 or FSR 4?
2. Any card: does Install HelixSR finish? If it fails, send the message it shows.
3. Hold L3+R3 in game, then Cancel and Quit.

Send user\last_run.log, and for HelixSR also helixsr.log from the helixsr folder next to BLauncher.exe.

Known issues

• HelixSR was tested only on a GeForce RTX 4070 so far (1280x720 to 1920x1080, 120 to 160 FPS). It is untested on AMD cards, which are the ones it is made for.
• Turning frame generation on mid-game can crash the game, with any upscaler. Turn it on in the launcher before you start.
• Do not share the helixsr folder: the network it builds is NVIDIA's.

Updating

Turn on Beta versions in the launcher's Advanced tab, then check for updates. Your saves and settings stay.

SHA-256 of bbport-windows.zip: 452066fe431f3398c22ad8a313b1c41e21ac540aff7c20730a598c1ec9df6892

Bloodborne for Windows 1.7.1

Bloodborne on Windows 10 and 11, running as a native PC program instead of in an emulator. You need your own copy of the game: this download contains no game files. Features, requirements and install steps are in the README.

New in 1.7.1

• The frame generation switch is now called "Frame generation" in the launcher and the in-game menu. The old name, "Frame generation (FSR 3.1)", made it look like it changed your upscaler to FSR 3.1. It never did: it works on top of whichever upscaler you pick, FSR 4 and FSR 4.1.1 included.
• Fix: the game could close by itself when Windows was low on memory, for example with other heavy programs open. The background save of the shader cache failed and took the game with it. A failed save is now skipped and tried again later.
• The README is rewritten for players, with current screenshots of the launcher.
• Reporting a problem on GitHub now opens a short form that asks for your version, graphics card and driver, and user\last_run.log.

Updating

• From 1.6.17 or 1.7.0: use Check for updates (Advanced). The launcher keeps your saves and settings.
• From 1.6.16 or older: let the launcher update you to 1.6.17 first, or download this zip and unzip it over your folder.

SHA-256 of bbport-windows.zip: 4d8a4cfceff82c737fce2efaf7d08d9f8036038e892f7f356c11c4f9e7738a04

Bloodborne for Windows 1.7.0

Bloodborne on Windows 10 and 11, running as a native PC program instead of in an emulator. You need your own copy of the game: this download contains no game files. Features, requirements and install steps are in the README.

New in 1.7.0

• Mouse and keyboard play (#5). The mouse turns the camera while the game window has focus, and Insert or Alt+Tab lets go of it. The keys follow Dark Souls III: left click attacks, Shift + left click is the strong attack, right click transforms, Space dodges and sprints, Q locks on, E interacts, F drinks a blood vial, Esc opens the menu and Tab the gestures. The direct mouse camera is ported from Ryansousa10's fork.
• A Controls tab in the launcher (Advanced view): pick your controller, remap every input on the keyboard, the mouse and the gamepad, and set the mouse sensitivity.
• Button icons for how you play. The launcher redraws the game's PlayStation buttons as Xbox buttons, or as your keyboard keys and mouse buttons. Pick the set in Controls > Button icons; Automatic follows the controller connected when the game starts. The icons are made from your own copy of the game when you press Play, and a mod with its own icons keeps priority.
• FSR 4.1.1 (experimental) on NVIDIA and AMD cards. Turn on Experimental features (Advanced), use "Download FSR 4.1.1" in Graphics (about 14 MB) and pick it. The launcher downloads fsr4vk with a fix for AMD's Windows driver, built by this port (source below).
• A monitor picker when you have more than one monitor, and "Add to Steam" on the Play page.
• Controllers whose sticks do not rest at the center (clone pads) work.
• user\last_run.log starts with your GPU and driver, and gets a Perf: line every 30 seconds, so a report shows how the game ran.

Fixes

• A crash or kill while the game saves can no longer leave a half-written save.
• A shader compiled ahead of time on a busy CPU, or an old shader cache entry, could break Vulkan's rules. Both are caught now; the shader cache rebuilds once after you update.
• Less smearing with object motion vectors on: still objects such as bushes in the Hunter's Dream no longer get bogus motion.
• Sprinting on the keyboard no longer stops when you let go of A or D after adding it to a straight sprint. Keyboard diagonals now push the stick the way a real stick does; checked in the game with a replay.
• The in-game menu (Insert) can now save over an existing settings file on Windows.
• In windowed mode, an output above 1080p opens a window of that size, or a maximized one when it would not fit, instead of a 1920x1080 window.
• Numpad 0 with Num Lock off opens the in-game menu, like Insert.
• The game asks Windows not to throttle it while another window has the focus.
• "Close the launcher when the game starts" waits for the game window, so large mods finish preparing.
• The online/offline screen at the title is skipped.
• The launcher finds updates by the repository's id, so a rename of the GitHub account cannot redirect them.

Known issues

• Some players hear the sound doubled, like an echo, with FSR 4 and frame generation on. It has not been reproduced on a test PC yet.
• FSR 4.1.1 on AMD has run on one RX 6600 so far. At odd output sizes it can leave the last row or column of pixels unwritten.
• Near walls the camera can still smear for a moment. The game's own camera jumps there, and FSR and frame generation cannot hide that.
• The frame rate fix for unfocused windows (the game opts out of Windows' background throttling, which Windows confirms) is not confirmed yet on the PC that reported the problem.
• The button icons are chosen when the game starts. Switching between keyboard and controller mid-game keeps them until the next start.
• The direct mouse camera needs game version 1.09. Other versions turn the camera through the stick, which feels slower.
• Native speakers have not checked the new launcher texts in languages other than English and Russian.

Updating

• From 1.6.17 or a 1.7.0 beta: use Check for updates (Advanced). The launcher keeps your saves and settings.
• From 1.6.16 or older: let the launcher update you to 1.6.17 first, or download this zip and unzip it over your folder.
• The shader cache rebuilds once on the first start.

fsr4vk source

fsr4vk is GPL-3.0. The fixed build the launcher downloads and its complete source with the build scripts are attached to the 1.7.0-beta.2 release as fsr4vk-v0.4.3-amdfix.zip and fsr4vk-v0.4.3-amdfix-src.zip. I reported the fix upstream as dvj5411/fsr4vk#1.

SHA-256 of bbport-windows.zip: 16a46c6e69d1b036acba23fe03714057d0cdb550b5e7c3430ac531b50b0a810a

Bloodborne for Windows 1.7.0-beta.2

Bloodborne on Windows 10 and 11, running as a native PC program instead of in an emulator. You need your own copy of the game: this download contains no game files. Features, requirements and install steps are in the README.

This is a beta. It has had less testing than the stable 1.6.17. Copy your user folder (your saves) somewhere safe before you try it. If something breaks, go back to 1.6.17 and send me your user\last_run.log.

New in 1.7.0-beta.2

• FSR 4.1.1 works on AMD cards. On AMD's Windows driver, fsr4vk stopped before its first frame and the game fell back to FSR 3.1. The launcher now downloads an fsr4vk build with a fix for that driver, made for this port (source below). If you downloaded FSR 4.1.1 with beta.1, the Graphics page offers "Update FSR 4.1.1".
• Mouse and keyboard (#5). The keys follow the Dark Souls III layout by default: left click attacks, Space dodges, Q locks on. The mouse turns the camera while the game window has focus, and Insert or Alt+Tab lets go of it. You can bind mouse buttons and the wheel, and the "Dark Souls III layout" button in Controls puts the defaults back. The direct mouse camera is ported from Ryansousa10's fork.
• A Controls tab in the launcher (Advanced view) to pick your controller and remap every input on the keyboard and the gamepad.
• Less smearing with object motion vectors on. Some still objects, such as bushes in the Hunter's Dream, got object motion of up to 650 pixels a frame, and FSR and frame generation smeared them. When an object's vector is far off from the camera's, the game now uses the camera's.
• In windowed mode, an output above 1080p opens a window of that size, or a maximized one when it would not fit, instead of a 1920x1080 window.
• The FSR 4.1.1 entry no longer stays gray after you turn on Experimental features or download the files.
• Object motion vectors on AMD cards have their own switch, off by default. Experimental features alone no longer turns them on.
• user\last_run.log gets a Perf: line every 30 seconds with the frame rate, the slowest 1% and the worst frame, so a report shows how the game ran.
• Numpad 0 with Num Lock off opens the in-game menu, like Insert.
• The game asks Windows not to throttle it while another window has the focus.

What to test

1. With an AMD Radeon RX 6000, 7000 or 9000 card: turn on Experimental features (Advanced), download or update FSR 4.1.1 in Graphics and pick it. Tell me whether it looks right and send your last_run.log; its Perf: lines show your FPS.
2. Play with the mouse and keyboard on the new default keys.
3. Alt+Tab to another window for a minute while the game runs, and tell me if the frame rate holds.

Open an issue on this repository for any report, and attach user\last_run.log.

Known issues

• Near walls the camera can still smear for a moment. The game's own camera jumps there, up to 1.4 m in a single frame, and FSR and frame generation cannot hide that.
• Some players hear the sound doubled, like an echo, with FSR 4 and frame generation on. It has not been reproduced on a test PC yet, and it is not fixed.
• FSR 4.1.1 on AMD has run on one RX 6600 so far. At odd output sizes it can leave the last row or column of pixels unwritten.
• The frame rate fix for unfocused windows is not confirmed yet on the PC that reported the problem.
• The direct mouse camera needs game version 1.09. Other versions turn the camera through the stick, which feels slower.
• Native speakers have not checked the new launcher texts in languages other than English and Russian.

Updating

• From 1.7.0-beta.1: use Check for updates (Advanced). The launcher installs the beta and keeps your saves and settings.
• From 1.6.17: turn on "Beta versions" (Advanced, Launcher), then use Check for updates.
• From 1.6.16 or older: let the launcher update you to 1.6.17 first, or download this zip and unzip it over your folder.

This build starts with "Beta versions" on, so it offers the next beta and the next stable release.

fsr4vk source

fsr4vk is GPL-3.0. The fixed build the launcher downloads (fsr4vk-v0.4.3-amdfix.zip) and its complete source with the build scripts (fsr4vk-v0.4.3-amdfix-src.zip) are attached to this release. I reported the fix upstream as dvj5411/fsr4vk#1.

SHA-256 of bbport-windows.zip: 849d6e9c7972a2ce17fc6f8f5a5f71c9cb04fcff6f301b8e59e9d51c2015d097

Bloodborne for Windows 1.6.17

Bloodborne on Windows 10 and 11, running as a native PC program instead of in an emulator. You need your own copy of the game: this download contains no game files. Features, requirements and install steps are in the README.

New in 1.6.17

A "Beta versions" switch in the launcher (Advanced, Launcher), off by default. Turn it on and the launcher also offers beta releases. Betas get new features first and have had less testing than stable releases, so copy your user folder (your saves) somewhere safe before you install one.

The game is the same as in 1.6.16. Only the launcher changed.

Updating

The launcher offers this version and installs it for you. Your saves and settings stay.

SHA-256 of bbport-windows.zip: 9ca5091cbf8f03eb900716e662ac2024e98ecb75c3758dfda3f700b700682cac

Bloodborne for Windows 1.7.0-beta.1

Bloodborne on Windows 10 and 11, running as a native PC program instead of in an emulator. You need your own copy of the game: this download contains no game files. Features, requirements and install steps are in the README.

This is a beta. It has had less testing than the stable 1.6.17. Copy your user folder (your saves) somewhere safe before you try it. If something breaks, go back to 1.6.17 and send me your user\last_run.log.

New in 1.7.0-beta.1

• FSR 4.1.1 on Windows, as an experimental option. Turn on Experimental features (Advanced), download it once from the launcher (about 20 MB) and pick it as your upscaler. It runs AMD's FSR 4.1.1 model through dvj5411's fsr4vk (GPL-3.0), which the launcher downloads only when you ask for it. On an NVIDIA RTX 4070 it costs about 2.4 ms per frame at 1080p, against 2.0 ms for FSR 4 and 0.55 ms for FSR 3.1.
• If the game crashes or is closed while it saves, your save can no longer be left half-written. The game writes a temporary copy first and swaps it in (ported from deadinside28's upstream port).
• With no frame cap, menus stay at 240 FPS instead of running at over 1,000. Messengers and loading-screen pictures no longer replay their animations (new FPS patch lists from the ps4_cheats database, ported by yumlevi).
• The online/offline choice at the title is skipped: the game goes straight to its main menu.
• Clone controllers whose sticks do not rest at the center work: each pad gets its own resting point and dead zone. Connect the pad without touching the sticks.
• A monitor picker (Display & FPS) when you have more than one screen.
• "Add to Steam" on the Play page. Close Steam first; your Steam shortcuts file is backed up.
• "Close the launcher when the game starts" waits until the game window is up. It closed after 5 seconds before, which could stop large mods while they were being prepared.
• Mods no longer crash the game at start when Windows Developer Mode is on.
• The shader cache could pair an old entry with a newer shader. The game now drops only the bad entry. Your shader cache rebuilds once after this update, so the first session stutters while shaders compile.
• An "Experimental features" switch in Advanced, off by default. It unlocks FSR 4.1.1 and, on AMD cards, object motion vectors.

What to test

1. If you have an AMD Radeon RX 6000, 7000 or 9000 card, or an Intel Arc card, try FSR 4.1.1: turn on Experimental features, download it and pick it. Tell me your FPS next to FSR 4, and whether the image looks right.
2. Play as usual, save and quit a few times, and tell me if a save ever fails to load.
3. If you use mods, turn on "Close the launcher when the game starts" and check that the game still starts.
4. If you have two monitors, pick the second one in Display & FPS.

Open an issue on this repository for any report, and attach user\last_run.log.

Known issues

• FSR 4.1.1 has only run on an NVIDIA RTX 4070 so far. At odd output sizes it can leave the last row or column of pixels unwritten. If it cannot start, the game uses FSR 3.1 and writes the reason in last_run.log.
• On some AMD cards the game finds damaged entries in its shader cache when it starts. This beta drops only the bad entries instead of the whole cache; tell me if each session still starts with stutter.
• Two identical monitors show up as one entry in the monitor picker.
• "Add to Steam" has been tested on copies of Steam's shortcuts file, not on a real Steam library yet. Tell me if the shortcut does not appear.
• The new launcher texts in languages other than English and Russian have not been checked by native speakers.

Updating

• From 1.6.17: turn on "Beta versions" (Advanced, Launcher), then use Check for updates (Advanced). The launcher installs the beta and keeps your saves and settings.
• From 1.6.16 or older: let the launcher update you to 1.6.17 first, or download this zip and unzip it over your folder. Your saves (user) and settings stay.

This build starts with "Beta versions" on, so it offers the next beta and the next stable release. Turn the switch off to get stable releases only.

SHA-256 of bbport-windows.zip: 4541c3e81e570d1d03132a14d1097ddbb37a7343b47ce2da31186d792fca871f

Bloodborne for Windows 1.6.16

Bloodborne on Windows 10 and 11, running as a native PC program instead of in an emulator. You need your own copy of the game: this download contains no game files.

New in 1.6.16

Less stutter after loading an area, mostly on AMD cards. After certain area loads, the part of the game that prepares shaders ahead of time stopped working, so every new shader was compiled while you played.

What this build includes

• Four upscalers: FSR 3.1, FSR 4, DLSS on NVIDIA RTX cards, and XeSS. The launcher only offers the ones your graphics card can run, and tells you why the others are unavailable. FSR 4 needs a one-time download from the launcher's Graphics tab.
• FSR 3.1 frame generation, off by default. When it's on and the frame cap is on Auto, the game runs at half your screen's refresh rate (at most 120 FPS) and frame generation adds a frame in between.
• ReShade with two looks, Natural and Vivid. Press Home in the game to adjust them.
• Shaders are compiled ahead of time and the driver's shader cache is kept between sessions, which cuts stutter in new areas.
• For The Old Hunters, the launcher reads the license from your DLC package and the game treats the expansion as owned.
• The launcher can install the game from your PS4 packages (base game, 1.09 update and DLC), or from a folder that holds them.

Fixes included

• The crash when you take a hit on Intel 12th gen and newer CPUs.
• The crash on AMD cards when an upscaler is on, and several crashes while loading areas.
• The black character preview, loading-screen pictures that disappeared, and switches in the in-game menu that did not change when clicked.

Known issues

• FSR 4.1.1 is not available on Windows in this port. AMD's own 4.1.1 is a DirectX 12 feature, and the port's Vulkan version of it needs an extension that no Windows driver is known to support yet.
• On AMD cards, object motion vectors stay off. They cost FPS and made frame generation draw some objects wrong.
• On some AMD cards the game finds damaged entries in its shader cache when it starts and rebuilds it, so each session begins with stutter while shaders compile. I'm looking into it.
• In frames added by frame generation, small bright flames and the edges of leaves can look cut.
• The first session after an update, or after clearing the shader cache, stutters while shaders compile.

Requirements

• Windows 10 (version 1903 or later) or Windows 11, 64-bit.
• A graphics card with Vulkan 1.3 and a current driver. DLSS needs an NVIDIA GeForce RTX 20 series card or newer.
• About 6 GB of free memory (RAM plus page file), or 10 GB for 1440p and 4K output.
• Your own dump of Bloodborne at game version 1.09, or its PS4 .pkg files. Other versions run at 30 FPS.

Install

1. Unzip bbport-windows.zip anywhere.
2. Open Bloodborne.exe. The first time, the launcher opens: choose your game folder (the one with eboot.bin), or use Install from PKG if you have the PS4 .pkg files.
3. Press PLAY. From then on, Bloodborne.exe starts the game directly, and BLauncher.exe opens the settings.

Updating

The launcher checks this page for new versions and installs them for you. Your saves and settings stay.

Reporting a problem

Open an issue on this repository and attach user\last_run.log. The game writes it every time you play.

Credits

Built on deadinside28's Bloodborne port (release 0.4) and Supermedo's Windows build, with fixes from yumlevi, bmy, Mrsuss60 and GoncaloLobo0. The bundled Intel XeSS, NVIDIA DLSS, ReShade and PkgTool keep their own licenses, which are in the zip's licenses folder.

SHA-256 of bbport-windows.zip: 12ebb3593641625398b8b2fdd5ec1857f5af3d90b7d291c49a65c98ab06be538