Anonymous edits have been disabled on the wiki. If you want to contribute please login or create an account.


Warning for game developers: PCGamingWiki staff members will only ever reach out to you using the official press@pcgamingwiki.com mail address.
Be aware of scammers claiming to be representatives or affiliates of PCGamingWiki who promise a PCGW page for a game key.

Difference between revisions of "Quantum Break"

From PCGamingWiki, the wiki about fixing PC games
(Added WineHQ)
Line 368: Line 368:
 
|shader model versions  =  
 
|shader model versions  =  
 
|shader model notes    =  
 
|shader model notes    =  
|windows 32-bit exe    = unknown
+
|windows 32-bit exe    = false
 
|windows 64-bit exe    = true
 
|windows 64-bit exe    = true
 
|windows exe notes      =  
 
|windows exe notes      =  

Revision as of 14:37, 2 November 2019

Quantum Break
Cover image missing, please upload it
Developers
Remedy Entertainment
Publishers
Digital Microsoft Studios
Retail Nordic Games[1]
Engines
Northlight
Release dates
Windows April 5, 2016[2]
Quantum Break on Wikipedia

Key points

Game requires a CPU with support for the POPCNT instruction. A CPU under the system requirements won't have this and thus won't work, although this can be worked around.

General information

Steam Community Discussions

Availability

Source DRM Notes Keys OS
Retail
Icon overlay.png
Timeless Collector's Edition. Includes 5 DVDs.[1]
Windows
GamersGate
Icon overlay.png
Windows
Gamesplanet logo.svg
Icon overlay.png
Windows
Green Man Gaming
Icon overlay.png
Windows
Humble Store
Icon overlay.png
Windows
Microsoft Store
Microsoft Store
Windows
Steam
Icon overlay.png
Windows
All versions other than the Microsoft Store version require Steam DRM.

Version differences

The Steam version is Direct3D 11 only[3] while the Microsoft Store version is Direct3D 12 only.[4]

Essential improvements

Skip intro videos

Delete or rename video files[citation needed]
  1. Go to <path-to-game>\videos\
  2. Delete or rename startvideos.bk2 and startvideos_4k.bk2.

Game data

Configuration file(s) location

System Location
Microsoft Store %LOCALAPPDATA%\Packages\Microsoft.QuantumBreak_8wekyb3d8bbwe\LocalState\renderer.ini
Steam %LOCALAPPDATA%\QuantumBreak\renderer.ini
Steam Play (Linux) <Steam-folder>/steamapps/compatdata/474960/pfx/[Note 1]

Save game data location

System Location
Microsoft Store %LOCALAPPDATA%\Packages\Microsoft.QuantumBreak_8wekyb3d8bbwe\LocalState\LSAO\
Steam %LOCALAPPDATA%\QuantumBreak\
Steam Play (Linux) <Steam-folder>/steamapps/compatdata/474960/pfx/[Note 1]

Save game cloud syncing

System Native Notes
Steam Cloud
Xbox Cloud
Saves are synced with the Xbox One version.[5]

Video settings

Graphics settings.
Graphics settings.

Template:Video settings

Windowed

Config file[citation needed]
  1. Go to the configuration files location.
  2. Open renderer.ini.
  3. Find the following lines, and set them to the desired values.
"m_iResolutionX": 1920,
"m_iResolutionY": 1080,

Input settings

General settings.
General settings.
Keyboard rebinding.
Keyboard rebinding.
Controller layout.
Controller layout.

Template:Input settings

Audio settings

Audio settings.
Audio settings.

Template:Audio settings

Localizations

Language UI Audio Sub Notes
English
French
German
Italian
Japanese
Korean
Brazilian Portuguese
Russian
Spanish
Choice of Mexican or International.
Traditional Chinese
Choice of China or Taiwan.

VR support

3D modes State Notes
Nvidia 3D Vision
See Helix Mod: Quantum Break (Steam version). Steam version only.

Issues fixed

Jack wearing an eyepatch

Playing the Microsoft Store version while signed out of the Store app triggers this issue.
Open the Store app and sign into the Microsoft account that owns the game before playing[6]

Nvidia SLI support (Steam version)

SLI support can be set manually for the Steam version (up to 95% scaling).[7]
Use Nvidia Inspector[7][8]
  1. Open Nvidia Profile Inspector.
  2. Find the Quantum Break profile
  3. Set the SLI compatibility flag for its DX11 mode to 0x080002F5
  4. Go to the SLI section
  5. Set number of GPUs to SLI_PREDEFINED_GPU_COUNT_DX10_FOUR
  6. Set Nvidia predefined SLI mode on DirectX 10 to SLI_PREDEFINED_MODE_DX10_FORCE_AFR

POPCNT instruction

Although the developers state that POPCNT instruction is required[9] to run the game, in reality this is not true, at least for the Steam release.
For Windows Store version see this workaround
If you have your CPU doesn't support the POPCNT instruction, then your CPU is below the system requirements of this game. Expect the game to run poorly on your PC.
Remove POPCNT check in rl_x64_f.dll[10]
  1. Get hex editor. HxD is free, portable and easy to use.
  2. Open dx11\rl_x64_f.dll in hex editor. Use "Browse local files" in Steam game options to find path to Quantum Break folder.
  3. Search for 0FBAE117730A hex string.
  4. Replace it with 0FBAE1179090 hex string.

GIF showing the steps to perform in HxD

Remove POPCNT check.gif

Other information

API

Technical specs Supported Notes
Direct3D 11, 12 Steam is Direct3D 11 only,[3] Microsoft Store is Direct3D 12 only.[4]
Executable 32-bit 64-bit Notes
Windows

Middleware

Middleware Notes
Physics Havok, NaturalMotion
Audio Wwise
Interface Autodesk Gameware
Cutscenes Bink Video Pre-Rendered Only

System requirements

Windows[2]
Minimum Recommended
Operating system (OS) 7 (Steam), 10 (Microsoft Store)
Processor (CPU) Intel Core i5-4460, 2.70 GHz
AMD FX-6300
System memory (RAM) 8 GB
Hard disk drive (HDD) 55 GB
Video card (GPU) Nvidia GeForce GTX 760
AMD Radeon R7 260x
2 GB of VRAM
DirectX 11 compatible
64-bit operating system is required.
Ultra requirements: Intel Core i7-4790 or AMD equivalent, Nvidia GeForce GTX 980 Ti or AMD Radeon R9 Fury X, 16 GB of RAM, 6 GB of VRAM.

Notes

  1. 1.0 1.1 File/folder structure within this directory reflects the path(s) listed for Windows and/or Steam game data (use Wine regedit to access Windows registry paths). Games with Steam Cloud support may store data in ~/.steam/steam/userdata/<user-id>/474960/ in addition to or instead of this directory. The app ID (474960) may differ in some cases. Treat backslashes as forward slashes. See the glossary page for details.

References