I was thinking, and 16x FSAA is nearly impossible without a very noticable performance hit. what if Matrox actually created an antialiasing system that aliases the edges only? This would cause little performance hit and detail wouldn't suffer either...
Announcement
Collapse
No announcement yet.
Smart AA?
Collapse
X
-
p5ycho, don't worry, be happy.
Few topics ago I have put a provocative message about espionage. Later somebody with horryfying name 'Ant' told a horrible message about a clinic and crazy ones who chase for their tails with 'matrox' imprinted on walls. I got a hint, so I draw quickly such an avatar (anybody needs larger version?) and promote Perhelia further.
Seriously - I have a strange silence from major 3d hardware review sites (include russians ones, like ixbt.com) about forthcoming matrox product. It may be only because they have the card on their sticky hands and a plaster on a mouth (remember the clinic walls with bluish letters on it?).
Let's wait till official announcement and then we'll sneak out those who hide the card for maybe weeks and written notes greedily about the Card on serviettes.
-
I've always wondered why they did FSAA instead of just AA-ing the edges. I mean... the card does have the edges in memory since the it's edges that create a wireframe for the scene on screen, or am I totally wrong here? Or is it somehow harder to just AA-ing the edges rather than AA-ing the entire screen?KT7 Turbo Ltd. Ed. ; Athlon XP 1600+ @ 1470 MHz (140*10.5); 512MB Apacer SDRAM ; G400 MAX ; Iiyama VM Pro410
Comment
-
Well done (eg. 16x) edge antialiasing combined with trilinear filtering and 64tap anisotropic should do the trick. And if you had a good algorithm to really only smooth the edges, this should not give major speed-drops...
Comment
-
Originally posted by Indiana
Well done (eg. 16x) edge antialiasing combined with trilinear filtering and 64tap anisotropic should do the trick. And if you had a good algorithm to really only smooth the edges, this should not give major speed-drops...KT7 Turbo Ltd. Ed. ; Athlon XP 1600+ @ 1470 MHz (140*10.5); 512MB Apacer SDRAM ; G400 MAX ; Iiyama VM Pro410
Comment
-
how much video-ram would 8xfsaa in 1024*768*32 + triplebuffer and 32bit z-buffer require?
i don´t know if you can calculate it like this, but i will try:
8*1024*768*4*4 + 3*1024*768*4 = 11010042 bytes
----z-buffer----- + --triplebuffer--
asuming the triplebuffer contains the downsampled output.
thats about 110 Mb and thats without textures or geometry.
seems high to me, or did i calculate it the wrong way?
maybe 8xfsaa in hires, is for the 256mb version only...
if these numbers are correct, then we can rule out 16xfsaa completely.
Btw why do people talk about 8xfsaa, wouldn´t 9xfsaa make more sense? 9xfsaa@1024*768 = (3*1024) * (3*768) = 3072*2304.Last edited by TdB; 10 May 2002, 11:24.This sig is a shameless atempt to make my post look bigger.
Comment
-
Yeah....
They should put on some safety goggles before reading the Parhelia specs. That way they won't have to pick their eyes up off the floor
Dr. MordridDr. Mordrid
----------------------------
An elephant is a mouse built to government specifications.
I carry a gun because I can't throw a rock 1,250 fps
Comment
Comment