!!!      !!!
***************************************************************************

Actors Static Lite v0.93

1) DESCRIPTION
   With this tool you can view edit and create actors.static files
   for Il2. The program works best with Il2 Mission Builder.
   It works in two modes: extract and create.
   But first about the contents of a typical actors.static file
   1.1) Contents of actors.static
        - information about bridges
        - information about takeoff points (an icon shown as airfield
                in Mission builder)
        - information about buildings and plates
        - information about runway points (not airfields)
        - information about taxi points
        - information about parking points
        The last three are probably used to navigate the AI over the
        airfield.
2) USAGE
   There are two commands than can be passed to this tool:
   2.1) java -jar Act.jar extract <filename>
        With this command the tool creates a number of out*.txt files
        in format suitable for inserting in the mission files that
        Il2 Mission Builder can read. More on that later. <filename>
        is the actual name of 'actors.static' file.
   2.2) java -jar Act.jar create
        With this command you create your 'actors.static' file named
        surprisingly MWactors.static. This file is ready to be used
        with your modified map and you can rename it as you wish.
        This option is the most time consuming by far. I might try to
        improve it's efficiency in the future versions. For Finland
        Gulf time to recode was around 15 min. That bastard has more
        than 600.000 'buildings' objects!
3) out*.txt files
   When you use extract command (see 2.1) the tool will create 5
   out*.txt files.
   3.1) outWing.txt
        In this file the information about bridges is stored. You can
        copy this into the mission file and load it with Mission
        Builder. You will see a A_20C flight path indiciating starting
        and ending points of all type 32 bridges. A_20G indicate
        type 64 bridges and B_17D type 128 bridges.
        Type 32 is a country bridge, 64 is ??? bridge and 128 is ???
        bridge.
        You can copy this file as a section in mission file for
        Mission Builder.
   3.2) outNStationary.txt
        In this file vehicles.planes.Plane$BI_1 is used to indicate
        takeoff points. Again, you can just copy this section to your
        mission file.
   3.3) outBuildings.txt
        This is typically the largest file. It is a direct replica of
        positions and buildings/plates types stored in 'actors.static'.
        Copy and load applies here as well.
   3.4) outChiefs.txt & outChiefsRoad.txt
        Within those two files info on runway, taxi and parking points
        are stored.
        3.4.1) Runway points are represented by Armor.1-BT7
        3.4.2) Taxi points are represented by Vehicles.GAZ67
        3.4.3) Parking points are represented by Vehicles.WillisMB_US
        Copy both files to your mission file in order to load properly
        in the Il2 Mission Builder.
4) in*.txt files
   These are used when you issue the create command.
   4.1) inBridgesReal.txt
        This one is created automatically by using the create command and
        it reads the information from inWings.txt you have to create.
        inWings.txt can be a copy outWings.txt. inWings.txt has to be in form
        which Il2 Mission Builder can read (see 3.1).
        Remember that bridges are defined with two points, so you
        should have even number of NORMFLY lines for each wing.
        Pay attention that for each flight there has to be a coresponding
        _way section with NORMFLY points. If there is not a single bridge
        of certain type, remove wing and coresponding _way section from this
        file if present. Bridge type is defined by airplane type of
        each wing (see 3.1).
   4.2) inNStationary.txt
        This can be a direct copy of outNStationary.txt file or the copy
        of your [NStationary] section in the mission file. Header's
        existance is obligatory, but you can rename it if you wish
        (I can't imagine why you would wish to do so...).
        vehicles.planes.Plane$BI_1 is also not obligatory as long it is
        in the [NStationary], the tool doesn't care.
        x_Static where x is an integer needs to be there, but don't worry
        on the sequence of integers. You can even have several lines
        with the same number, for exmaple:
        3_Static ...
        3_Static ...
        3_Static ...
   4.3) inBuildings.txt
        Direct copy of outBuildings.txt or the appropriate section from
        your mission file. Keep the header, rename if you wish. Number x
        in x_bld is irelevant as in 4.2.
   4.4) inChiefs.txt & inChiefsRoad.txt
        Almost everything is important here: types of object must be
        the same as in out*.txt counterparts. Numbers don't have to be
        in sequence (some number can be skipped too), but they have to
        be different for all 'Chiefs'.
        Of course they have to be consistent in two files.
5) MapSize.txt
   For some reason, bridges are upside down compared to all other objects.
   In order to fix this the tool needs to know y (aka NorthSouth) size of
   the map in question. The value is in meters, set the value yourself.
6) FINAL WORDS
   6.1) Mission files can be huge and might fail to load if you copy everything
        from out*.txt files. No need to do that. Copy just relevant sections.
        Since buldings section can be huge on it's own, try to copy just parts
        of it to mission files. Anyway, what is important is that you have
        all that you need in in*.txt files before you run create. The tool will
        use these files and these files only to create MWactors.static.
   6.2) I expect bugs, sorry.
   6.3) Because of 6.2, there might be some bugfix releases in the future.
7) LEGAL
   Don't know. I'm not responsible.

------------------------------------

BUGFIXES:

21.Jan.2008 (v0.93)
   Failure to create MWactors.static file with empty inWings.txt file
   fixed. Users who had bridges in their actors.static files were
   unaffected by this oversight on my part.