DarkMatter
New Member
- Joined
- Oct 5, 2007
- Messages
- 1,714 (0.28/day)
| Processor | Intel C2Q Q6600 @ Stock (for now) |
|---|---|
| Motherboard | Asus P5Q-E |
| Cooling | Proc: Scythe Mine, Graphics: Zalman VF900 Cu |
| Memory | 4 GB (2x2GB) DDR2 Corsair Dominator 1066Mhz 5-5-5-15 |
| Video Card(s) | GigaByte 8800GT Stock Clocks: 700Mhz Core, 1700 Shader, 1940 Memory |
| Storage | 74 GB WD Raptor 10000rpm, 2x250 GB Seagate Raid 0 |
| Display(s) | HP p1130, 21" Trinitron |
| Case | Antec p180 |
| Audio Device(s) | Creative X-Fi PLatinum |
| Power Supply | 700W FSP Group 85% Efficiency |
| Software | Windows XP |
Those are not the names of the cards, but the codenames of the chips. Just like G92 > G94 > G96 > G98. OR G71 > G73. NV40 > NV43.
It's been always like that and IMO it just has to do with the number of the project that was chosen to continue into production. Pretty much like with US fighters, the F-22 could have been the F-21 if that was the project that'd won between the two. And maybe I'm mistaken but the F-15 and the F-16 projects started at the same time and F-15 > F-16.
In the case of GPU tesselation and the one that Ati has right now is just SUBDIVISION, that is subdivide the polygons into more polygons. It has nothing to do with textures nor with repeating paterns, etc.
It does not really save computing power either, at pure rendering end I mean, because resulting triangles have to be calculated, textured, lit, etc. It does save a lot of memory, something that could make data transfers easier. And it definately makes animation easier: as long as you have enough vertex to make detailed animations, the less vertex the better, so that's something that is potentially keeping game models at "relatively low" poly count. The idea behind using tesselation is to have 20.000-50.000 poly models and make them look as if they had 100.000++ or millions of them. No more spikes in the heads.
Tesselation could essentially be used to make models LESS detailed too and get rid of LOD models, something that could be very useful too.
The end goal is to have models that vary on detail depending on the distance or simply the power of the GPU or the settings you use, without the need of LODs and the jumps between them that are so apparent sometimes.
In any case the simple use of tesselation has like a constant performance penalty, much like DX10 has, but more pronounce probably, so the use of it in current games is questionable. See it as phone contracts with a high constant component and a small price per spoken minute. They are not good unless you will speak a lot AND you can pay that much. Current GPUs probably can't "pay" as much still.
EDIT: Oh and on-topic I don't take that chart seriously. That roadmap is VERY different from other expectations/rumors and suggested roadmaps and without any proof to make a decision, which one is to believe...
Last edited:
