Animated jetways: Difference between revisions

Jump to navigation Jump to search
+ Section briefly the two types of jetways based on description further down; +- Cleanup; +cat: AI Traffic
m (→‎Related content: +- Jetways as scenery objects → List stg files with non-AI jetway scenery objects)
(+ Section briefly the two types of jetways based on description further down; +- Cleanup; +cat: AI Traffic)
Line 1: Line 1:
[[File:Animated-jetways-KSFO.jpg|thumb|Animated jetways at [[San Francisco International Airport|KSFO]]]]
[[File:Animated-jetways-KSFO.jpg|thumb|Animated jetways at [[San Francisco International Airport|KSFO]]]]
'''Animated jetways''' can be set in motion by pilots arriving at terminals of airports in FlightGear that have had them added.
'''Animated jetways''' can be set in motion by pilots arriving at terminals of airports in FlightGear that have had them added.


Jetways are the "tubes" that passengers use when entering or leaving aircraft docked to the passenger terminals.
Jetways are the "tubes" that passengers use when entering or leaving aircraft docked to the passenger terminals.


There are at least 2 types of animated jetways in FlightGear.
== Different types of jetways ==
There are at least two types of animated jetways in FlightGear, here called type 1 and type 2. Type 1 is more advanced than type 2.
 
; Type 1
: They can connect to your aircraft and also to AI or multiplayer aircraft, (almost) no matter where you stand and in which orientation, as long as you are near enough.
 
; Type 2
: You have to park very precisely, they do not connect to AI aircraft and they are not visible to other in multiplayer, etc.  


== Animated jetways type 1 ==
== Animated jetways type 1 ==
Type 1 is described in [[Howto:Animated jetways]].
{{main article|Howto:Animated jetways}}


Type 1 is more advanced than type 2.  They can connect to your aircraft and also to AI or multiplayer aircraft, (almost) no matter where you stand and in which orientation, as long as you are near enough.
=== Known issues ===
=== Known issues ===
* They only exist in [[San Francisco International Airport|KSFO]]. But jetways.xml files for more airports are availible here: http://media.lug-marl.de/flightgear/jetways/ and here: https://github.com/mherweg/Airports
* They only exist in [[San Francisco International Airport|KSFO]]. But <code>jetways.xml</code> files for more airports are available here: http://media.lug-marl.de/flightgear/jetways/ and here: {{github source|user=mherweg|repo=Airports}}
* <code>generic.xml</code> in FGData is broken. <code>generic.xml</code> in [[TerraSync]] is repaired.  See this forum post:
* <code>generic.xml</code> in FGData is broken. <code>generic.xml</code> in [[TerraSync]] is repaired.  See this forum post: {{forum link|p=257608|title=Re: jetways at KSFO}}
http://forum.flightgear.org/viewtopic.php?f=5&t=27375#p257608 
* The elevations in the output file of the Jetway editor has to be corrected manually. '''A version of <code>jetways.nas</code> without the elevation problem can be found here''': http://media.lug-marl.de/flightgear/jetways/
* The elevations in the output file of the Jetway editor has to be corrected manually. '''A version of jetways.nas without the elevation problem can be found here''': http://media.lug-marl.de/flightgear/jetways/
* The stg converter of the Jetway editor has a bug in the file-selection dialog.  '''A fixed version of <code>jetways_edit.nas</code> can be found here: ''' http://media.lug-marl.de/flightgear/jetways/
* The stg converter of the Jetway editor has a bug in the file-selection dialog.  '''A fixed version of jetways_edit.nas can be found here: ''' http://media.lug-marl.de/flightgear/jetways/


The last 2 bugs (jetways.nas & jetways_edit.nas) are fixed in the git version of FGData http://sourceforge.net/p/flightgear/fgdata/ci/dd3390b3afee955ba23dfd9334baf438bc7ae989/
The last 2 bugs (<code>jetways.nas</code> & <code>jetways_edit.nas</code>) are fixed in the git version of FGData {{fgdata source|commit=dd3390b3afee955ba23dfd9334baf438bc7ae989}}


here's another improved version of jetways.nas & jetways_edit.nas:
Here's another improved version of <code>jetways.nas</code> & <code>jetways_edit.nas</code>:
https://forum.flightgear.org/viewtopic.php?f=5&t=8728&p=306013&hilit=jetway#p305747
{{forum link|p=306013|title=Re: The animated jetway project}}


=== Adding type 1 jetways to an airport ===
=== Adding type 1 jetways to an airport ===
Line 29: Line 32:
=== Type 1 Jetways at KDEN ===
=== Type 1 Jetways at KDEN ===
recommended:
recommended:
* Rename Models/Airport/Jetway/jetway-movable.xml   to jetway-movable.xml.bak
* Rename <code>Models/Airport/Jetway/jetway-movable.xml</code> to <code>jetway-movable.xml.bak</code>
alternative:
alternative:
* remove all <model> entries from Objects/w110n30/w105n39/KDEN_Concourse_C.xml
* remove all <model> entries from <code>Objects/w110n30/w105n39/KDEN_Concourse_C.xml</code>


