WaltC said:
Well, to be synchronized they have to take the same amount of time...
That wasn't what I was talking about specifically. I was talking about the penalty incurred by the synchronization.
Synchronization means that the card that's first to finish has to wait for the other one. Load balancing reduces this wait time to almost nothing. There is no other significant penalty for the sync.
As well, how is it distiguished as to which is better, AFR or split-frame rendering?
The user can choose which one to use, or leave the decision to the driver, which I guess would prefer AFR until it recognizes some operations that make AFR inefficient.
It's been so long that I cannot recall precisely, but it seems to me a single V2 could do 1024x768, max. I'm pretty sure that V2 SLI could do up to 16x12, but can't recall precisely. My V3 could 2048x1536 with 16mbs ram ROOB, although of course it was very slow...
I have a pretty detailed document from 3dfx here stating that the max resolution for a single V2 is 800x600. The reason is that one buffer wasn't allowed to straddle a 1MiB boundary. 800x600x16bit is just slightly less than 1MiB
With 3dfx SLI two odd-even scanline fields of 800x600 combined is certainly a 1600x1200 final resolution frame. In 3dfx SLI each gpu renders every other scanline. They never render the same ones, and so obviously I don't know what you mean about "2x 800x600."
1600x1200 is four times 800x600, not two times.
V2 SLI running 1024x768 meant each card does 1024x384.
But IIRC "NvSLI" allows you to drive a dual (or even quad) display system rendering one 3D scene, both at their resolution limit. There you have the increased resolution.
Which is not like 3dfx SLI at all, which was my point.
Effectively, it is the same.
The point was it's redendant on your nVSLI purchase, unlike with 3dfx SLI, where it not only wasn't redundant, it didn't exist.
That redundancy is pretty insignificant. Using multiple displays, there is no redundancy at all.