• Embed Doc
  • Copy Link
  • Readcast
  • Collections
  • 1
    CommentGo Back
Download
 
John Carmack Archive - .plan (2002)
http://www.team5150.com/~andrew/carmack
March 18, 2007
 
Contents
1 February 2
1.1 Last month I wrote the Radeon 8500 support for Doom.(Feb 11, 2002). . . . . . . . . . . . . . . . . . . . . . . . . . 2
2 March6
2.1 Mar 15, 2002. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 June7
3.1 The Matrox Parhelia Report (Jun 25, 2002). . . . . . . . . . 73.2 More graphics card notes (Jun 27, 2002). . . . . . . . . . . 81
 
Chapter1February 
1.1 Last month I wrote the Radeon 8500 sup-portforDoom. (Feb11,2002)
The bottom line is that it will be a fine card for the game, but the detailsare sort of interesting.I had a pre-production board before Siggraph last year, and we were dis-cussing the possibility of letting ATI show a Doom demo behind closeddoorsonit. Wewereallverybusyatthetime,butItookashotatbringing upsupportoveraweekend. Ihadn’tcodedanyofthesupportforthecus-tom ATI extensions yet, but I ran the game using only standard OpenGLcalls (this is not a supported path, because without bump mapping ev-erything looks horrible) to see how it would do. It didn’t even draw theconsole correctly, because they had driver bugs with texGen. I thoughtthe odds were very long against having all the new, untested extensions working properly, so I pushed off working on it until they had revved thedrivers a few more times.My judgment was colored by the experience of bringing up Doom ontheoriginal Radeon card a year earlier, which involved chasing a lot of driverbugs. Note that ATI was very responsive, working closely with me on it,andwewereabletogeteverythingresolved,butIstillhadnoexpectation2
of 00

Leave a Comment

You must be to leave a comment.
Submit
Characters: ...
11 / 27 / 2010<span class="translation_missing">en_US, this_document_made_it_onto_the</span>Rising List!
You must be to leave a comment.
Submit
Characters: ...