Originally posted by: Wreckage
No it's clearly and 100% AMDs fault.
How? Their hardware already supports the in-game implementation, and the work has already been done.
Why should AMD get a free lunch? So while NVIDIA did all the ground work to help AA get going with the developer, AMD should just get to sit at home and wait for a check to arrive.
You might have a point if there was something inherently special about the implementation that only made in-game AA possible on nVidia?s cards. But that isn?t the case because it works unaltered on ATi cards. It also appears to be no faster than driver AA, so the argument that it?s more efficient doesn?t seem to apply either.
Your argument failed. AA is not a "standard feature" of the Unreal Engine.
According to Sweeney the engine supports it under DX10.
Wrong again. It has to be programmed into the game for it to work "in game" otherwise you have to force it globally which is less efficient.
In fact AA does run on Batman by using CCC, it's just slower. So what really have they lost out on?
Someone tested it in the other thread and they claimed there?s no performance difference between in-game AA and nVidia?s control panel. If true it again begs the question of what makes it so special that it expended so much effort from nVidia and the developer, and why it needed to be artificially blocked on ATi?s parts.
Well then AMD should have worked with the developer.
Why, given their GPUs already work with the implementation out of the box? The only thing stopping it is the artificial vendor check. Again, you might have a point if it required something special inherent to nVidia?s hardware, but that doesn?t seem to be the case.
This whole thing is looking more and more like a marketing and advertising tool by having an AA toggle that?s artificially grayed out on ATi?s cards.
Kind of like how Crysis? very high options were grayed out on XP despite many settings having absolutely nothing to do with DX10, like sound and physics. Or like how Halo 2 only works on Vista despite not even being DX10.
I guess in these instances you?d claim XP is at fault despite the artificial locks from the developer, and despite the fact that both locks can be defeated on XP?
AMD is holding back game development by not working with game developers, not implementing physics, delaying games and all their other shenanigans.
If you honestly think that nVidia would allow ATi to compete with them with PhysX then your arguments are naïve. If ATi implemented PhysX and it happened to run faster on their boards, do you honestly think nVidia would sit idly by and do nothing? ATi don?t even support PhysX and we?ve already seen nVidia apply a vendor-lock to PhysX by disabling it in systems with ATi cards.
Also DX11 is not an open standard.
Yes it is. Any vendor is free to implement it on their hardware without restriction or royalty requirements. Furthermore Microsoft is vendor agnostic so there?s no conflict of interest, unlike someone trying to compete with nVidia and their own PhysX API.
As for non-MS platforms, I guess you?re not familiar with Crossover games.