Professional Documents
Culture Documents
Concept: AES Repaint Install Info Version 2.30
Concept: AES Repaint Install Info Version 2.30
30
Concept
With AES 2.30 the second Step of replaceable vehicle textures is implemented.
The assignment of Textures can be very complex, so that AES 2.30 first includes the
simple form, which is more or less automatic. Repaints can now replace the AES
Default Texture for the vehicles for all Airports, Regions or for a specific Airport based
on the ICAO code.
Vehicle ID
The <vehicle ID> defines the Vehicle it is used for, like 02-01 for the long bus.
At the end of this document, you find a list with the ID’s related to the vehicles they
are used of
Texture ID
The <Texture ID> is a 4 digit Name, for the default AES Texture it is always 4 zeros
(0000).
Never use repaints, where the 0000 is in the name, they will be overwritten any time
of an AES update.
1
For the <Texture ID> in this AES Version, two type of ID’s are usable
This are the Default Textures of AES and will always replaced, then AES is installed
or updated. So please don’t use them for any replacements. This textures are used in
AES, when no other Texture of a higher level is found.
In this case, the repaint Texture is used at all airports instead if the AES Default
Texture, as long as there is no ICAO code related Texture of a higher level is present
for that Airport.
The first Letter of the ICAO Code, like K--- for all Airports in USA.
Those Textures will be used of all Airports of the Region.
Level 3: <Texture ID> = ??- - Two Letters followed by two minus signs
The first two letters of the ICAO code defines the Country, where the Textures will
used, like ED- - for all German Civil Airports
Level 4: <Texture ID> = ??? - Three Letters followed by one minus sign
The complete ICAO Code will define the Airport, where the textures are used.
When you have downloaded a repaint set, please check the used Texture ID’s. If
they don’t fit to your needs, rename the both (*.BMP and *_LM.BMP) as you want to
use it, XXXX for global use, or ICAO Code for a specific airport.
If you want to use the same texture at multi airport, but not global, at the moment
please make a copy of the textures for each Airport you want to use it.
2
Who does AESHelp handle the config?
When AESHelp is starting and closed, it will check, which Textures are present in the
<FS9 or FSX>\Aerosoft\AES\TEXTURE Subfolder and will create a special Config file
for all Airports, where repaints could be found. So you have to do nothing else, then
to copy the Texture in the TEXTURE Subfolder of AES and start and stop AESHelp
once. If AESHelp don’t find a repainted Texture of one vehicle, it will still use the
original AES Default Texture.
Future Plans?
Beside the “simple” Texture ID’s we used now, we plan for the future Version also
Texture ID’s based on Airlinecode or Service Agents and a Configuration tool to
assign such textures to each airport manually. But this will be much more complex
and need some more planning and development.
http://forum.aerosoft.com/index.php?/files/category/42-airport-vehicle-repaint/
http://forum.aerosoft.com/index.php?/forum/113-airport-enhancement-services/
3
Vehicle ID List