why all the SLI & AA issues?

S

ShortyDammit

Guest
I'm confused as to why nvidia seems to have so many issues with SLI and AA, why some games work fine and others do not. How come 3dfx could make SLI and AA work in EVERY game, without the game even knowing either were active, nor did they care if it was active or not. You turned it on in the drivers, and the drivers & card did what they were told. Absolutely no game support was needed. It just worked. And nvidia bought all of 3dfx's technology. So, why can't their stuff just work? There's absolutely no reason for you to be denied AA because of how a game was written. "You can't use AA in Halo because it renders this feature in this manner." BS, it shouldn't matter what or how you render. Turning on AA should do nothing more than tell the card to render more than once and average those extra frames into the final frame. It worked just great for voodoo cards. No reason it can't work exactly the same, and just as well, for nvidia and ati cards. All without the game ever having to know it's even happening, because it's irrelevant to the game. It's something the card does after the rendering instructions. Whatever you render is immaterial. Want 4x AA, render it 4x, and average the four frames. Done. Yes, I know that would be "slow" to do. Because you actually quadruple the workload. Guess what? Cards are more than fast enough to do so. So that argument doesn't apply. When you've got an 8800 capable of hundreds of frames per second in pretty much every game you care to throw at it in something like 1024x768, would you really care if rendering each frame four times dropped your framerate down to the 75 fps range? When you'd get absolutely gorgeous AA, with 100% compatibility with every single game in existence without fail? 3dfx's marketing department certainly killed the company. But that voodoo5 still has better AA than every single card available today. And that's hilarious.
 
Please, if you want a good answer and not to cause huge migrene for readers, add some spaces to your text.

As for the post, a legit question. Would like to know the answer too :)
 
Please, if you want a good answer and not to cause huge migrene for readers, add some spaces to your text.

As for the post, a legit question. Would like to know the answer too :)

I agree. i read the first two lines, then skipped down to this post

edit: spelling ftw
 
1998 games != 2006/7 game ?

I only read your thread title and a few lines...(next time put long rant in the title k thx)
 
That's also my point. The game and type of rendering it does is irrelevant. Or should be, if you're actually doing things correctly. Don't be so lazy.
1998 games != 2006/7 game ?

I only read your thread title and a few lines...(next time put long rant in the title k thx)
 
So after reading the rest of your post, you could of just said...

3dFX's AA/SLI was game independant, it worked for all games. Nvidia bought 3dFX. Presently there are games with AA/SLI issues. What has changed?

amirite?

I dont make game engines or video cards so I dont know, but I see your point.
 
I just don't see any reason, other than nvidia just not wanting to do so, that any and every game should work just fine with SLI/AA without there ever being a case where one wouldn't. If they did their hardware and drivers correctly, the game would never be an issue, no matter what game or what the game's engine does. SLI/AA should be, and could be, completely isolated from anything the game does. They own the tech that shows how 3dfx did it. And they could do it that way if they chose to. But they'd rather not, for whatever reasons they have. I can imagine some of the reasons, at least the most prominent one being that it is such a performance sapper in the case of AA. But, with so much extra performance on tap, it would seem to be about time they considered using the tried-and-true method, since it would work just fine. Oh well.
 
damn people, either answer his question or move on. If you don't want to read his whole post, move on, no need to comment on it.

Anyway shorty, did you by chance read something I posted within the last week to spark this? Seems awful similar to something I said.

What I DIDN'T say in my post though was that there are DIFFERENT ways to anti-alias. I don't know all the different ways to do it, but when I was a 3dfx fanboy (and stock owner - doh!), their way was clearly superior to the way nvidia and/or ATI was doing it. Now I don't know if nvidia adopted 3dfx's method or not. I would guess Yes because they bought 3dfx, but I don't know for sure. And I think 3dfx's method relied heavily on SLI simply because SLI allowed the screen to be rendered multiple times without a significant frame rate hit. I do remember nvidia's implementation being inferior though.

But IF nvidia adopted 3dfx's method, and IF it's somehow related to SLI, then perhaps it's a chipset problem (i.e, Intel chipsets) since Intel chipsets were the reason 3dfx couldn't come out with their Voodoo 6000? It's been a looooooong time since I've fought this battle, so I could be mistaken.
 
If you'll recall, they had their T-Buffer that was used for lots of different things, AA being one of them. For 4xAA they rendered the scene, exactly the same scene, four seperate times with the origins jitterred slightly for each instance, so that each instance was just slightly different. (sub-pixel) And then averaged those four into the final frame. Nvidia and ATI do not do anything like that. It's too costly, performance-wise. But with performance steadily getting crazier and crazier, that should no longer be an issue. Perhaps one day it will be done correctly again, but for now it is not.

edit - the Beyond3D pdf at the bottom of this page states the differences, and this *still* applies to this day to some degree. Nvidia (and ATI) don't do anything like the FSAA that 3dfx did. It's interesting to read this doc again after all these years.

http://digilander.libero.it/F1Land/3dfxarchive/develop/tech/antialiasing.html
 
Back
Top