AMD To NVIDIA: If You Can’t Beat’em, Blame’em; Controversy Carries On

Alessio Palumbo
Posted Aug 18, 2015
190Shares
Share Tweet Submit

Yesterday, just after the press embargo ended, we published our DirectX 12 benchmarks based on Ashes of the Singularity’s Alpha build along with NVIDIA’s own take on the test.

As you’re probably aware now, controversy ensued with Oxide & Stardock answering back that the test was indeed valid and there was no MSAA performance bug in DX12 mode.

However, the controversy flame may have been just ignited to a much greater degree with AMD suddenly joining the verbal fray. On Twitter, our very own article detailing NVIDIA’s response has been linked to Roy Taylor, Corporate Vice President of AMD, who replied as follows a few hours ago:

if you can’t beat em blame em. From the makers of gameworks

https://twitter.com/amd_roy/status/633535969015275521

That’s surely going to keep the debate heated for a while. In the meantime, Stardock has commented further on the situation with NVIDIA; Brad Wardell himself replied on the forum thread.

We’ve offered to do the optimization for their DirectX 12 driver on the app side that is in line with what they had in their DirectX 11 driver.  Though, it would be helpful if Nvidia quit shooting the messenger.

It sounds like there may be a solution coming up to fix NVIDIA’s DX12 performance woes in Ashes of the Singularity.

Wardell also added that the “MSAA issue” described by NVIDIA would occur in any DirectX 12 game currently.

What I can say, with absolute certainty: The MSAA issue they described will happen on any DirectX 12 game currently.  That’s why we were surprised they tried to describe the issue as a “bug” in our code.

I don’t expect it to be an issue for long though.  Even as recently as last week, Nvidia released an updated driver that made significant performance gains with Ashes.

We’ll keep you updated in case there are any followups to this story.

Share Tweet Submit