I do not know where to place this, but since it discusses ways in which games are rendered with regards to AA, I think it should be here. I've read it and found it to be quite an eye-opener -
http://www.brightsideofnews.com/news....aspx?pageid=0
Printable View
I do not know where to place this, but since it discusses ways in which games are rendered with regards to AA, I think it should be here. I've read it and found it to be quite an eye-opener -
http://www.brightsideofnews.com/news....aspx?pageid=0
The biggest problem here is that the Unreal 3 engine doesn't have anti-aliasing to begin with. I think it's a little underhanded what nVidia did, but then again they did the work. AMD has a long way to go before they have developer relations even beginning to approach the levels that nVidia has been operating at for years.
Great read. Seems like there is a multitude of people to blame and no one is innocent. I like what Nvidia does for developers and I think it is time for AMD to step up to the plate. I frown upon lock outs but at the same time AMD shouldn't have turned their back on the development team. All they had to do was send in their source code and they would have been supported no problem.
Wow.. fascinating read.
My take aways:
AMD needs to be more aggresive with QA of their hardware and with working with devs.
Nvidia is ruthless enough will do what ever it takes to come out ahead, even if that will negatively affect other consumers.
Edios needs to better protect their IP. They should have taken charge and used their position to make both sizes play nice. In the end they're the ones that got screwed the most since it was their IP in the center of it all.
Some one at Warner Bros finally pulled their head out of their *** long enough to realize that a great comic book game can be made if you ignore Hollywood and let game devs do their job.
EPIC needs to wake up and implement some basic AA in their future engines.
From what I read, it sounded like AMD never sent their source code though. They argued that Nvidia should be the ones to fix the lock out problem since ATi hardware has run fine in the past with similar Nvidia structured code.
I'm not choosing sides here, but I think it was lazy of AMD for not sending their own code in the first place.
Like Tinman said, AMD needs to be more aggressive when working with devs. From the article, it sounds like AMD saw the graphic requirements description, and thought, "oh Nvidia will take care of that again".
I have to wonder if NV has the developers on some type of leash when it comes to titles that have been labeled TWIMTBP.
I think the leash varies from company to company and at the end of the day Nvidia is going to try to get way with as much as they can. It's up to the devs to watch Nvidia and keep them in check.
In the case of Batman:AA, it sounds like Edios left it up to Nvidia and ATI to do whatever they wanted to do. And thats what each company did.Quote:
Originally Posted by From the article
From what I saw Nvidia gives a lot to the game devs. Did you read that bit about them suppling the devs with high end graphics cards, systems, etc and the company was only a start up. I don't really blame Nvidia as much after reading all of that. I would be a bit peeved if ATi always let Nvidia work out the details and then they reap the benefits.
Like Taggart said, moral of the story:
Nvidia is getting pissed and doesn't want their work to contribute to Ati.
Ati needs to get with the game and work with the devs.
Epic should have implemented AA in the first place.