Quote:
Originally Posted by gstanford
The thing is you can't have 32xAA unless you are using 32xS (big performance hit but top notch IQ providing the application will run in that mode - some won't go past 16xS) or SLIAA. nvidia's standard control panel AA modes top out at 16xQ.
I guess I'm just pretty sensitive to aliasing and shimmering.
Speaking of which ChrisRay, you might like to ask the nvidia driver team when they are going to get around to fixing the aliasing on the battlecruiser at the start of the 3dmark05/06 demos (pics attached, see "saw teeth" on horizontal edges under hangar opening). This has never been addressed and looks butt ugly (horrendous in motion). Of course it could be a futuremark modeling error, I'm not sure.
http://img19.imageshack.us/img19/983...board01kxg.jpg
http://img19.imageshack.us/img19/514/clipboard02jzc.jpg |
Actually. SLI 64xQ is 32x multisampling. Its 32x multisampling, 32x Coverage Sampling, ((and a very weakly positioned 2x2 Supersampling)). ((8x8x8x8x)) + CSAA 8x8x8x8x
I'll look into the 3dmark thing. I dont have any comments because I'm not familiar with the problem. 32xS "working" is entirely dependent on whether the driver detects the available memory amount. Say you may find that 32xS will work on a 512 card at 800x600 but will revert back to 16xS at 1024x768. Its a driver fail safe thing. 32xS can be used in some games like World of Warcraft with Quad GTX 295 and net about an AVG of 45-50 FPS typically at 1680x1050.