Well, I don't have to expound on how much I wish that ioq3 updated its 10-year-old rendering tech to, say, 7-year-old rendering tech, so I'll keep this short. I decided that for there to be any movement on this at all from any interested parties, there had to be a starting point for commenting. With that in mind, I present:
http://wiki.ioquake3.org/Modular_Rendering_System You can scroll to the bottom for the quick-and-dirty summary. Please bear in mind that this is written from someone without a working knowledge of the quake 3 codebase. In fact, I would extremely love to have people with that knowledge take a look at see what parts seem feasible or practical or even possible! And at the very least this will be a reference point for others to look at and say "ok this idea has merit" or "what was he smoking when he came up with THAT?" And hell, if this gets hashed out well enough, even if there are no interested parties at present who want to implement it, it should make any future attempts at implementation easier for whoever wants to try tackling it. So please, constructive comments, discussion, etc. This is pretty much as far as my skillset will allow me to contribute to this idea/effort so instead of lamenting the lack of these features I figured I'd at least do what I could to make implementation easier for others. Thanks for your time! Monk. _______________________________________________ ioquake3 mailing list [email protected] http://lists.ioquake.org/listinfo.cgi/ioquake3-ioquake.org By sending this message I agree to love ioquake3 and libsdl.
