I originally got BLUE REFLECTION working on Ubuntu 20.10 with Proton 5.0. Installing Media Foundation was the part that took me ages. The guides I found were not much help for a noob like me, so I wrote down the folders, variables and commands I used.
That setup used a dxvk.conf file in the main game folder, a Media Foundation workaround and a check of the installed GStreamer packages. Several parts have changed since then.
Updated: 25 October 2026. This guide covers the original 2017 Steam release of BLUE REFLECTION, AppID 658260, through the Linux Steam client and Proton. A Windows Steam installation inside Wine or Lutris has its own prefix and runner.
What changed since the original setup
| Old instruction | Current status |
|---|---|
| Ubuntu 20.10 | Reached end of life on 22 July 2021. Use a supported distribution and current graphics drivers for a new setup. |
| Start with Proton 5.0 | Keep this for the historical setup. Start a current test with Steam’s current stable Proton; Valve’s latest full stable GitHub release is 11.0-2 as checked on 25 October 2026. |
d3d9.deferSurfaceCreation = True | Still listed in the DXVK configuration reference. Test it when investigating presentation or black-window behaviour. |
d3d11.constantBufferRangeCheck = True | An old rendering workaround. DXVK removed the option on 12 July 2022. |
Download z0z0z/mf-install | The original repository currently returns 404. A surviving archive explicitly says it is unmaintained. |
Valve’s current Steam Deck/SteamOS compatibility report lists BLUE REFLECTION as Unsupported, checked on 25 October 2026. Test the opening videos and normal gameplay on the setup you intend to use.
Start with current Proton
- Install BLUE REFLECTION in the Linux Steam client. Keep a copy of any existing launch options before changing them.
- Open Properties → Compatibility and select the current stable Proton provided by Steam. Begin with its normal configuration, without the old Media Foundation installer or extra DLL overrides.
- Launch once and allow Steam to finish its first-run setup. Close the game after reaching the menu, if it gets that far. This also lets Proton create the game’s prefix.
- Start a new game and watch the opening. Check the picture, sound and subtitles, then reach a normal 3D scene and check movement, controls and rendering.
- If it fails, repeat the same test with Proton Experimental. Record which version you selected and where the failure happens.
Reaching the title screen only checks part of the game. The old reports show failures after selecting New Game, so include that transition when testing.

Check video playback separately from rendering
The Proton compatibility thread records startup failures, subtitles over a black video, and a later white screen. In April 2020, a separate DXVK report covered stretching and flickering shadows on an Nvidia setup. These are different symptoms with different parts of the software involved.

