That makes more sense than no-aa-in-dx9.That's what I seemed to remember: No MRT+MSAA in DX9 - not just UE3 but an API limitation. Now just looked it up again in google.
That makes more sense than no-aa-in-dx9.That's what I seemed to remember: No MRT+MSAA in DX9 - not just UE3 but an API limitation. Now just looked it up again in google.
Yes, that's why i explicitly mentioned that it wasn't possible in Batman: Arkham Asylum - not in dx9 in general.That makes more sense than no-aa-in-dx9.
Antialiasing in Batman:AA was/is a hack not possible by the standards of DX9, AFAIBT. So while it's not "nice" to not open it up, it's at least understandable - just imagine, there'd be some kind of error, running that code on Ati cards: "Nvidia injected viral code in order to cripple competitors' image quality/game performance ZOMG!"
The only problem with that is Nvidia locked it up in Legalese. When ATI was asked to provide their own version for use in the game, they did so.
Only to then find out that it would not be legally possible to be used because it was exactly the same as what Nvidia had provided, and Nvidia had a binding legal contract with regards to that. And when other software developers were asked about it, it was claimed it was the standard/easiest way that most developers would have used to implement AA in a Dx9 title. But hey, use lawyers to prevent either the developer or the opposition from implementing it. And then to add injury to insult make sure it's included in the DRM, so that users wouldn't be able to hack it in without violating the terms of use for that game.
Hardly something to wrap up in legal BS, eh? It was and remains an especially deplorable act of a company desperate to stem the loss of marketshare. And then making sure that the base experience would have zero fog with which to compare to the PhysX animated fog. What better way to make PhysX look better than what it was. I mean it would have already looked better in comparison to either static or limited movement fog. But hey, we can make it look absolutely super. With PhysX you get Fog. With no PhysX your system can't even do Fog, poor wimpy computers without a PhysX accelerator. And on top of that we can even make it react to your player.
Regards,
SB
W1
It's so surreal that you are complaining about one company which is doing something for their customers and yet have no problems that "your's" is doing nothing.
No he's complaining that one company provided a solution that worked on all graphics cards , then went out of their way to actively prohibit it working on other cards, and actively prevented the developer from making it work on other cards, and actively prevented the other graphics card company from providing their own solution
What's the difference between this and a "platform exclusive game" funded by a console vendor?
No one buys Halo at full price, tries to play it on their PS3 and discovers graphical features have been arbitrarily disabled to punish customers with the wrong hardware? And there's a pretty big difference between Sony or MS fully or significantly funding development of an exclusive game and nVidia's dev relations team emailing a developer their bog-standard UE3 MSAA code.
It's funny that so many supposedly smart people still can't grasp the difference between "disabled for them" and "enabled only for me". Or maybe they can but disabled just sounds so much more dastardly! Here's a hint - something can only be disabled after first being enabled.
It's funny that so many supposedly smart people still can't grasp the difference between "disabled for them" and "enabled only for me". Or maybe they can but disabled just sounds so much more dastardly! Here's a hint - something can only be disabled after first being enabled.
It's funny that so many supposedly smart people still can't grasp the difference between "disabled for them" and "enabled only for me". Or maybe they can but disabled just sounds so much more dastardly! Here's a hint - something can only be disabled after first being enabled.
Of course it makes a difference. If nVidia did nothing and the result was that nobody got AA, ATi users would be no better off and there would be a lot less complaining. It is the enabling of AA on Geforces that started the whinefest, not disabling it on Radeons.
No one buys Halo at full price, tries to play it on their PS3 and discovers graphical features have been arbitrarily disabled to punish customers with the wrong hardware? And there's a pretty big difference between Sony or MS fully or significantly funding development of an exclusive game and nVidia's dev relations team emailing a developer their bog-standard UE3 MSAA code.
Actually it was the fact that we aren't idiots and people came out with a 2 second hack that lets fsaa work on Radeon cards that started the whinefest. It became obvious to everyone except you that its a feature beign with held due to nvidia's marking choices which are harmful to consumers.
For one, when they provided (or at least helped to provide?) the AA solution for STALKER (I think it was the first "expansion" or "sequel"), they didn't limit it for their cards only. They also worked on the DX10.1 support, optimized it, and on top of all that, even worked to get many of their improvements for DX10 path, even though at the time AMD had 2 generations of 10.1 hardware and nVidia had only DX10Of course, maybe ATI would do that, but how do you know that ATI wouldn't make it exclusive to them?
It's a simple question. Without nVidia's meddling would ATi users have gotten AA support in Batman? If the answer is no, and that's what it seems to be, then ATi users have no reason to be upset. But that assumes people are rational which of course isn't the case.