The Crew 2 Laptop and Desktop Benchmarks
Game Engine
Hardly anything appears to have changed visually between The Crew and The Crew 2, despite there being four years between the two games. The textures, characters, their animations and the damage model could all be better in The Crew 2. The damage model is particularly rudimentary. Crashing into objects and other cars yield only stylized scratches. We could not get the cars to dent or lose any bodywork regardless of the impact to which they were subjected.
The Crew 2 has impressive draw distances though, and the reflections are pretty albeit not particularly sharp. Likewise, the cars are designed with such a high attention to detail that they often resemble both the inside and outside of real counterparts. For example, Ubisoft has done a great job at accurately recreating the Mazda MX-5’s distinctive dashboard and infotainment systems.
The visual effects are decent too. The day to night changes during races, the varying weather and the different seasons all create a good atmosphere, although some environments feel comparatively sterile. There are added visual touches like sparks flying and water splashes that add to the experience too. In short, there is never a dull visual moment on screen.
The Crew 2 generally does a better job at creating an interactive environment its main competitor, EA’s Need for Speed Payback. In The Crew 2, passers-by jump out of the way of imminent danger, while road boundaries like fences and pillars are destructible thanks to the physics system.
Overall, the graphics are fine, but they are uninspiring, as is arguably the driving model. The Crew 2 feels like an arcade racer rather than a simulation, with each vehicle handling in a similarly unrealistic fashion. Casual gamers will get their money’s worth out of The Crew 2, but many gamers will get sick of the game’s lacklustre collision system.
We did not get a chance to complete the story mode, so we can only offer a more general judgment. The story during the first few hours of play feels cliched and uninspired. The story mode is often poor in racing games though, so The Crew 2 is not particularly bad in this respect.
The keyboard layout and menu guidance are as cumbersome as they are on Need For Speed Payback though. It is obvious that Ubisoft designed The Crew 2 with consoles in mind when playing with a keyboard.
Fortunately, The Crew 2 has comprehensive graphics options. There are twenty graphical options across various menus which are organized by resolution, picture mode, brightness levels and details. The Crew 2 starts to come into its own from mid-range settings upwards, but there are often only subtle differences between default graphics levels. For example, High and Ultra hardly differ visually.
Graphics options can be set according to a few presets for those who do not fancy tinkering with the wealth of options available. Graphics changes are implemented without restarting the game too, which is a bonus as there are non-skippable intro videos and the game takes a while to load through Uplay. Uplay is effectively Ubisoft’s answer to Steam and acts as a launcher and store for Ubisoft games.
There are no load screens once you are past the initial boot up though, which is impressive given The Crew 2’s freely navigable open world.
We cannot understand why Ivory Tower, the development studio responsible for the first part of the game, integrates an FPS limit. The Crew 2 will only run at a maximum of 60 FPS even with V-Sync disabled. This means that the game cannot take advantage of high refresh rate displays that would make the game look even smoother. We attempted to bypass the 30/60 FPS lock by editing the PCScalability file in the Documents folder to no avail, so all benchmarks are limited to 60 FPS. To make matters worse, The Crew 2 does not even feel that smooth at 60 FPS either.
The Crew 2 should run at a constant 60 FPS while other racing games vary between 30 and 60 FPS. However, we experienced random performance jitters on some systems for which we have no explanations as to why they occurred.
The installation size is 24 GB, which is fairly small given the size of The Crew 2’s map. The game needs to be permanently connected to the internet even on single player, while rules out gaming on the go, for example.
Benchmarks
We picked a race set in Las Vegas for our speed tests and is accessible shortly after the game’s tutorial. We recorded almost a forty-second sequence using Fraps, which correlates to around 20% of the race distance. You can watch the video below.
The Crew 2 does suffer some frame rate fluctuations because of changing light and weather conditions. These change from race to race so our results are not always a 1:1 comparison.
The FPS lock also means that we are unable to see the difference in performance between stronger CPUs, at least when playing the game in Full HD. Some powerful high-end GPUs struggle to hit 60 FPS at 3,840x2,160 with details set to High or Ultra mind you.
Results
The Crew 2 has relatively moderate system requirements. Integrated GPUs like the Intel HD Graphics 630 will not be able to run the game at any settings, but entry-level dedicated GPUs like the NVIDIA GeForce 940M will be able to run the game at 1,280x720 with graphics set to low. We recommend a mid-range GPU if you would like to run The Crew 2 at 1,920x1,080. Medium to high details is playable on an NVIDIA GeForce GTX 1050, while the ultra preset requires at least an NVIDIA GeForce GTX 1050 Ti.
Actual high-end GPUs are needed for playing the game in higher than Full HD. We would recommend pairing The Crew 2 with at least an NVIDIA GeForce GTX 1060 for gaming at 2,560x1,440 and an NVIDIA GeForce GTX 1080 Laptop GPU for playing the game at 3,840x2,160.
The Crew 2 | |
3840x2160 Ultra Preset 2560x1440 Ultra Preset 1920x1080 Ultra Preset 1920x1080 High Preset 1920x1080 Medium Preset 1280x720 Low Preset | |
NVIDIA GeForce GTX 1080 Ti (Desktop), i7-7740X | |
NVIDIA GeForce GTX 1080 (Desktop), 6700K | |
NVIDIA GeForce GTX 1080 Mobile, i7-7820HK | |
NVIDIA GeForce GTX 1070 (Desktop), 6700K | |
NVIDIA GeForce GTX 1070 Mobile, 6820HK | |
NVIDIA GeForce GTX 1060 (Desktop), 6700K | |
NVIDIA GeForce GTX 980, 6700K | |
NVIDIA GeForce GTX 1060 Mobile, 6820HK | |
AMD Radeon RX 480 (Desktop), i7-7740X | |
NVIDIA GeForce GTX 980M, 6700HQ | |
NVIDIA GeForce GTX 1050 Ti Mobile, i7-7700HQ | |
NVIDIA GeForce GTX 1050 Ti Mobile, i5-7300HQ | |
AMD Radeon RX 460 (Desktop), i7-7740X | |
NVIDIA GeForce GTX 970M, 6700HQ | |
NVIDIA GeForce GTX 1050 Mobile, i7-7700HQ | |
NVIDIA GeForce GTX 1050 Mobile, i7-7700HQ | |
NVIDIA GeForce GTX 965M, 6700HQ | |
NVIDIA GeForce GTX 960M, i7-7700HQ | |
NVIDIA GeForce GTX 950M, 6700HQ | |
NVIDIA GeForce MX150, i7-7700HQ | |
NVIDIA GeForce MX150, i5-8550U | |
NVIDIA GeForce 940MX, 6700HQ | |
NVIDIA GeForce 940M, 5700HQ | |
AMD Radeon R9 M280X, FX-7600P | |
NVIDIA GeForce 920M, 2970M | |
Intel UHD Graphics 620, i5-8550U | |
Intel HD Graphics 615, i7-7Y75 | |
Intel HD Graphics 630, i7-7700HQ |
Overview
Test Systems
Device | Graphics Card | Processor | RAM | Operating System |
---|---|---|---|---|
Desktop PC I | MSI GeForce GTX 1080 (8GB GDDR5X) MSI GeForce GTX 1070 (8GB GDDR5) NVIDIA GeForce GTX 1060 (6GB GDDR5) NVIDIA GeForce GTX 980 (4 GB GDDR5) |
Intel Core i7-6700K | 2 x 8 GB DDR4 | Windows 10 64 bit |
Desktop PC II | NVIDIA GeForce GTX 1080 Ti (11 GB GDDR5X) ASUS GeForce GTX 980 Ti (6 GB GDDR5) XFX Radeon R9 Fury (4 GB HBM) Sapphire Radeon R9 290X (4GB GDDR5) Sapphire Radeon R9 280X (3GB GDDR5) MSI Radeon R7 370 (2GB GDDR5) |
Intel Core i7-4790K | 2 x 4GB DDR3 | Windows 10 64-bit |
Alienware 17 R4 | NVIDIA GeForce GTX 1080 (8GB GDDR5X) | Intel Core i7-7820HK | 1 x 16GB DDR4 | Windows 10 64-bit |
ASUS G752VS | NVIDIA GeForce GTX 1070 (8GB GDDR5) | Intel Core i7-6820HK | 2 x 16GB DDR4 | Windows 10 64-bit |
MSI GT62VR | NVIDIA GeForce GTX 1060 (6GB GDDR5) | Intel Core i7-6820HK | 2 x 8GB DDR4 | Windows 10 64-bit |
MSI GE72 | NVIDIA GeForce GTX 1050 Ti (4 GB GDDR5) | Intel Core i7-7700HQ | 2 x 4 GB DDR4 | Windows 10 64 Bit |
ASUS GL753VD | NVIDIA GeForce GTX 1050 (4GB GDDR5) | Intel Core i7-7700HQ | 1 x 8GB DDR4 | Windows 10 64-bit |
MSI GL62 | NVIDIA GeForce GTX 1050 (2GB GDDR5) | Intel Core i7-7700HQ | 2 x 4GB DDR4 | Windows 10 64-bit |
ASUS G752VY | NVIDIA GeForce GTX 980M (4GB GDDR5) | Intel Core i7-6700HQ | 2 x 16GB DDR4 | Windows 10 64-bit |
MSI GS60 | NVIDIA GeForce GTX 970M (3GB GDDR5) | Intel Core i7-6700HQ | 2 x 4GB DDR4 | Windows 10 64-bit |
MSI GE72 | NVIDIA GeForce GTX 965M (2GB GDDR5) | Intel Core i7-6700HQ | 1 x 8GB DDR4 | Windows 10 64-bit |
MSI GL72 | NVIDIA GeForce GTX 960M (2GB GDDR5) | Intel Core i7-7700HQ | 1 x 8GB DDR4 | Windows 10 64-bit |
MSI PE60 | NVIDIA GeForce GTX 950M (2GB GDDR5) | Intel Core i7-6700HQ | 2 x 4GB DDR4 | Windows 10 64-bit |
MSI PL62 | NVIDIA GeForce MX150 (2GB GDDR5) | Intel Core i7-7700HQ | 1 x 8GB DDR4 | Windows 10 64-bit |
MSI CX72 | NVIDIA GeForce 940MX (2GB DDR3) | Intel Core i7-6700HQ | 2 x 8GB DDR4 | Windows 10 64-bit |
MSI GP62 | NVIDIA GeForce 940M (2GB DDR3) | Intel Core i7-5700HQ | 1 x 8GB DDR3 | Windows 10 64-bit |
MSI CX61 | NVIDIA GeForce 920M (2GB DDR3) | Intel Celeron 2970M | 1 x 8GB DDR3 | Windows 10 64-bit |
ASUS N551ZU | AMD Radeon R9 M280X (4GB GDDR5) | AMD FX-7600P | 2 x 4GB DDR3 | Windows 10 64-bit |
4K Monitor | NVIDIA drivers | AMD drivers |
---|---|---|
2 x Asus PB287Q, Philips 328P6VJEB | ForceWare 398.36 | Adrenalin 18.6.1 |