Media Foundation provides Windows media interfaces. GStreamer is part of the Linux media stack used by Wine/Proton. A DXVK graphics option can change presentation behaviour while a missing or broken video path still prevents a cutscene from playing.
If current Valve Proton still fails specifically at a video, a current official GE-Proton build is another test. Its maintainer lists additional Media Foundation patches for video playback. The installation instructions link to ProtonPlus as a graphical way to manage releases:
- Select the Steam installation you actually use in the version manager and install a current GE-Proton release.
- Fully exit and restart Steam so it discovers the installed compatibility tool.
- Choose that GE-Proton version under BLUE REFLECTION’s Properties → Compatibility.
- Repeat the opening-video and gameplay checks. Keep the exact GE-Proton version with any results you record.
Try the remaining DXVK setting when needed
d3d9.deferSurfaceCreation delays creation of the graphics surface until presentation. It remains a documented DXVK option. To test it explicitly, create a dedicated configuration file:
mkdir -p "$HOME/.config/blue-reflection-proton"
printf '%s\n' 'd3d9.deferSurfaceCreation = True' > "$HOME/.config/blue-reflection-proton/dxvk.conf"
Put this in Steam’s Properties → General → Launch Options:
DXVK_CONFIG_FILE="$HOME/.config/blue-reflection-proton/dxvk.conf" %command%
DXVK supports an explicit configuration-file path, which makes the chosen file clear even when the game’s working directory differs from its installation folder. If you already use other launch variables, keep them on the same line with a single %command%. Remove the DXVK_CONFIG_FILE assignment to stop using this test configuration.
Leave d3d11.constantBufferRangeCheck out of a current configuration. It was confirmed as a fix for the 2020 shadow problem, but the later removal commit deleted both the option and BLUE REFLECTION’s built-in profile entry for it.
Find the actual game prefix
A Proton prefix contains Windows-style directories and registry data. The usual pattern is steamapps/compatdata/658260/pfx, but its location depends on the Steam library and any custom compatibility-data path. It is separate from the game’s executable folder.
If you have Protontricks installed, this command prints the prefix it selects for BLUE REFLECTION:
protontricks -c 'printf "%s\n" "$WINEPREFIX"' 658260
For a Flatpak installation of Protontricks, use its application command instead:
flatpak run com.github.Matoking.protontricks -c 'printf "%s\n" "$WINEPREFIX"' 658260
Choose the command for the version you installed, and launch the game once first. For an external Steam library, the Flatpak helper also needs access to that location; its installation documentation covers that setup.
If the game’s launch options set STEAM_COMPAT_DATA_PATH, that value identifies its compatibility-data directory, with the prefix in its pfx subdirectory. Keep the same path override when using Protontricks; its documentation describes that environment variable.
Test a clean prefix if an old workaround is still installed
The archived MF script copies DLLs into the prefix and writes registry overrides. Those changes belong to that prefix even when you select another Proton version. A clean-prefix test can help when moving away from an old modified setup.
- Back up your save files. Locate the game’s
pfxpath and its parent compatibility-data directory, normally named658260. Account for any custom path override. - Close the game and fully exit Steam.
- Give that compatibility-data directory a unique backup name, such as
658260.before-clean-testfor the normal layout, keeping its contents. Keep any existing backup rather than replacing it. - Restart Steam, select the Proton version you want to test and launch the game. Steam/Proton will create a new compatibility environment.
- Test the opening before adding overrides. Saves stored inside the previous prefix remain in the backup and may need to be restored separately.
Archive: the Ubuntu 20.10 and Proton 5.0 method
The original procedure was to launch once with Proton 5.0, close the game, and place a dxvk.conf file beside the game executable containing:
d3d9.deferSurfaceCreation = True
d3d11.constantBufferRangeCheck = True
The next part used the old mf-install script, followed by a check of the host’s GStreamer packages. For an existing copy of that script extracted to ~/Downloads/mf-install and an existing Proton 5.0 installation in the old default native-Steam location, its environment and invocation look like this:
cd "$HOME/Downloads/mf-install"
export WINEARCH=win64
export WINEPREFIX="$HOME/.steam/steam/steamapps/compatdata/658260/pfx"
export PROTON="$HOME/.steam/steam/steamapps/common/Proton 5.0"
bash ./mf-install.sh -proton
WINEPREFIX points to the game’s existing 64-bit prefix. PROTON points to the compatibility tool, and the archived script’s -proton argument selects its Wine binaries. Use $HOME inside quoted paths; a quoted ~ remains literal. Setting WINEARCH does not convert an existing prefix to another architecture.
This is a historical example for that older layout. The surviving archive’s README says it is unmaintained and retains a May 2020 notice explaining that Wine’s Media Foundation work had already made the script unnecessary for many games. Its script also expects the older runner layout and both wine and wine64 commands.
What to do with the GStreamer instructions
The official GStreamer Linux installation page linked in the original guide covers packages installed on the host distribution. The required plugins and their architecture depend on the environment running the program.
Current Proton configures its own GStreamer plugin search paths and registry directory, and GE-Proton documents its container runtime. Checking every GStreamer package in Synaptic therefore does not establish that the media stack inside the selected Proton environment is working. Test that runner’s video playback and collect its log before changing host packages.
Collect a log for a remaining failure
Valve documents PROTON_LOG in its runtime options. Put this in Steam’s Launch Options, reproduce the failure once, then close the game:
PROTON_LOG=1 %command%
The default filename is steam-658260.log in the home directory used by Steam. If you also want to keep the DXVK configuration test enabled, combine the variables on one line:
PROTON_LOG=1 DXVK_CONFIG_FILE="$HOME/.config/blue-reflection-proton/dxvk.conf" %command%
Keep the exact Proton version, GPU and driver, the point where the game fails, and any configuration or DLL overrides with the log. Remove PROTON_LOG=1 after collecting it. If a problem only occurs with GE-Proton, use its issue tracker; reproduce a Valve-Proton report with Valve’s build.
My BLUE REFLECTION gameplay
I recorded BLUE REFLECTION on Linux about a year after getting the original setup working. The Part I livestream below is from 26 January 2022.
Open my BLUE REFLECTION playlist on YouTube · Open Part I on YouTube.
Sources and references
- BLUE REFLECTION on Steam and Valve’s Steam Deck/SteamOS compatibility response.
- Proton 11.0-2 release notes, the BLUE REFLECTION compatibility thread and Proton runtime options.
- DXVK configuration reference, the 2020 shadow issue and the July 2022 option-removal commit.
- Official GE-Proton documentation and Protontricks documentation.
- Archival copy of mf-install, GStreamer installation documentation and the Ubuntu 20.10 end-of-life announcement.
