Herr Otto Partz says you're all nothing but pipsqueaks!
Started by Cyberman, July 23, 2004, 08:15:12 PM
Quote from: Duplode on April 01, 2008, 03:31:52 AMdstien will find specially amusing the fact it is written in Fortran...
Quote from: Duplode on April 01, 2008, 03:31:52 AMAnd before I forget, nice find about the helmet, when we find what escape code produces the circular taillights it will be a neat addition.
Quote from: Duplode on April 01, 2008, 03:31:52 AMThose corrections mean that now we only have the mysterious "UNKNOWN" middle section to understand. Actually, I did some brute force tests while writing the parser (e.g. blanking the whole thing), and it seems that the "UNKNOWN" section has actually two parts, one with five-byte blocks and the other with three-byte blocks. The first part might have some relation with angles of visualization - for instance, wheels have "ff ff ff ff ff" sequences, and blanking some (don't remember which) values will make them disappear, while arbitrary changes might make them go on and off as the car0 structure rotates in the selection screen. As for the second part, still no clue on what it stores.
Quote from: Duplode on April 01, 2008, 03:31:52 AMNow, on where we go from now... first thing I wish to do is to print better polygon maps, so it is feasible freely colorize a car. Also, I wonder about editors. One of the motivations behind the creation of the ASCII parser was to use it as an intermediate tool for feasible edition. I can think of two routes:Decompose the .3SH in tables of vertexes, colours, polygons and whatever else is needed, modify the intermediate as wished and re-package everything on a new .3SH with another program. That could be useful, for instance, in providing a comfortable way to tune colours without having to worry all the time about offsets - but more important would be the role of such process in the other treatment......namely, use a new parser to convert the essentials (vertex and polygons at least) data in a format that can be read by an actual 3D editor, then use another program to rebuild the .3SH. While that may sound unfeasible at first, there's a damn simple and common 3D shape format that uses tables very similar to what we already have to code polygonal shapes: the .OBJ format.For the moment, though, I'm merely speculating. Surely dstein knows a lot more about 3D shape edition than me (for I would have found nothing without his guidance), and is a more experienced programmer as well (he doesn't have to write his parsers in Fortran ), so he can have a more proper opinion in that respect.
Quote from: dstien on April 04, 2008, 12:55:25 AMQuote from: Duplode on April 01, 2008, 03:31:52 AMdstien will find specially amusing the fact it is written in Fortran...Hehe, I do find your choice of languages -- Fortran and R -- a little, um, esoteric.
Quote from: dstien on April 04, 2008, 12:55:25 AMI plan on making a resource editor with low-level editing and import/export of 3d mesh data...
Quote from: Duplode on April 05, 2008, 12:38:01 AMyou may be sure beta testers won't be lacking!
svn co http://stuntstools.googlecode.com/svn/trunk/stressed/ stressedcd stressedqmake stressed.promakesrc/stressed /path/to/MISC.PRE
Quote from: Duplode on April 05, 2008, 12:38:01 AMBTW, before I forget, dstein: are you reading the colour data while generating that shape pics for the file from somewhere?
Quote from: dstien on April 20, 2008, 04:37:18 AMJust added bitmap import/export. When will we see the first custom dashboard?