Blur

Game uses its own online account system [1] and doesn’t include VOIP, text chat or any other way to communicate with online players.

Updates cause various audio issues (such as crackling and cutting-off earlier than expected) especially on higher quality audio presets and frame rates over 60. Downgrade to the original version to avoid frame rate and audio issues. [2]

Despite the uncapped frame rate, gameplay sections are internally limited to 60 FPS with higher values duplicating the same frames while also breaking some post-processing effects (e.g. motion blur, lens flare, etc.). To change the internal limit and restore some of the broken effects see High frame rate. [3]

Official Master server for multiplayer was shut down. Can be restored with a mod, see Multiplayer types

General information

Availability

Online features require registering an account in-game. [1]

Essential improvements

Patches

Patch 1.2 for retail copies. Steam version is already patched.
Causes Audio issues at higher than 60 FPS and on higher quality audio presets. [5]

Skip intro videos

Change driver name

Game data

Configuration file(s) location

System	Location
Windows	%APPDATA% \bizarre creations\blur\settings.xml
Steam Play (Linux)	/steamapps/compatdata/ 42640 /pfx/ [Note 1]

Save game data location

System	Location
Windows	%APPDATA% \bizarre creations\blur\save\
Steam Play (Linux)	/steamapps/compatdata/ 42640 /pfx/ [Note 1]

Save game cloud syncing

Video

Graphics settings.

High frame rate

This method can only fully restore some of the broken post-processing effects like motion blur while others (like lens flare) may still exhibit broken and inconsistent behaviors. That is if the new internal limit matches the desired external value.

Simply running at a higher rate – regardless of this fix being applied – speeds up camera movement and sensitivity. This fix helps the sped up camera to render at higher internal values.

High frame rate may be somewhat difficult to consistently achieve on some setups due to limited multi-threading. This can be alleviated by using dxvk to wrap D3D9 API calls to Vulkan. This reduces overall CPU usage and overhead but increases GPU usage. [9]

1. Install Cheat Engine and attach the game process.
2. While Blur.exe is selected in the memory search range, search for 0.016666666666 as a float in rounded (extreme) mode, while Executable, Writable and CopyOnWrite is set to Don’t Care and the Fast Scan option disabled.
3. Change all viewed values to 1/FPS (e.g. 0.006944444444 for 144 FPS or to 0.002777777777 for 360 FPS) of which there should be three instances of. This will cause the gameplay to slow down.
4. Search for 60.000000000000 with the same options mentioned above, individually change each instance to the desired value until the two values that return the game to the intended speed are found.
5. Remove all irrelevant values and than save the cheat table.

Temporary solution. The saved cheat table must be used and its values changed with each launch.
This method will not alter the effective range of the “Shock” power-up.

1. Open Blur.exe with a hex editor such as HxD.
2. Replace all instances of 89 88 88 3C (60 FPS) with one of the following,
   • 89 88 08 3C for 120 FPS.
   • 39 8E E3 3B for 144 FPS.
   • 89 88 88 3B for 240 FPS.
   • 61 0B 36 3B for 360 FPS.
3. Replace the first instance of 00 00 70 42 (60 FPS) with one of the following,
   • 00 00 F0 42 for 120 FPS.
   • 00 00 10 43 for 144 FPS.
   • 00 00 70 43 for 240 FPS.
   • 00 00 B4 43 for 360 FPS.
4. If gameplay speed becomes slow change other instances of 00 00 70 42 ; however, if not possible, all instances can be replaced at once without any noticeable changes to gameplay.