Knowing that they couldn't match the 6800 they did this by disseption.
You're reading alot into that that you can't back up. Wanna prove it?
Optimizations are good in general for the end user.
As long as it's not Floptimizations like their initial run-time compiler usage/shader replacement, intial brilinear replacement, and partial precision. So far ATI has come into the optimization of AF at a point where the difference is minor. nV threw the floptimizations into the mix in raw form and didn't allow you to turn it off so it was a huge impact on users. Not the same thing by a long shot.
ATi too is using application detection, with colored mip maps thats why this is just as bad as Nvidia's first time at it.
Once again, PROOF? Application detection was initially mentioned and thought to be the cause of the mip differences, but since then that has be shown to not be the case, unlike FartCry, and the UT2K3 issue with the FX series where even AF testers renamed U2K3 shows brilinear optimizations because of the name change. Seriously you're making alot of accusations without much to back them up.
I think alot of people didn't expect ATi to do this in the manner they have.
That's the real issue here. The optimization isn't as bad as the way it was implemented. Even the issue about turning off nV's optimizations held true for the R9800series, but not for the X800. Both of those lead to the majority of the informed anger.
Even worse they give "special treatment" to game developers to specifically optimize for thier cards. Which is absolutely wrong.
That's not limited to either company. If anything nV does more of that with thei TWIMTBP program which actually penalizes non-nv users, like in EA's TigerWoods.
The other optmizations that ATI and Nvdia have been doing are well documented why not this one?
Well the documentation isn't coming from nV it's coming from those who discover nV's optimisations. You show me where their brilinear and run-time compiler optimizastions are 'well documented' in NV's actual literature. This one is no different. The reason why it's note worthy is becuse ATI doesn't have the same history of slippingin optimizations that might be questionable. Perhaps that's why hey didn't mention it, they didn't think it was questionable, since it did have minimal impact on IQ (it does impact, but the level is much lower than previous floptimizations). The main problem is that ATI has always said they wouldn't affect IQ, they didn't qualify that with, we won't affect IQ more than 99%, so this is something that definitely goes against the openess they profess, and that's what people are most Pi$$ed at IMO.
Funny there's nothing new in Lars' article, but suddenly it's a hot topic again here.
Oh well, still nowhere near FartCry, but I guess people have been looking for something to hang ATI with. As for the list of optimisations, I find it funny that the list is restricted to AF alone, I guess you want to keep the issue on AF, but since LARS mentions optimisations, it would be nice to include the entire list not just those in AF. But funny he didn't include nV's application detection for UT2k3, which is only for nV. Guess that was OLD news whereas this has 'never' been covered. :lol:
- You need a licence to buy a gun, but they'll sell anyone a stamp <i>(or internet account)</i> ! - <font color=green>RED </font color=green> <font color=red> GREEN</font color=red> GA to SK