=== Type 1 Jetways at KLAS ===
=== Type 1 Jetways at KLAS ===
recommended:
recommended:
* Rename Models/Airport/Jetway/jetway-movable.xml   to jetway-movable.xml.bak
* Rename <code>Models/Airport/Jetway/jetway-movable.xml</code> to <code>jetway-movable.xml.bak</code>
alternative:
alternative:
* remove all lines with <code>OBJECT_SHARED Models/Airport/Jetway/jetway-movable.xml</code> from <code>Objects/w120n30/w116n36/1056643.stg</code>
* remove all lines with <code>OBJECT_SHARED Models/Airport/Jetway/jetway-movable.xml</code> from <code>Objects/w120n30/w116n36/1056643.stg</code>
Line 41: Line 44:
=== Type 1 Jetways at PANC ===
=== Type 1 Jetways at PANC ===
recommended:
recommended:
* Rename Models/Airport/Jetway/jetway-movable.xml   to jetway-movable.xml.bak
* Rename <code>Models/Airport/Jetway/jetway-movable.xml</code> to <code>jetway-movable.xml.bak</code>
alternative:
alternative:
* remove all lines with '''OBJECT_SHARED Models/Airport/Jetway/jetway-movable.xml''' from Objects/w150n60/w150n61/501192.stg
* remove all lines with <code>OBJECT_SHARED Models/Airport/Jetway/jetway-movable.xml</code> from <code>Objects/w150n60/w150n61/501192.stg</code>


=== Type 1 Jetways at EGKK ===
=== Type 1 Jetways at EGKK ===
* create a folder Models/Airport/Jetway/backup and move jetway.xml, jetway-747-ba.xml, jetway-737-ba.xml, jetway-a320-ba.xml into that folder.
* create a folder <code>Models/Airport/Jetway/backup and move jetway.xml</code>, <code>jetway-747-ba.xml</code>, <code>jetway-737-ba.xml</code>, <code>jetway-a320-ba.xml</code> into that folder.
alternative:
alternative:
* remove all lines with '''OBJECT_SHARED Models/Airport/Jetway/...''' from Objects/w010n50/w001n51/2941771.stg
* remove all lines with <code>OBJECT_SHARED Models/Airport/Jetway/...</code> from <code>Objects/w010n50/w001n51/2941771.stg</code>


=== Type 1 Jetways at EHAM ===
=== Type 1 Jetways at EHAM ===
That is a tough one! The static jetways are part of the .ac file of the terminals e.g. Schiphol_Gate_E.ac. If you really want animated jetways there, you have to edit those terminal buildings in a 3D software like blender or sketchup.  EHAM_gate.xml and EHAM_gate_2.xml also need to be fixed but that is easy: you can download them here:  
That is a tough one! The static jetways are part of the .ac file of the terminals e.g. <code>Schiphol_Gate_E.ac.</code> If you really want animated jetways there, you have to edit those terminal buildings in a 3D software like blender or sketchup.  <code>EHAM_gate.xml</code> and <code>EHAM_gate_2.xml</code> also need to be fixed but that is easy: you can download them here:  
http://media.lug-marl.de/flightgear/jetways/
http://media.lug-marl.de/flightgear/jetways/


=== Type 1 Jetways at EDDF ===
=== Type 1 Jetways at EDDF ===
EDDF has no other jetways except for Type1-Jetways at Terminal A+. So just put EDDF.jetways.xml into  the Airports/E/D/D/  folder
EDDF has no other jetways except for Type1-Jetways at Terminal A+. So just put <code>EDDF.jetways.xml</code> into  the <code>Airports/E/D/D/</code>   folder


== Animated jetways type 2 ==
== Animated jetways type 2 ==
Line 74: Line 77:


=== Adding type 2 jetways to an aircraft ===
=== Adding type 2 jetways to an aircraft ===
Add the following to your aircraft-set.xml, see the A380 as an example. You can find the right values by parking your aircraft at a type 2 jetway and setting the properties in /scenery/airport/jetway. In that way you don't have to restart FlightGear everytime to check if your settings are right.
Add the following to your aircraft-set.xml, see the A380 as an example. You can find the right values by parking your aircraft at a type 2 jetway and setting the properties in <code>/scenery/airport/jetway</code>. In that way you don't have to restart FlightGear every time to check if your settings are right.


<syntaxhighlight language="xml">
<syntaxhighlight language="xml">
Line 98: Line 101:
</aircraft>
</aircraft>
</syntaxhighlight>
</syntaxhighlight>


== Related content ==
== Related content ==
* [[List stg files with non-AI jetway scenery objects]]
* [[List stg files with non-AI jetway scenery objects]]


[[Category:Scenery enhancement]]
[[Category:Scenery enhancement]]
[[Category:AI Traffic

Navigation menu