I think that you have, quite understandably got a big misconception about .map files. Let me try to explain...
How it used to work: 1. Make a .map file with an editor. 2. Compile it into a .bsp with some tools from id (bsp, rvis, rlight). 3. Play. How it now works: 1. Make a map in an editor that often uses it's own file format, thus allowing you to do some cool stuff that saves a lot of time when editing maps (such a grouping objects, negative brushes, etc), but is not supported by the .map format. 2. Convert it to .map with the editor. 3. Compile it with tools evolved from the ones id GPL'd 4. Play. You cannot go the other way 'round---i.e. it is not possible to convert a .bsp into a .map. You can find the .qkm files used to create the levels I made for AQ on our Subversion server ( http://agrip.org.uk/svn/trunk/audioquake/ ) and I think QuArK can convert them to .map files, but these are very low-level I'm afraid. You can also find on our subversion server the beginnings of a system I started to write that converts .map files into higher-level more abstract text-based data structures and back. Don't get excited though, it's nowhere near finished yet. It is at http://agrip.org.uk/svn/trunk/ldl/ if you're interested, though. I hope this helps! -- Matthew Tylee Atkinson <[EMAIL PROTECTED]> _______________________________________________ AGRIP-discuss mailing list [email protected] http://lists.agrip.org.uk/cgi-bin/mailman/listinfo/agrip-discuss
