http://www.xbitlabs.com/articles/video/display/geforce-fx.html
I haven't seen this posted in B3D before - so apologies if its old news.
I haven't seen this posted in B3D before - so apologies if its old news.
We guess the 42.68 driver is specially optimized for 3DMark03. When the driver meets “familiar†code of pixel and vertex shaders from 3DMark03, it probably substitutes it with another code producing the same visual effect, but running faster on GeForce FX. Or it may use lower precision of calculations in pixel shaders.
I have to disagree with you here. From http://www.xbitlabs.com/articles/video/display/geforce-fx_9.htmldemalion said:The vertex shader discussion seems to be quite a bit less distorted, but my thought is that is because the GF FX really does have demonstrated vertex processing advantages.
AFAIK "performance" aniso is using bi-linear filtering only.demalion said:It even reads as if they don't know what the difference between "Performance" and "Quality" aniso is for the R300.
chavvdarrr said:AFAIK "performance" aniso is using bi-linear filtering only.demalion said:It even reads as if they don't know what the difference between "Performance" and "Quality" aniso is for the R300.
Am I right?
In same time FX's "aggresive" although using really 'aggresive' aniso&trilinear combination (limited to mip-map boundary), does use trilinear. And IMHO 8xAgg gives better quality than 16xP - judging from seen shots of course.
chavvdarrr said:AFAIK "performance" aniso is using bi-linear filtering only.demalion said:It even reads as if they don't know what the difference between "Performance" and "Quality" aniso is for the R300.
Am I right?
In same time FX's "aggresive" although using really 'aggresive' aniso&trilinear combination (limited to mip-map boundary), does use trilinear. And IMHO 8xAgg gives better quality than 16xP - judging from seen shots of course.