December 30, 20205 yr Hi all, Using Drzewiecki Design's KSEA, at the gate I can get jetways to dock using the SODE menu, but when I use GSX it just says, 'No Jetways Here'.# If I go into the gate configuration page, it says 'No Jetway' even though I can clearly see it and it works with SODE command. If I click '1 Jetway Here' in the GSX gate it just places a random jetway in the wrong place...! Can someone help? Cheers, Ben AMD Ryzen™ 9 9900X3D, AM5, Zen 5, 12 Core, 24 Threads, 4.4GHz, 5.5GHz Turbo 64GB (2x32GB) DDR5 6000MHz Corsair Vengeance 32GB GeForce® RTX 5090 Graphics Card
December 30, 20205 yr Commercial Member This has been explained many times on our forum: for 3rd party SODE jetways recognized by GSX, their associated gate name must be named *EXACTLY* like the matching gate in the AFCAD, because the precise, exact, gate name and number is the only way for SODE to communicate to GSX which jetways is assigned to which gate. The gate name must follow standard AFCAD naming convention exactly so, for example, a gate named Gate B 23, MUST be referred in the SODE XML file as such: AfcadGateName="GATE_B" AfcadParkingNumber="23" That's the only way the gate would be recognized by GSX as well. Also, having to stick to the default naming convention in order to enable GSX communication, won't restrict in any way the ability for developers to present the jetways using a more friendly name to users, because SODE has a parameter for that so, to continue the following example: AfcadGateName="GATE_B" AfcadParkingNumber="23" CustomDesignator="Terminal 1 Gate B23"> The jetway would still follow strict AFCAD naming rules, so it would be recognized by GSX, but it will display with friendlier name on the SODE menu so, no flexibility is ever lost to maintain full GSX compatibility. I don't know specifically about KSEA but, DD sceneries use to encrypt their SODE XML files, so they are .SDX files you cannot modify for yourself so, if this is the case for KSEA too, I suggest reporting this to DD, so they might add the required modifications to the file to obtain full GSX compatibility. The alternative would be, instead, just removing the XML ( or SDX file ), and replace all jetways with GSX L2 jetways. And yes, it's entirely normal they would appear in a "random" place because this is what is supposed to happen when the jetway is not recognized by GSX ( because of the naming convention not followed ), the parking is treated as empty, so GSX cannot possibly know where to place a jetway it cannot see, so it place it in a random location on the parking spot. Edited December 30, 20205 yr by virtuali Umberto Colapicchioni http://www.fsdreamteam.com FSDT on Facebook
Archived
This topic is now archived and is closed to further replies.