AA Renderer

The AA Render depends on the configuration files for the TripleA Open Source "Axis and Allies" clone game. You need to ensure that you have the game installed and that the configuration for the AA renderer is pointing to the correct location.

You can use the "Default" section to configure the AA renderer. Select the version from the combo box, specify the directory that you installed the TripleA game into (e.g c:\program files\TripleA) and then hit the apply defaults button. This will update the three value described below with values appropriate for the specified TripleA version. By using the radio buttons in the default section you can specify which of the default maps you would like the renderer to use.

You can use the default section as a helper to switch between TripleA maps. If you have downloaded skins, you can modify the maps directory to point to the directory containing the skins.

You can also explicitly set the following three configuration values:

  • TripleA Maps Directory - This is the location of the map tiles for the game. This could be a skin or a directory that game with the game. It is important to ensure that the maps directory you choose corresponds with the "Game Config" file that you select (see below).
  • TripleA Images Directory - This is the location of the images files for the game. This includes the unit icons and country flags.
  • TripleA Game Config File - This is the XML configuration file that you wish to use. Each XML file should correspond with a map directory (see above). For instance the Big_World_1942.xml corresponds with the map files in the big_world directory.

    • The renderer will accept any combination of the above directories and file (N.B. You can have the renderer drawing different regions (from the XML) over a totally incompatible map. The renderer will function if the config and images aren't specified (albeit without units and region names rendered), but it does need the maps directory to point to a valid TripleA maps directory.

    The renderer now supports importing of save games generated by TripleA version 0_8_1 and above. If you select the "Import TripleA Savegame" check box and specify a save game file it will generate a AAA.txt in the aa renderer install location. This file is used to render the current save game and all previous turns. You can configure the speed that the screen saver flips through turns by modifying the values in the configuration dialog.

    N.B. To use the import save game functionality you will need to ensure that the configuration points to the most recent javaw.exe on your machine (packaged with newer versions of tripleA). You will also need to configure the AA renderer to point to the current TripleA.jar in the TripleA install directory. (the JAR file that was used to generate the turn). The defaults section of the configuration dialog tries to fill these values correctly, so you can use that for a guide.

    Please email me if you have any questions.

    Disclaimer 
     Copyright (c) 2006
 Tom Horn.  All rights reserved.

 Redistribution and use in source and binary forms, with or without
 modification, are permitted provided that the following conditions
 are met:
 1. Redistributions of source code must retain the above copyright
    notice, this list of conditions and the following disclaimer.
 2. Redistributions in binary form must reproduce the above copyright
    notice, this list of conditions and the following disclaimer in the
    documentation and/or other materials provided with the distribution.
 3. Redistributions in any form must be accompanied by information on
    how to obtain complete source code for the DB software and any
    accompanying software that uses the DB software.  The source code
    must either be included in the distribution or be available for no
    more than the cost of distribution plus a nominal fee, and must be
    freely redistributable under reasonable conditions.  For an
    executable file, complete source code means the source code for all
    modules it contains.  It does not include source code for modules or
    files that typically accompany the major components of the operating
    system on which the executable file runs.

 THIS SOFTWARE IS PROVIDED BY TOM HORN ``AS IS'' AND ANY EXPRESS
 OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
 WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR
 NON-INFRINGEMENT, ARE DISCLAIMED.  IN NO EVENT SHALL TOM HORN
 BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
 CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
 SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
 INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
 CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
 ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
 THE POSSIBILITY OF SUCH DAMAGE.