BSPTwoMap version 1.0b (December 31st, 2003)
by Skyler 'Zipster' York
--------------------------------------------

Description
-----------
The purpose of BSPTwoMap is to decompile a Half-Life BSP file into a MAP file viewable in Valve's Hammer editor.  The ultimate goal of this application is to produce something that can be easily recompilable (using Zoner's compile tools) into a working version of the map.  In addition, any textures that are stored in the BSP will be extracted into a custom WAD file created by the application.

Usage
-----
-notextures	Do not extract included textures
mapname		Name of the BSP to decompile

Current Version Notes
---------------------
At this early beta stage, the output produced by BSPTwoMap could hardly be considered something easily recompilable into BSP format.  As a matter of fact, it's highly unrecommened at this point.  However, the program produces output acceptable for viewing in Valve's Hammer editor, output magnitudes better than that of its predecessors (WinBSP for example).  A few of the recreated brushes may extrude slightly, however this is a known side effect and will hopefully be fixed in the next release or two.  Remember that no map will ever be 100% perfect, so you should always check it over before attempting to recompile, especially with more complex maps.

Currently, BSPTwoMap works well on some maps, and really poorly on other maps.  It worked well on 95% of the maps I tested it with, however on others it created a lot of invalid brushes.  During the early development stages, BSPTwoMap would also get stuck in an infinite loop on a small number of maps, however as I made bug fixes this behavior eventually disappeared altogether.  Yet as a precaution, if you notice BSPTwoMap taking a long time on a certain model, noteably the worldspawn (a long time would be in the range of 20 to 30 seconds), then close the application.  If the map file generated is in the ballpark of 50 megs or greater, then BSPTwoMap is unable to handle your map at this stage in its development.  However this behavior is extremely rare, and I was unable to reproduce it before this release.  For your reference, most MAP files produced will be under 20 megs, or in the range of 20 - 30 megs for larger, more complex maps.  Future versions will also hopefully reduce the filesize as more complex decompile methods are introduced.

Version History
---------------

Version 1.0b
December 31st, 2003	->	First release