Developer's Backdoor > GSX Backdoor

Aerosoft AES Compatibility

<< < (2/2)

virtuali:

--- Quote from: fbass on February 01, 2012, 08:04:31 pm ---GSX does nothing unless you request a service.  There are no "airport clutter" items on the airport until you request a service.
--- End quote ---

That's correct.


--- Quote ---AES does nothing unless you request a service with a hot key.  There are no clutter items until you want them - via a request.
--- End quote ---

Not quite, there's a difference:

BOTH programs have an Hotkey that will open a menu, and from that you then select services and operation. The difference is that GSX will not do anything until AFTER you select the wanted operation from the menu so, if you just open and then close its menu, nothing will appear, AES prepares a parking with objects as soon as you press its Hotkey to open its menu.


--- Quote ---HUH?  It was my understanding that both AES and GSX modify FSX default textures and provide additional airport vehicle models to enhance the scenery.
--- End quote ---

None of them does anything like that. Both programs comes with their own set of objects, using their own textures, and no default object or texture is ever touched.

The only thing that GSX does to the default objects, is to disable the default Pushback vehicle, by patching a default .BGL, after having made a backup of it, to be restored in case you uninstall GSX.

vadriver:
umberto

AES does not - in my experience - need an hotkey to "start".

when you load an FS situation, it "automatically" extends the jetway & sends the baggage loaders & similarly when you arrive at the gate after providing marshalling direction as appropriate.

so i am guessing & as i want to use GSX at FSDT airports (with animated jetways), somehow I need to stop AES thereat !!

however for example, at flightbeam's KSFO, i would need to use AES for the animated jetways (but GSX won't interfere if I don't use its hotkey).

thus, a mix & match scenario for me

your advice please

deetee:
Hi folks,

Neither AES or GSX will do anything until you activate their services via their respective hotkey-activated menus.

However to me it would also make sense to exclude any AES activated airports from GSX using the "Couatladdons.ini" file as explained in the manual, by adding their ICAOs to the "disable_on_airports" line.

virtuali:

--- Quote from: deetee on February 02, 2012, 09:26:26 am ---Neither AES or GSX will do anything until you activate their services via their respective hotkey-activated menus.
--- End quote ---

Not really, in GSX, if you press its hotkey while parked, nothing will happen until you select an actual operation (Boarding, Deboarding, Pushback) from the menu. Pressing the hotkey again, to let the menu disappear, it's the same as having changed your mind without doing nothing. No objects will ever be created on the parking if you just open and then close its menu.

In AES, as soon as you are on a parking with engines off and activate the parking brakes, the parking is prepared with ground objects and stairs automatically approach the airplane even before you open its menu with the hotkey.

This difference is what prevents a better mix of both products because, if AES did the same as GSX, and created or at least started to move objects towards the airplane only after you selected one of its operations, you could do something like letting AES operating the jetway, Deboarding baggage with GSX, ask AES for lavatory/water vehicles, ask for GSX catering, and maybe being Pushed back by AES.

There might be some clashing between ground objects starting positions, but we can tweak that easily, it wouldn't be a great issue if you had both AES and GSX vehicles together at the same parking standing still, as long they aren't really on top of each other.


--- Quote ---However to me it would also make sense to exclude any AES activated airports from GSX using the "Couatladdons.ini" file as explained in the manual, by adding their ICAOs to the "disable_on_airports" line.
--- End quote ---

We added that option for the only reason to give a temporary working solution to AES users wanting to use AES on an airport they purchased credits for.

fbass:
Ah, the light comes on.  The discussion has revealed that there may be some conflicts between the two products but the user can use techniques and configurations to solve them.  This is what I was looking for - and thanks to every one who responded.

It also appears that there is some work to be done by the user if both products are to be used at the same time.  I don't know about you, but I don't have the time to concern myself about particular airports and whether or not I can use this product or that one when I fly to or from them.  I don't want to worry about that - in other words if it's not automatic don't use it.

I haven't seen a reasonable case made for which product is better - functionality, textures, operation, etc.  So, unless Aerosoft makes their product compatible with the FSDreamTeam software, I'm going with FSDT.

Thanks for the insight.

Frank

Navigation

[0] Message Index

[*] Previous page