No, GSX will spawn vehicles only around your plane, didn't saw vehicles around AI's. Did saw some GSX vehicles at random spots, but in very small numbers. I will set default vehicles on minimum or medium, just to keep airports alive.

GSX

I use both AES and GSX, I use AES at any airport that is compatible with it, and GSX at airports that aren't such as freeware, default or ones that just haven't been given the AES treatment yet.

 

AES works great with a proper jetway system, cleaning crew and pushback and custom liveries for the service vehicles for different airports with a large database available for free. 

 

GSX works great at airports with either default or no jetways, but with add-on airports with correctly modeled jetways GSX lags behind AES, but still great as it's a once off payment and can be used at any airport you want.

 

My opinion, get both.

 

Regards,

Ró.

So will AES work with FSDT airports? They work with all of Aerosoft's airports though right? Is there a list somewhere of all the airports that AES works with? 

Here's the list of airports that work with AES:

 

http://www.aerosoft2.de/downloads/aes/aesairports.html

 

AES is compatible with all FSDT airports bar JFK v2.0 and CYVR AFAIK.

 

Regards,

Ró.

Ronan thanks a lot for that list!

I use both AES and GSX, I use AES at any airport that is compatible with it, and GSX at airports that aren't such as freeware, default or ones that just haven't been given the AES treatment yet.

 

AES works great with a proper jetway system, cleaning crew and pushback and custom liveries for the service vehicles for different airports with a large database available for free. 

 

GSX works great at airports with either default or no jetways, but with add-on airports with correctly modeled jetways GSX lags behind AES, but still great as it's a once off payment and can be used at any airport you want.

 

My opinion, get both.

 

Regards,

Ró.

I concur.

 

AES is the better product with the limitations of the compatibility to addon airports. It just feels like a more complete package because of its customization to the airport.

 

Shez

One little nuance I have with AES is when you first open the menu with Ctrl+Shift+w is the fact that you have to resize the box to see the options. Is there any fix for this or is it just me?

AES is the better product with the limitations of the compatibility to addon airports. It just feels like a more complete package because of its customization to the airport.

A common misconception, is believing that GSX is "automatic" only, while AES is "tailored" to an airport.

 

This is just not true. GSX can ALSO work in fully tailored mode, it just that we have chosen against selling airport customizations one by one, as a business model

 

Instead, we chose to make GSX a one-time purchase, give away for free all customization (FSDT and Flightbeam sceneries) AND let users (and 3rd party scenery developers) create their own customization and share them.

 

There are 3 different ways GSX operates:

 

1) Automatic "default" mode, which is how GSX works on any airport, past present and future, as long as it comes with a standard AFCAD.

 

2) USER customization mode.

 

Any user can easily fix issues in the scenery AFCAD such parking sizes too big or too small, pushback not working or wrongly assigned, the presence of fake/static jetways or other parking assignments which GSX can't detect, etc.

 

OR, an User can go a bit deeper than that, and customize each and every vehicle starting position for each parking, in order to integrate better with the scenery objects, using a very easy interactive editor inside FSX. Users can also share their customization files quite easily.

 

Note that, although this is called "user" customization, the more involved parking-by-parking customization might be made by original scenery developer, simply supplying the scenery with a GSX .INI file together with the scenery files. This way, a scenery developer can offer better GSX support without our help, on scenery release date.

 

3) FSDT complete customization.

 

This is even more involved and, right now, its most complex features can only be programmed by us, because they are written as a Python program as a script, without any graphical interface . Those includes custom pushback routing with custom label messages, renaming and re-grouping of all parking names to overcome the AFCAD naming limitations, custom parking assistances such as docking systems and much more.

 

Right now, all FSDT and all Flightbeam sceneries comes with a full-blown #3 customization AND they are ALL FREE, there's no need to purchase GSX to get a fully working GSX with a complete customization on those sceneries.

 

If a scenery developer would like to offer this level of customization, we'll be happy to help, and it won't cost him anything: a license will be required ONLY in case he wants his scenery to work with the FREE GSX, which is what Flightbeam does, but their customers won't have to pay anything extra, if they already own GSX.

 

We also plan to gradually extend features that were previously possible only with scripting code, in the regular user customization mode. Earlier GSX releases didn't had a graphical editor for parking spots, and didn't had any graphical editor for airplane config either, it was all made with scripting, but now this is included and accessible to all users, it's just that writing graphical UIs for those features (for example, to draw custom pushback routes) is not the easiest thing in the world, but they'll come, eventually.