» Wed May 16, 2012 6:07 am
The story behind the AMD release day troubles as I understood it was that id tested it with 'fixed'/optimized drivers from AMD, but on Rage launch day AMD didn't manage to release the correct version. What happened after that I don't know, all I know is that only with 11.11 now finally released I can finally play Rage on my AMD GPU. I get the impression AMD's always been very slow to roll out 'fixes' (not neccesarily due to incompetence but maybe they have some elaborate release engineering process) and they already had to deal with releasing Battlefield 3 optimized drivers, maybe that screwed things up too. Not sure if I should blame id or AMD, clearly id shouldn't have made their game depend so heavily on some specific driver release without guarantees it would be available on launch day... but maybe they both deserve some heat.
As for the root cause of the issues, Rage being an OpenGL game and megatexturing being a somewhat unique technology, it's entirely possible neither Rage or the AMD driver had any actual bugs but Rage simply could have used the OpenGL api (which isn't used for Windows games very often anymore) in ways that aren't as optimized as could be om AMD's drivers.. that's pure speculation, but something that should be considered before you start pointing fingers