The newest game from the Tomb Raider franchise – the 10th in the franchise, a reboot telling how Lara Croft became Tomb Raider and doesn’t carry any of the storyline from the previous games. This is the fourth Tomb Raider game developed by Crystal Dynamics, and they used a heavily modified and updated Crystal engine, the engine they used in Tomb Raider Underworld and Guardian of Light. As a result, the game now supports DX11 features like hardware tessellation, super-sample anti-aliasing, and the new TressFX developed by AMD – a hair physics effects rendering a realistic hair animation.
We’re gonna take a look at how this game will perform on low-end systems and possible ways how to improve its performance.
Test System and Requirements
|Test System||Minimum requirements|
|Processor||Intel Celeron G550 2.6 GHz Dual-core||Dual core CPU: AMD Athlon64 X2 2.1 Ghz (4050+), Intel Core2 Duo 1.86 Ghz (E6300)|
|Memory||4GB DDR3 1600MHz||2 GB|
|Video Card||AMD Radeon HD 7750 1GB DDR5 |
nVidia GeForce 9600GT 512MB DDR3
|DirectX 9 graphics card with 512Mb Video RAM, AMD Radeon HD 2600 XT, nVidia 8600|
|Driver / Patch version||AMD Catalyst 13.2 Beta 7|
nVidia Forceware 314.07
|1.0.722.3 Survival Edition|
|Windows 8 64-bit Windows 7 SP1 64-bit / DX 11||Windows XP Service Pack 3, Windows Vista, Windows 7, Windows 8 (32bit/64bit)|
The requirements is not that high and probably older system can still manage to play the game with good performance, but we have to assume that it will only be on “Low” settings.
All tests were done with the following components and settings
- Intel Celeron G550 2.6 GHz Dual-core
- 4GB DDR3 1600MHz
- AMD Radeon HD 7750 1GB DDR5
- Windows 7 SP1 64-bit
- Normal preset, 1920×1080 (1600×900 for individual settings tests)
- Fraps 3.5.9 for recording average and minimum frames per second; 60 seconds and twice for each test.
Built-in Benchmarking Tool vs Actual Gameplay
I was curious if the built-in benchmarking tool really represents the performance of the game, so I picked an “actual” gameplay to compare with. The level is from Helicopter Hill to Windmill Campsite.
At Low, Normal, and Ultimate preset, the two benchmarking process displayed different results, most especially at Low preset with 14fps difference. Only at Ultra preset where the two process displayed almost identical results with 21 and 22 frames per second. I also noticed that at Ultra and Ultimate presets, the actual gameplay exhibited faster performance than using the Built-in benchmarking tool.
With these uneven results, I decided to use the actual gameplay for the rest of the tests. I am not saying that the built-in benchmarking tool is unreliable, it’s just I’m more comfortable using the gameplay for benchmarking. And besides, It’s the “actual gameplay”.
You can read a more detailed article here from our partner site comparing benchmarking using built-in tools against actual gameplay.