And while I'm pestering all and sundry about the guts of Marathon, another question: has anyone written a good de_script_ion of the format of a Marathon (1, in particular) map file? There are some things I'd like to do with them, but I couldn't find the right kind of info. It seems I've forgotten what corners to poke in since the last time I was really into Marathon... *sigh* Thanks in advance, -= Sixten =-

And while I'm pestering all and sundry about the guts of Marathon, another question: has anyone written a good de_script_ion of the format of a Marathon (1, in particular) map file? There are some things I'd like to do with them, but I couldn't find the right kind of info. It seems I've forgotten what corners to poke in since the last time I was really into Marathon... *sigh* You can get it from the Hyperarchive... M2_MapSpecs Note that this is just the C header files - there is enough info in there to read a map file, but you'll have to write the reader. I have a Pascal translation of these files if that is more useful to you.

You can get it from the Hyperarchive... M2_MapSpecs Note that this is just the C header files - there is enough info in there to read a map file, but you'll have to write the reader. I have a Pascal translation of these files if that is more useful to you. Thanks! Actually, C is much more useful to me, so this should be just great as-is. But let me ask one more stupid question: aside from things like the the details of the shapes file, and the ids of various things, are the M2/I map format and the M1 map format the same? In other words, can I trust this to parse maps from the original Marathon? -= Sixten =-

Thanks! Actually, C is much more useful to me, so this should be just great as-is. But let me ask one more stupid question: aside from things like the the details of the shapes file, and the ids of various things, are the M2/I map format and the M1 map format the same? In other words, can I trust this to parse maps from the original Marathon? To be honest, I can't remember. It is a long time since I touched an M1 map. You could try it... Someone help us here Looking at the source code for Chisel (which I didn't write, but have now modified in the interface department), it makes no distinction, but then again I don't think it was ever intended to work with M1 maps. What I seem to remember is that the overall structure is the same, but the chunks themselves are different - ie they store different data. (of course, PNTS, EPNT, LINS chunks are pretty much the same, but POLY certainly changed a bit.) later, MikeT

And while I'm pestering all and sundry about the guts of Marathon, another question: has anyone written a good de_script_ion of the format of a Marathon (1, in particular) map file? There are some things I'd like to do with them, but I couldn't find the right kind of info.         One can download some code that reads Marathon 2/oo map files in my Marathon Map Exporter

I have a Pascal translation of these files if that is more useful to you. Thanks! Actually, C is much more useful to me, so this should be just great as-is. ...         My Map Exporter uses C++, and is rather heavy on templates and inheritance. I implement all the individual exporters as subclasses of a generic exporter class, and I've created template classes for memory-allocation wrappers (their destructors do all the deallocation necessary).         Has anyone here thought my source code worth trying to read?