Links: | Thanks Ant and Acleacius. |
Play: |
Royal
Offense 2. Tower Droids. |
Link: | Susannah Mushatt Jones shares secrets to a long life. Thanks Boing Boing. |
Stories: |
Want to buy your own airship: Get your orders in now. Thanks
Skullguise. Former 'Star Wars' actor arrested after chase. Pod-racing skills rusty. |
Science: | Access to electricity linked with reduced sleep. Thanks HARDOCP. |
Images: | Brace yourselves for the Steam Summer Sale. |
Media: |
OUTLAST:
WHISTLEBLOWER - PART 2 (React- Gaming). Best Fails of the Week 3 June 2015. Ouch. Thanks nin. Flying Kitty Surprise. Maybe scarier than yesterday's weightlifter. |
The Funnies: | Dilbert Comic Strip. |
More From John Carmack on D3D Quake
I got an email from John Carmack that cleared up a misconception that I had (and I would guess others had too), which was that Direct3D Quake would have been an option for owners of current 3D video cards:
D3D quake is indeed canned. But this should not have any impact on current 3D card owners.
The only current card that would have been fast enough to run D3Dquake is 3dfx, and they can run glquake.
Glquake is implemented with blended lighting instead of surface caching, which gives a more level framerate at the expense of pushing twice as many pixels. The low end cards (S3, ATI, etc) have less than a third of the fill rate of 3DFX on real world data, so they would have been hard pressed to hit 15 fps running glquake/d3dquake. Anyone with one of these cards that was holding out for the D3D version would have been very dissapointed.
A custom, on-the-metal port to these cards might have been able to give performance almost as good as vquake (verite has exceptional potential for optimization if you go to the trouble, which compensates somewhat for the reletively low fill rates), but I don't think it is worth it.
The next generation of most vendors cards should be fast enough to run glquake and derivitives. Tell them they should support OpenGL.
John Carmack