AUTOMATIC JETWAYS
-----------------

This is a customized version of the project: "The animated jetway project", see the Flightgear forum.

Author: Xavier De Goër (alias AF2222).
Contact: FGExtend@autosoft.fr

Purpose: To achieve acceptable performance for both the simulated aircraft and MP aircrafts.
         In the case of MP aircraft, the criterion used is the running/stopped state of the first engine.


May 2019.

Correction of malfunctions, and improvement of the logic MP.

By default, the only reliable parameters (useful in this context) transmitted through the MP protocol are the engines parameters.
We do not find the park brake, for example.

I finally adopted the following logic:

Either the aircraft used is "standard", and I remain on the previous principle (engine 0 running or not) to activate the gateway animation.
Either we use an airplane that transmits on MP the 3 connected, connected [1], connected [2] properties, or at least the first one if the aircraft only manages one gate:
A "copy" of the maneuvers of the gateways initiated by the user of the related aircraft is then obtained.


June 2017.

Package Contents:
	- fgdata.zip: The structure should be sufficiently explicit, except that there are 2 versions of the Models/Airport/Jetway directory.
				  The Jetway.edit contains all image and *airline.*.xml files used by my sample sceneries, and keeps the "old" jetways,
				  this can be useful to place "new" jetways at the same place than "old" ones.
	              You need to rename your Jetway directory, and then use either one instead.
				  You need also to rename the Models/Airport/Jetway directory of the main scenery directory (Terrasync), as "_Jetway" for example.
  
	- ICAO_scenery *.zip: Examples to use as custom sceneries, I do not explicit that here.


Issues related to gateways in Terrasync sceneries.
--------------------------------------------------
There are two kinds of problem:
	1) if there are static jeteways in the .ac file of the terminal, no other possibility than to modify this file to remove them,
	   this is the case at TFFF (Thanks to David), and TNCM for example, then use the modified file in a custom scenery folder.
	2) There are references to jetways in .stg files:
	   In this case, the Models/Airport/Jetway directories of both fgdata and Terrasync folders MUST no longer contain the target templates (hence my advice above).
	   It is also necessary to avoid that Terrasync hands them back, hence the use of FGExtend (free advertising !!!, lol).


Known Issue:
------------
Loading ai gateways causes lags, I bypass this by disabling them during the flight, and reactivating them when taxiing on arrival.

2017/06/24
I modified some constants in the script, and now jetways are loaded only if your aircraft groundspeed is less tah 20 Kt.
The  result seems to be quit correct.


Conclusion:
-----------
I spent a lot of time putting a plaster on a wooden leg, with some success.
I hope that the issue "jetways" will be taken up properly by the FG developers.
Waiting...
