pommesschranke wrote in Wed Sep 09, 2015 8:31 am:but is KSFO the only airport that uses this kind of Jetways?
Feel free to expand the FG universe with this awesome but unfortunately underutilised infrastructure
Regards,
Edward
pommesschranke wrote in Wed Sep 09, 2015 8:31 am:but is KSFO the only airport that uses this kind of Jetways?
pommesschranke wrote in Wed Sep 09, 2015 10:57 am:do you maybe have an idea how/why it got broken or how to fix it ?
commit 9b19d5e20e87e0f2e3e4473fa6162285fd2b1fe7
Author: Ryan M <tpbspammail <att> gmail dot com>
Date: Mon Feb 4 15:42:08 2013 -0800
Animated jetways: Remove obsolete use-custom-scenery-data property
but is KSFO the only airport that uses this kind of Jetways?
<!-- Parameters set by the script -->
<toggle-action-script type="string" />
<!-- Animations -->
<!-- Click action -->
<animation>
<type>pick</type>
<action>
<button>0</button>
<repeatable type="bool">false</repeatable>
<binding>
<command>nasal</command>
<script alias="../../../../toggle-action-script" />
</binding>
</action>
</animation>
# The script dynamically generates runtime model files, writes them to
# $FG_ROOT/Models/Airport/Jetway/runtimeX.xml, and places them into the
# simulator using the model manager.
#
if (props.globals.getNode("/aircraft/door[0]/x-m") != nil and props.globals.getNode("/aircraft/door[0]/y-m") != nil and props.globals.getNode("/aircraft/door[0]/z-m") != nil)
{
var xm = getprop("/aircraft/door[0]/x-m");
var ym = getprop("/aircraft/door[0]/y-m") - 2.65;
var zm = getprop("/aircraft/door[0]/z-m") - 3.752;
<sim>
<model>
<door>
<position-x-m type="float">X-M</position-x-m>
<position-y-m type="float">Y-M</position-y-m>
<position-z-m type="float">Z-M</position-z-m>
<jetway-hood-deg type="float">HOOD-DEG</jetway-hood-deg>
</door>
</model>
</sim>
# old system (legacy support)
elsif (props.globals.getNode("/aircraft/jetway-pos/x-tra") != nil and props.globals.getNode("/aircraft/jetway-pos/y-rot") != nil and props.globals.getNode("/aircraft/jetway-pos/z-rot") != nil and props.globals.getNode("/aircraft/jetway-pos/hood-rot") != nil)
{
# rotation angles and extension lengths are predefined
var xtranslate = getprop("/aircraft/jetway-pos/x-tra");
var yrotate = getprop("/aircraft/jetway-pos/y-rot");
var zrotate = getprop("/aircraft/jetway-pos/z-rot");
var hoodrotate = getprop("/aircraft/jetway-pos/hood-rot");
}
<aircraft>
<jetway-pos>
<x-tra>-2</x-tra>
<y-rot>2</y-rot>
<z-rot>18</z-rot>
<hood-rot>0</hood-rot>
</jetway-pos>
</aircraft>
pommesschranke wrote in Fri Sep 11, 2015 8:44 am:because there is a fallback to the older convention, which is not documented in the wiki:
pommesschranke wrote in Wed Sep 09, 2015 10:59 pm:* you click one and all start to move
pommesschranke wrote in Wed Sep 09, 2015 10:59 pm:* they only work when placed in front of the aircraft, I can not use them when the terminal building is on the side of the aircraft.
pommesschranke wrote in Wed Sep 09, 2015 10:59 pm:* movement is not visible via multiplayer
pommesschranke wrote in Fri Sep 11, 2015 8:44 am:why does it work then ?
because there is a fallback to the older convention, which is not documented in the wiki:
Users browsing this forum: No registered users and 12 guests