Jump to content

AES FAQ - Please read before Post!


Recommended Posts

  • Developer

Before you post a "Bug" in AES or you have problems with any of the features, please read the post below first, many of the know issues will be explained here.

When you see a problem post of any user in this forum, where a solution is explained here, please just post a link to the related post, so the user can find the text here.

Link to comment
Share on other sites

  • Developer

1.) AES Window not open correct, only Headline visable

When you use the FSX with the Acceleration-Pack (ACC), it will happen, that you open the AES Window this the key-combi and it will only show the headline:


This is a bug in the API of the ACC-Pack, which is corrected in the public SP2, so only user with ACC-Pack have this issue.

In this case, click with the mouse the lower boarder of the transparent window and enlarge the size by pulling down the window, until you see all the lines.

Normally the FSX will keep this size until you restart the FSX.

Link to comment
Share on other sites

  • Developer

2.) AESConfig did not connect to the FS (Windows 7)


When you click on "Set Aircraft Parameters" or "Configuration" in AESHelp, AESConfig is starting. When you don't have a green "Local" in the upper left corner, AESConfig could not connect.

In this case, check the following:

  • FS is running and your Aircraft is place at an airport, which is active supported by AES. When AES is not running (AES Window available) at the Airport, AESConfig can not connect
  • When you use Window 7, it is important to start AESConfig in the same Mode (Admin/Normal) as the FS is started, otherwise Windows will block the communication.
    Start AESConfig direct from the <FS>\Aerosoft\AES Folder or make a shortcut on the desktop, which you configure in the same way as the FS shortcut (Admin/non Admin)

Link to comment
Share on other sites

  • Developer

3.) Aircraft is jumping or crashes while Pushback

When you make the pushback and the aircraft is jumping or generate a crash, the "static_cg_height" and "static_pitch" values in the aircraft.cfg of the aircraft is not set optimal.

  • Place the aircraft at an AES activated airport and start AEShelp/AESConfig. At the "Set Aircraft Parameters" page, you find the "Repair for Push" Button.
  • Press this button once, then save and exit the config.
  • Reselect the Aircraft in the FS to reload the aircaftconfig and try the push again.

It is possible, that the automatic calculation of the values by AESConfig will not correct this problem. In this case, start AESConfig again and press the Button "Reset Push to default", then the original values are back in place in the aircraft.cfg

When the AESConfig button don't help, you can try to find the correct values in the following way:

  • Go to the <fs9>\Aircraft\... or <FSX>\Simobjects\Airplane\... Folder and find the folder related to the aircraft having the problem
  • In that folder you find the aircraft.cfg
  • Search for "static_pitch=" which is in the [contact_points] section


  • Then place the aircraft somewhere in the FS and switch to the "Slew" Mode (default key Y) and back to normal, and you will see that the aircraft will move up and down or change his pitch, when you switch between Slew and Normal.
  • Now, try to change the "static_cg_height" Value in small step's (+- 0.10), save the CFG file, reselect the aircraft in the FS (to reload the new cfg) and check the switch Slew/Normal again.
  • If the aircraft changing the pitch, try the same with "static_pitch"
  • When the aircraft is not anymore moving while the switch over between Slew and Normal mode, the push will work without jumps and crashes.

For the PMDG 737 NGX following values should work correct:

For the PMDG 777 try this:


Link to comment
Share on other sites

  • Developer

4.) Autogen set to NONE: AES will maybe not get active at the Airport, even when set to FS9/FSX in AESHelp

When you use the FS with setting AUTOGEN = NONE (off), it could happen, that at some sceneries objects are missing and not display, maybe only if you fly into an airport. This can not only happen with Aerosoft products!

For AES it could happen, that AES is not active at the airport, even when the airport is activated in AESHelp.

When AUTOGEN is ON (Spare or higher) all is fine.

This is generated by an FS internal optimize process. Some sceneries use special codeparts to protect the autogen around the airports to be removed, but this code will have a sideeffect by setting Autogen=NONE, so that the FS will ignore that code under this conditions.

At the moment it is not clear, if there is a solution to get a fix for Autogen=NONE. Please set the Autogen to Spare or more, related to the speed of you PC to prevent problems here.

Link to comment
Share on other sites

  • 4 weeks later...
  • Developer

5.) You don't hear the Annoucements (Groundstuff and so on)

Please place your aircraft at a AES controlled Airport and start AEShelp/AESConfig, press the Configuration and check the volume of the sound's.

If the sound don't come back at maximum, set the Checkbox "Maximum" behind the annoucement slider, then you should hear the sounds.

Link to comment
Share on other sites

  • 3 weeks later...
  • Developer

6.) AESHelp will not find the Airport Addons as "Installed"

If AESHelp will show an Airport in Red color (or is not in the list, if you have check the Box for "List only installed Addons"), this can have serveral reasons:

- You have not installed the Needed Addon for that airport, which is supported by AES. -> Check the Airportlist on the productpage and install the product

- The Addon is installed, but not activated by a needed Onlineactivation (Aerosoft Launcher for example) -> Activate the Scenery Addon first

- The Addon is installed, but not active in the Scenery Library of the FS -> Check the Scenery Library, if the Addon is listed there and the checkbox infront is active

- The Addon is installed, but it is not the correct/newest Version or a needed Update is missing -> Check the homepage/shop of the Addonprovider for available Updates

- You have removed or renamed manually BGL Files in the addons Scenery directory, which was used by AES to detect the Addon -> bring the BGL's back into the original nameing or reinstall the Addon

Allways check first, if you can see the Airportaddon in the FS, as long as the addon is not shown correct and you see only the default Airport or only parts of the Addon, correct this first, before you try AESHelp. AEShelp will detect addons only by looking in the scenery.cfg for Active entries and search for special BGL files to find in the related Scenery Pathes. If this BGLs are not found, AEShelp will report the Airport as not Installed.

For FS9 in additation another issue may generate trouble to detect installed addons:

When you have installed the FS9 to it's default directory below c:\Program files on a Windows Vista or Windows 7 OS, the UAC (User Access Controll) is active, then it could happen, that the Scenery.cfg of the FS9 is not changed in the original position in the mainfolder of the FS9. In this case Windows makes a copy into the "Virtual Store" to prevent overwriting the original file.

AESHelp will report this condition, when it is started and you can correct this.

  • Upvote 1
  • Downvote 1
Link to comment
Share on other sites

  • Developer

7.) Why can I only order one Creditpack in the Shop (Aerosoft/Simmarket)?

This is a limitation of the Shopsystem, because it is only designed to order one copy of the same Download-Product in one order (which is the usual process for all other Aircafts, Sceneries or Tools, nobody needs them twice). The Shop can assign and store in the History only one Serialnumber for a product in the same order.

So you must make seperate orders, when you what to buy more then one creditpack. Is not nice, but could not be changed for only one Product, where this could happen. Sorry.

Link to comment
Share on other sites

This topic is now closed to further replies.

  • Create New...