README.TXT 6.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173
  1. Legal Stuff:
  2. THE COMPUTER CODE CONTAINED HEREIN IS THE SOLE PROPERTY OF PARALLAX
  3. SOFTWARE CORPORATION ("PARALLAX"). PARALLAX, IN DISTRIBUTING THE CODE TO
  4. END-USERS, AND SUBJECT TO ALL OF THE TERMS AND CONDITIONS HEREIN, GRANTS A
  5. ROYALTY-FREE, PERPETUAL LICENSE TO SUCH END-USERS FOR USE BY SUCH END-USERS
  6. IN USING, DISPLAYING, AND CREATING DERIVATIVE WORKS THEREOF, SO LONG AS
  7. SUCH USE, DISPLAY OR CREATION IS FOR NON-COMMERCIAL, ROYALTY OR REVENUE
  8. FREE PURPOSES. IN NO EVENT SHALL THE END-USER USE THE COMPUTER CODE
  9. CONTAINED HEREIN FOR REVENUE-BEARING PURPOSES. THE END-USER UNDERSTANDS
  10. AND AGREES TO THE TERMS HEREIN AND ACCEPTS THE SAME BY USE OF THIS FILE.
  11. COPYRIGHT 1993-1998 PARALLAX SOFTWARE CORPORATION. ALL RIGHTS RESERVED.
  12. We make no warranties as to the usability or correctness of this code.
  13. About the Source Code:
  14. Included is almost all the source code to Descent 1, ver. 1.5. We removed
  15. all code to which we did not own the copyright. This mainly involved low-
  16. level sound and modem code.
  17. Kevin Bentley, maintainer of the Descent Developer Resources and author of
  18. Kahn, has agreed to support this code base through his website at
  19. www.ladder.org/ddr. If you have questions or comments about the code, please
  20. go there. Please do not contact Parallax Software, its employees or its
  21. affiliates.
  22. The following tools were used in the development of Descent:
  23. Watcom C/C++, version 9.5
  24. Microsoft Macro Assembler, version 6.1x
  25. Opus Make, version 6.01
  26. Have fun with the code!
  27. Parallax Software Corporation
  28. Jan. 12, 1998
  29. Kevin Bentley's notes:
  30. As included in this zip file, the source should compile and run with the
  31. following:
  32. Watcom 10.6
  33. Miscrosoft Macro Assembler 6.11
  34. GNU (or compatible, such as Microsoft, or Borland) Make utility
  35. To build the executable, you should be able to just run maked1.bat.
  36. Descentr.exe should be built in the main subdirectory.
  37. When you unzip the archive, make sure you use the -d option to expand subdirectories, or it will not
  38. compile.
  39. The compiled code will run fine with no sound, and no serial port functionality
  40. (This means no VR equipment that uses serial interfaces, and no modem or serial
  41. play games.)
  42. If you port this to another platform, please drop me a note
  43. kevinb@stargatenetworks.com , I would be happy to post a copy of your port on
  44. the web site. *PLEASE* make an attempt to keep the existing code compilable (ie.
  45. use #IFDEFS)), so other people can benefit from your work.
  46. To build the editor, change the CCFLAGS variable in all the makefiles to
  47. "CCFLAGS = /dNETWORK /dEDITOR" and rebuild all files. You will need the files
  48. in editdata.zip (included in this archive) to run the editor. Also, I was only
  49. able to get the editor to run using the -nobm command line arguement.
  50. ---
  51. Interview with Matt Toschlog and Mike Kulas regarding the release of the
  52. Descent source code:
  53. Q: Why are you releasing the source code?
  54. Mike: The main reason is we figured a lot of people aspiring to work in the
  55. game industry would like to see production "quality" code. There are two
  56. reasons for this. One, you can learn a lot by looking at working code.
  57. Two, people will see that you can write a decent game without writing
  58. beautiful code.
  59. Matt: That's a good thing?
  60. Mike: Not really, except that it might make people think writing production
  61. quality code isn't that hard.
  62. Matt: That's a good thing?
  63. Mike: Well, not really, unless they learn that they have to focus on
  64. designing a brilliant game, rather than writing brilliant code.
  65. Matt: Ah, that's a good thing.
  66. Mike: Yeah, I don't think I understood that until we started working on
  67. Descent. At first all I cared about was writing technically good code.
  68. Matt: Then we ran out of money and all we cared about was finishing our game.
  69. Mike: Right. Our code got ugly, but our game got done.
  70. Matt: Writing code is easy. Finishing is hard.
  71. Q: Is there any code you're particularly proud of?
  72. Matt: No.
  73. Mike: No.
  74. Matt: I'm most ashamed of the vector intersection code.
  75. Mike: Yeah, that's pretty bad.
  76. Matt: Mike's AI code is the worst I've ever seen.
  77. Mike: Only because you program with your eyes closed.
  78. Matt: I'm proud we managed to finish without going bankrupt.
  79. Mike: Yeah, finishing is all. Who said that?
  80. Q: Seriously, what should people look at?
  81. Matt: I really don't know. It's not like there's a lot of reusable code in
  82. there. Some low level stuff could probably be used. The vector-matrix
  83. library is probably fairly instructive.
  84. Mike: The AI is an example of how not to write an AI system.
  85. Matt: You're doing it the same way in FreeSpace, right?
  86. Mike: Yeah.
  87. Matt: The texture mapper is worth looking at, not that you'll be needing a
  88. software texture mapper much longer.
  89. Q: You're including the editor, right?
  90. Mike: Yeah, people will be able to use our editor. On the whole, I doubt
  91. it's any better than DMB2. And it doesn't run under Windows.
  92. Q: What enhancements do you hope to see people make?
  93. Matt: If an aftermarket sprouts for it, we'd be very happy. People ask for
  94. lots of little features that we just don't have the time to add.
  95. Mike: People could probably roll in some of the D2 multiplayer features
  96. without too much difficulty.
  97. Matt: I don't think we can guess what people will do. We had no idea how
  98. much would be done with third party levels.
  99. Q: The license states that people can't use the code for commercial gain.
  100. What if some kid develops something and wants to recoup some of the cost
  101. through shareware?
  102. Mike: We're not opposed to that in principle. They need to get written
  103. permission from us, though. And, it would have to be after the thing is
  104. done so we know what we're permitting to be commercialized, if you want to
  105. call it that.
  106. Q: Any plans to release the D2 source code?
  107. Matt: No definite plans. Though, I guess I don't see why all our source
  108. code wouldn't eventually get released.
  109. Mike: Me, too. It loses commercial value in just a few years. And,
  110. releasing it brings us closer to our customers, which is a very good thing
  111. to do.
  112. Q: Any final comments?
  113. Mike: Yeah, have fun with the code.