Tomb Raider (2013)
|Developer(s)|| Crystal Dynamics|
PC Nixxes Software
|First release date||Windows March 5, 2013|
|Tomb Raider II||1997|
|Tomb Raider III: Adventures of Lara Croft||1998|
|Tomb Raider: The Last Revelation||1999|
|Tomb Raider Chronicles||2000|
|Tomb Raider: The Angel of Darkness||2003|
|Tomb Raider: Legend||2006|
|Tomb Raider: Anniversary||2007|
|Tomb Raider: Underworld||2008|
|Lara Croft and the Guardian of Light||2010|
|Tomb Raider (2013)||2013|
- PC port features high resolution textures, tessellation, high quality shadows and more PC specific features.
- Forcing DirectX 9 mode results in an approximately 25% performance boost at a small loss of visual fidelity.
- Large performance issues with Nvidia graphics cards.
- Many quick time events (QTEs) do not display the key required to complete them. See QTE streamlining for guide.
- Steam Community Discussions
- Steam Users' Forums for Tomb Raider series.
- Tomb Raider Forums - not PC-specific.
- Eidos Forums - not PC-specific.
- All versions require Steam, including both retail and digital distribution.
 Skip game launcher
 Game data
|Registry path||HKEY_CURRENT_USER\Software\Crystal Dynamics\Tomb Raider|
|Local Steam Cloud repository||C:\Program Files\Steam\userdata\<unique Steam ID>\203160\|
- Settings are saved in registry instead of configuration files.
- Steam Cloud is supported for game saves.
- Most of graphics settings in registry corresponds with .ini options for benchmark.
 Video settings
|Multi-monitor||All HUD elements are correctly drawn on the center screen. Some in-game cutscenes display odd animations or missing models in areas that aren't visible in 16:9.|
|Field of view (FOV)||Possible using custom resolutions. See Field of view (FOV).|
|Windowed||For borderless uncheck "exclusive fullscreen".|
|Borderless fullscreen windowed||For borderless uncheck "exclusive fullscreen".|
|Anisotropic filtering (AF)||Up to 16 samples.|
|Anti-aliasing (AA)||FXAA, SSAA x2, and SSAA x4.|
|Vertical sync (Vsync)||Double and tripled buffered.|
- FoV is calculated from aspect ratio, therefore running the game at a custom resolution will result in a custom FoV.
- Nvidia information is hypothetical at this point.
Notes about this fix
- This way of altering the field of view will allow the player to regain some sense of peripheral vision, without altering the ratio between character height and image height. This preserves to some extent the original intention underlying the frame composition.
- There is no distortion of the picture.
- The image will effectively be cropped (Vert-). Black bars will appear at the top and bottom of the screen.
- Having to change the desktop resolution each time is not convenient.
Set custom resolution (AMD/ATI) • Link
Set custom resolution (NVIDIA) • LinkNVIDIA users can specify a custom resolution through the NVIDIA Control Panel.
 Force DirectX 9 renderer on DirectX 11 systems
- Forcing DirectX 9 will result in better performance. However DirectX 11 specific features (tessellation, TressFX) will be disabled.
Custom aspect ratio • Link
Performance difference between DirectX 9 and 11 renderer
Based on ingame benchmark with DirectX 11 features (tessellation, TressFX) disabled for both renderers.
|DirectX 9||DirectX 11||Difference [%]|
Tested on Intel i7 with HD6870 GPU, average of five measurements for each renderer.
 Input settings
|Mouse acceleration||Mouse smoothing can be switched off|
 Issues unresolved
 Persistent crashing on Nvidia graphics cards
- Nvidia graphics cards appear to be causing constant crashing
- Errors occur such as: "Failed to Initialize Direct3D with current settings"
User-made fix • Link
Other possible fixes:
- There is no universal fix yet, but these are confirmed to work for some users:
- Turn off vertical synchronization (vsync).
- Disable tesselation - recommended.
- Disable exclusive fullscreen.
- Revert drivers to version 310.90
- Update to the 314.21 beta drivers
Fix for "Failed to Initialize Direct3D with current settings":
- Manually set the aspect ratio to that of your monitors (ex: 1920x1080=16:9, 1920x1200=16:10)
 Crash with "Fatal error - out of memory" error
There seems to be memory leak within the game. After few hours of playing game can't allocate more memory due to the game executable is only 32 bit and crashes.
 Separate vertical and horizontal sensitivity with mouse
Vertical and horizontal sensitivity do not match, with vertical being much lower, making it hard to aim with a mouse and keyboard.
 Issues resolved
 Low framerate
Low framerate fix • Link
There are several performance demanding options that can be disabled. Get significant FPS boost by:
 Missing effects in fullscreen mode
- Fixed in first patch. If you are still experiencing this issue install path or follow instructions below.
Some camera effects are missing when game is run in fullscreen mode. Effects like lens flares, water drops and blood overlay.
 Flickering and crashing with SLI or CrossFire
 Crashing to desktop and issues with minimizing game
 Graphical artifacts and FPS drop on Nvidia GPUs
 Static noise from music and ambient sound in the game
 Other information
 QTE streamlining
