Originally posted by: VIAN
*UPDATED 3/6/05
This thread is to prove that ATI has better default IQ than Nvidia (although that's not happening right now with no ATI pics) resulting in unfair benchmarking with Anisotropic Filtering enabled. And if that's not good for ya, it's also a challenge to
this.
Nvidia states the difference between Quality and High Quality in this 10MB
pdf:
Quality is the default setting that results in optimal image quality for your applications
High Quality results in the best image quality for your applications. This setting is not necessary for average users who run game applications. It is designed for more advanced users to generate images that do not take advantage of the programming capability of the texture filtering hardware.
Accompanied by a graph that looks like
this.
There is and there isn't a difference between those settings, and any difference will be much more noticeable when you are in motion. If you don't enable Anisotropic Filtering, you will see no difference. Although there might be some subtle differences in certain situations like what I've seen in Call of Duty in the Ship level in mutlitplayer, differences like these are hard to spot. In this level you will notice it from a distance with the shadow of the railing of the ship.
If you turn on Anisotropic Filtering however, you will be able to see it on only certain types of textures. Sometimes you won't be able to see it at all, sometimes you'll be able to see it a bit in motion, and sometimes it will stick out like a black eye. Take COD for instance. The textures on the wall are nice, but never as defined as when there is are patterns on the floor. With Quality enabled you will notice artifacts that look like a crap load of texture aliasing a.k.a. texture shimmering with those patterns. It'll be visible in the pictures below(only on the patterned part). I'm pretty sure ATI doesn't have this problem as I never noticed it playin COD before. Also noticeable on the floorboards on the ship level. Painfully noticeable. If you follow the floorboards, you don't see anything, but as soon as you look at them diagnally or horizontally, then you have a serious problem.
Even at High Quality, there is just something weird about those textures that I noticed coming from an ATI card. For starters, not always does HQ do Trilinear - You may have to force it.
Being that Quality is default, benchmark numbers reflect this loss in Image Quality when they bench with Anisotropic Filtering, which is unfair to the competition that uses optimizations with NO Image Quality loss.
Quality.JPG VS
High_Quality.JPG
In the High Quality picture above, you will see that near the wall, there is a bilinear transition there. Trilinear is set however in the game.
Quality_2.JPG VS
High_Quality_2.JPG
Again in the High Quality pictures you are able to see some bilinear transitions, one is a bit farther than the lower, farther corner of the door.
If you are one of those dudes that was complaining about the second set not being in the same position. Here you go:
Q.JPG VS HQ.JPG
Although, these are using the 71.84 BETA drivers. There was an addition feature in 71.84 named Negative LOD BIAS, this was changed from default to Clamp.
If anyone can oppose that ATI has better default driver image quality with 8x Anisotropic Filtering enabled in an ATI pic, that would be great since I don't have an ATI card. But I'm looking into buying a cheap 9600 to prove this, but I don't know how long that will take.
SPECS
Athlon XP 2700
1GB Corsair Value Select PC2700
A7N8X-X
eVGA 6600GT - Forceware 66.93
Other than changing Image Settings in the drivers, Vsync was off and Anisotropic Filtering was set to 8x. Everything else left at default.
For Optimal Image Quality using drivers 71.84 without Anisotropic Filtering leave drivers at default settings. If you want Anisotropic Filtering, change the following:
Image Settings: High Quality
Force Mipmaps: Trilinear
Negative LOD BIAS: Clamp
PICS IN OTHER GAMES
HL2Q.JPG VS
HL2HQ.JPG - Highest Settings, no Vsync
FarCryQ.JPG VS
FarCryHQ.JPG - High Settings, AF set in driver, no Vsync