Sounds like that production was final
And everything I said was right it seems. Thanks, source!
Well, yes, this is not usual. But you've got to remember that the NV30 was badly delayed, but other projects were being done in parallel. So I'd guess that if the NV30 would have had no delays and have been in stores for October or November, the NV30GL would have only been released around December or January.
16X FSAA sounds very nice. The Wildcat, AFAIK, is able to do 16X Line AA but only 4X FSAA. So nVidia got a nice advantage there. Even though it's unlikely you'll get 25 FPS for anything if using that mode...
256MB is indeed a standard for workstation.
There's something I really don't understand however:
Featuring three parallel vertex engines with the industry’s first on-chip vertex cache
Does that mean VS is not done in the same way as on the NV30? That could mean that's one of the cut downs going in the NV31/NV34. Does that mean no dynamic branching perhaps? Or signficantly worse dynamic branching perhaps...
Also, what the heck is a on-chip vertex cache in this case?
Uttar
EDIT: Just wanted to add that having 16X FSAA support got *nothing* to do with having 256MB of RAM. Some Wildcats got 256MB, some even 384MB, and can only do 4X FSAA ( and 16X Line AA, as I said earlier )