- Tomb Raider is heavy on quick time events (QTEs), which can be sometimes annoying.
- QTEs in Tomb Raider does not display key names but rather icon associated with specific binding or QTE, which can be confusing and problematic to solve.
List of QTEs and possible solutions:
|Hand in red circle||Repeatedly press interact key (default E) as fast as possible.|
|Exclamation mark in red diamond.||Press melee key (default F).|
|White circle getting smaller||Tap repeatedly melee key (default F). This QTE is bugged - circle animation is out of sync with trigger behind QTE and therefore it is difficult win this QTE normally. Luckily there is no penalization for missing said trigger with key press so pressing melee key for whole duration of QTE works perfectly.|
|Left and right arrow||Alternately press left and right movement keys (default A and D).|
|Hand in red circle when Lara is hanging from ledge||Press interact key (default E).|
Bypass mashing keys • Link
1. Open you macro/gaming software and create new macro.
2. Record single key press and make sure there are delays between action at least 20ms. It should look something like this for E key:
Key E down 20ms delay Key E up 20ms delay
3. Set this macro to your desired key and set option to "repeat macro as long as pressed".
 Benchmark mode
- Benchmark mode generates a file named:
benchmarkresults yyyy-mm-dd hh-mm-ss.txt
• LinkBenchmark in game options.
Benchmark from Steam • Link
Benchmark via shortcut • Link
 Command line parameters
|Command line parameter||Type of benchmark|
|-benchmark||Run the benchmark on startup and quit the game when finished.|
|-benchmarkini “filename.ini”||Run the benchmark on startup and quit the game when finished. The ini file contains overrides for quality settings.|
|-loop||Loop the benchmark instead of quitting after it completes. This is a demo mode, so statistics are disabled.|
|-dxdiag||Include dxdiag information in the benchmarkresults file.|
- When running from the command line, exclusive fullscreen is automatically switched on and vsync is switched off.
- When running as a looping demo, a result file is not generated.
 .ini file options
|QualityLevel||0 to 4||Sets all settings to a quality level. 0 for Low, 4 for Ultimate.|
|Fullscreen||0 or 1||Enables or disables fullscreen.|
|ExclusiveFullscreen||0 or 1||Enable this when fullscreen is enabled for better performance but worse multitasking.|
|AspectRatio||Width / height x 10000 or 0||Sets aspect ratio. 16000 for 16:10 for example.|
|VSyncMode||0 - 2||Options for vertical synchronization. 0 for Off, 1 for Double Buffer and 2 for Tripple Buffer.|
|FullscreenWidth||number||Width of resolution in pixels.|
|FullscreenHeight||number||Height of resolution in pixels.|
|FullscreenRefreshRate||number||Screen refresh rate in Hz.|
|StereoEnabled||0 or 1||Enables or disables stereoscopic support.|
|TextureQuality||1 to 4||Texture quality from Low to Ultra.|
|BestTextureFilter||0 to 18||Texture filtering - 0 for No Filtering, 1 for Bilinear, 2 for Trilinear, or 2 + the Anisotropic level.|
|HairQuality||0 or 1||Enables TressFX enhanced hair quality. 0 for Normal or 1 for TressFX.|
|AntiAliasingMode||0 to 3||Sets anti-aliasing level. 0 for none, 1 for FXAA, 2 for 2xSSAA and 3 for 4xSSAA.|
|ShadowMode||0 or 1||Enables or disables shadows.|
|ShadowResolution||0 to 2||Sets shadow resolution. 1 for Off, 2 for Normal and 3 for Ultra.|
|SSAOMode||0 to 2||Sets ambient occlusion quality. 1 for Off, 2 for Normal and 3 for Ultra.|
|DOFQuality||0 to 3||Sets depth of field quality. 1 for Off, 2 for Normal and 3 for Ultra.|
|ReflectionQuality||0 to 2||Sets quality of reflections. 1 for Off, 2 for Normal and 3 for High.|
|LODBias||0 to 4||Sets level of detail bias from Low to Ultra.|
|EnablePostProcess||0 or 1||Enables or disables post-processing effects.|
|EnableHighPrecisionRT||0 or 1||-|
|EnableTessellation||0 or 1||Enables or disables tessellation.|
 System requirements
|Operating system (OS)||Windows XP Service Pack 3, Windows Vista,7,8 (32bit/64bit)||Windows Vista, Windows 7 or Windows 8|
|Processor (CPU)||Dual core CPU, AMD Athlon64 X2 2.1 Ghz (4050+), Intel Core2 Duo 1.86 Ghz (E6300)||Quad core CPU, AMD Phenom II X2 565, Intel Core i5-750|
|System memory (RAM)||1GB (2GB on Vista)||4 GB|
|Video card (GPU)||DirectX 9 graphics card with 512Mb Video RAM, AMD Radeon HD 2600 XT, nVidia 8600||DirectX 11 graphics card with 1GB Video RAM, AMD Radeon HD 4870, nVidia GTX 480|
|Hard disk drive (HDD)||10 GB||10 GB|
- ↑ Tomb Raider PC features, system requirements revealed - Shack News
- ↑ Launch Tomb Raider directly and skip launcher - Steam Community Discussions for Tomb Raider
- ↑ Tested by LDK March 5, 2013.
- ↑ Live Q&A with Jurjen Katsman of Nixxes - Tomb Raider Forums
- ↑ crashing - Steam Community Discussions for Tomb Raider
- ↑ New CTD type: Fatal error, out of memory - Steam Users' Forums for the Tomb Raider series
- ↑ 7.0 7.1 Full Graphics only in windowed mode! (w/Temp Fix at bottom) - Steam Community Discussions for Tomb Raider
- ↑ 8.0 8.1 8.2 8.3 Technical FAQ - Written and produced by EscondeR - Tomb Raider Hub