The goal of this content is to show that HBAO and SSAO have negligible performance impact on Battlefield 1 performance when choosing between the two. This benchmark arose following our Battlefield 1 GPU performance analysis, which demonstrated consistent frametimes and frame delivery on both AMD and nVidia devices when using DirectX 11. Two of our YouTube commenters asked if HBAO would create a performance swing that would favor nVidia over AMD and, although we've discussed this topic with several games in the past, we decided to revisit for Battlefield 1. This time, we'll also spend a bit of time defining what ambient occlusion actually is, how screen-space occlusion relies on information strictly within the z-buffer, and then look at performance cost of HBAO in BF1.
We'd also recommend our previous graphics technology deep-dive, for folks who want a more technical explanation of what's going on for various AO technologies. Portions of this new article exist in the deep-dive.
Battlefield 1 marks the arrival of another title with DirectX 12 support – sort of. The game still supports DirectX 11, and thus Windows 7 and 8, but makes efforts to shift Dice and EA toward the new world of low-level APIs. This move comes at a bit of a cost, though; our testing of Battlefield 1 has uncovered some frametime variance issues on both nVidia and AMD devices, resolvable by reverting to DirectX 11. We'll explore that in this content.
In today's Battlefield 1 benchmark, we're strictly looking at GPU performance using DirectX 12 and DirectX 11, including the recent RX 400 series, GTX 10 series, GTX 9 series, and RX 300 series GPUs. Video cards tested include the RX 480, RX 470, RX 460, 390X, and Fury X from AMD and the GTX 1080, 1070, 1060, 970, and 960 from nVidia. We've got a couple others in there, too. We may separately look at CPU performance, but not today.
This BF1 benchmark bears with it extensive testing methodology, as always, and that's been fully detailed within the methodology section below. Please be sure that you check this section for any questions as to drivers, test tools, measurement methodology, or GPU choices. Note also that, as with all Origin titles, we were limited to five device changes per game code per day (24 hours). We've got three codes, so that allowed us up to 15 total device tests within our test period.
Mirror’s Edge Catalyst is EA’s reboot of their 2009 first-person parkour game. The first Mirror’s Edge was well-received for its advanced visuals and intuitive, mechanical gameplay. For some of those who played the first ME, time has only sweetened memories of the innovative parkour-style gameplay. When EA and DICE announced the sequel, we were immediately interested -- we liked the first game most for its time trials and 3D platforming, somewhat unique in execution with Mirror’s Edge.
Like its predecessor, gameplay in ME Catalyst is deceptively simple. You run, you jump, you slide, and sometimes, you kick. We pick-up playing as Faith, a young woman who makes her living as an aptly titled ‘runner.’ If you couldn’t guess, that means she runs items and information from point-to-point, like a courier -- but in a dystopian future where private security companies routinely invade the privacy of citizens. Runners allow data to be moved about more discreetly. As a runner, you traverse the rooftops of Glass -- the city ME Catalyst takes place in -- almost entirely made of a white concrete that stays freakishly clean. Those rooftops also host a lot of ventilation, piping, and fences, all of which are used to the advantage of our parkour-trained runner. Navigation of the rooftops is left largely up to player, but certain obstacles light-up red to guide the player towards the objective.
Mirror's Edge – the first game – had some of the most intensive graphics of its time. Just enabling PhysX alone was enough to bring most systems to their knees, particularly when choppers unloaded their miniguns into glass to create infinitesimal shards. The new game just came out, and aims to bring optimized, high-fidelity visuals to the series.
Our Mirror's Edge Catalyst graphics card benchmark tests FPS performance on the GTX 1080, 1070, 970, 960, AMD R9 Fury X, 390X, 380X, and more. We're trying to add more cards as we continue to circumvent the DRM activation restrictions – which we're mostly doing by purchasing the game on multiple accounts (update: we were able to get around the limitations with two codes, and it seems that the activation limitation expires after just 24 hours). The video card benchmark looks at performance scaling between High, Ultra, and “Hyper” settings, and runs the tests for 1080p (Ultra), 1440p (Ultra), and 4K (High), with a splash of 1080p/Hyper tests.
We've also looked briefly into VRAM consumption (further below) and have defined some of the core game graphics settings.
Recapping last week's game news -- following our DOOM benchmark and review -- mostly looks at major Overwatch playerbase announcements, future Star Wars titles (and an RTS, maybe?), and Ubisoft's plans through March, 2017.
Overwatch announced a major achievement in its acquisition of 9.7 million active players during its beta weekend, Respawn Entertainment teased its work on a new Star Wars title, as did EA, and Blizzard is making moves toward an eSports media network.
Video below, script below that.
EA and Dice seem to be having trouble counting. Yesterday, EA launched a campaign blitz for the next Battlefield title -- “Battlefield 1.” Presumably, the title refers to the game’s setting which was previously confirmed World War One. The newly released trailer, as well as the two-hour livestream celebrating the franchise, finalize the setting that had been accidently leaked months ago through NeoGaf.
Breaking news from Germany -- Duke Franz Ferdinand is dead.
Well, maybe -- a NeoGAF listing by EA re-confirmed Battlefield 5, a game we already knew would ship from a recent EA earnings call. While this isn’t shocking, the setting is: according to the store listing, the Battlefield franchise will go back in time to World War 1. This rumor starts with the listed description of the game (now redacted), which states auf Deutsch that the game in question is “Mehrspieler Taktik Shooter im 1. Weltkrieg.” In the language of the victors, that’s “multiplayer tactical shooter in WW1.” If the unintentional leak is true, this would be a first for the Battlefield franchise and takes us back farther than its 1942 - Vietnam roots.
It's game launch season. This is the busiest time of year for the games industry, and that's apparent to anyone who's followed recent launches – it's been one hit after the next. Black Ops III led into Fallout 4, into Battlefront, into Assassin's Creed Syndicate, and now Blizzard's Overwatch. The intensity of the season makes for plenty of discussion topics in the gaming news space (and for lots of benchmarking), something that GN's newest commentator is eager to discuss.
This week's biggest news items include, perhaps obviously, Assassin's Creed Syndicate & Battlefront launches, the Overwatch beta weekend, and some Star Citizen Alpha 2.0 news. Our loose script / video outline can be found below the news recap!
It’s time to pick up the blasters and lightsabers again. After 10 years, the Star Wars “Battlefront” franchise is returning to something bigger than a handheld device. Initially announced two years ago, EA is now sending out invitations to a closed alpha test for the PC version of Star Wars Battlefront. You can join in by signing up at starwars.ea.com.
Despite recent patches to Battlefield 4, issues within the game are still prevalent on every platform. Issues being experienced have been addressed by DICE on their forums. Courtesy of their post updated on the 20th, known issues are listed below.
We moderate comments on a ~24~48 hour cycle. There will be some delay after submitting a comment.