EA DICE has released a version of Battlefield 4 optimized for AMD's Mantle API. Details on the patch are available in this blog post on the BF4 site, but there's a catch. While the game has been updated for the close-to-the-metal API, the required AMD drivers are missing in action.
The press was scheduled to receive the Mantle-infused Catalyst 14.1 beta driver last night. However, AMD says it had to "kick off another build." We're supposed to get the updated driver some time this morning, at which point we'll furiously begin performance testing, so we can share some results with you soon. Our understanding is that AMD should be making a driver available to the wider public not long after that.
AMD and EA DICE have both released figures detailing Mantle's impact on BF4. Here are the performance increases quoted by AMD:
And here are the performance increases detailed in EA DICE's blog post:
The numbers suggest the Mantle build delivers bigger gains in CPU-limited scenarios. According to EA DICE, the 58% performance increase on the CrossFire-equipped system is due to the CPU being too slow to feed the dual 290X cards. This may be the first time I've seen a six-core Sandy Bridge-E processor referred to as too slow for anything.
The BF4 update includes a performance analysis tool that logs frame times, so we'll be able to do our own testing just as soon as AMD releases the requisite driver. Scott's already set up to gather his own performance data and subjective impressions. Stay tuned.
|Gigabyte's Z170X-Gaming G1 motherboard reviewed||7|
|Star Wars Battlefront video review||37|
|Club 3D active adapters convert DisplayPort 1.2 to HDMI 2.0||21|
|Phanteks' Power Splitter lets two systems run on one PSU||43|
|Just Cause 3 system requirements won't blow up your wallet||27|
|Biostar's GeForce Gaming GTX 950 glows a fiery red||22|
|Asus updates Zenbook UX305 with a Skylake Core M CPU||60|
|Shuttle XPC Nano's svelte body is clad in black and gold||20|
|AMD ends driver support for non-GCN Radeon cards||86|
|This is the answer to SSK's question on the Firefox news post.||+33|