Conclusion: My own two cents
There are only two conclusions you can make. The First one is the subject of this analysis, Batmangate. After carefully reviewing statements released by all sides, talking to developers, there isn't much left. Forum members on Batman: Arkham Asylum Forums and AMD themselves all changed the vendor ID on their cards and got equal functionality as the one experienced on nVidia cards. This happened at the time when nVidia members both claimed that Batman AA code is proprietary to Eidos and that no vendor ID locks is implemented in the code. "Hands in a cookie jar" is the only parallel we can draw here.
With their engineering resources spread on DirectX 11 titles, it is natural that AMD could not dedicate themselves on making Batman: AA code. But what is unforgiveable for both sides is the fact that Unreal Engine 3
is out for four years now and nor AMD nor nVidia didn't develop a way for in-game AA selection for engine itself. Ultimately, the responsibility for FSAA doesn't lie neither with nVidia nor AMD. For a feature that became a standard in 2000, i.e. nearly 10 years ago, it is irresponsible that Epic Games didn't offer built-in AA support as the new versions of Unreal Engine rolled out. Being forced to develop multi-platform titles to survive, developers such as Rocksteady have thin resources to spend additional time on developing PC-only features, especially in a recession year when so many great studios closed their doors.
Secondly, if AMD is constantly criticizing nVidia as a company and deployed strategies, it would be nice to finally hear some positive AMD-related experience from the developers. Naturally, AMD needs to earn that respect first - while on USS Hornet, AMD disclosed the list of DirectX 11 titles that are coming out and if those developers don't start publicly saying that AMD's support is great - something will have to change.
© 2009 - 2013 Bright Side Of News*, All rights reserved.