[P3Dv4] Vidan Design Billund X v1.02 -> GSX does not interact with SODE (v1.5.3)

[Er!k]

Hello Umberto,

Today did a flight to Billund in P3Dv4 (Vidan Design v1.02). The scenery has SODE jetways included and they do work. However, when arrived at the gate GSX does not recognize the SODE jetways, so I need to use SODE to operate the jetways. Also stairs are by default placed at door L1 (I removed them with the config tool) for all gates with jetways.

Is this something that can be fixed in a future update?

Thanks,

Erik

[virtuali]

There's no reason GSX won't work with a 3rd party scenery with SODE jetways, since it has been designed to recognize such jetways.

Is this scenery made using the latest SODE jetway SDK ? If it's using a very early version, it's possible jetways might not be recognized.

[Er!k]

I'll ask over the Vidan forum, thanks!

[Er!k]

For who is interested; I raised the topic here: http://vidandesign.com/forum/viewtopic.php?f=42&p=3168&sid=d0572c1f7f38740d79fd3dd2368346ca#p3168 No reply unfortunately

[Anders Bermann]

I'm having the same issue... also have the same problem with Drzeweicki Design newly released NYC Airport package...

[Er!k]

Strange indeed... And no reply over at the Vidan forum. I do not own the DD packages (was too disappointed with v1) so can't test that one out.

[Anders Bermann]

Okay... I've been digging around a little with Vidan Design EKBI...

It seems that GSX is working correctly but for some reason, the scenery itself is incorrectly configured. Perhaps Umberto can shed some light on what this means...

I found this in SODE.log file:

Code: [Select]

[15:31:33.794] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=8, DoorDesignator='1L', OwnFlag=0, DoorDataOverrideFlag=1, Mode=1
[15:31:33.794] WARN SODE.FSLOOP :  [JETWAY CONTROL SYSTEM] No 'jetway.cfg' found. Unable to move Jetway...

Something in the scenery is missing, because I assume that the API::TRIGGER line means, that GSX 'asks' the SODE jetway to connect - but SODE throws an error back, saying it can't find a 'jetway.cfg' file... Hence, the jetway won't move...

I guess, I'll have to see if Vidan Design will take a look at this...

[Anders Bermann]

I just got a reply back from the SODE Support Forums and it's a problem with GSX, which apparently tries to call a static jetway.
This is the full log:

[17:15:29.704] INFO  : SODE Version 1.5.3
[17:15:29.704] INFO  : Targetting Platform 'P3Dv4'
...
[17:16:46.855] INFO SODE.FSLOOP : ### FILTERING OBJECTS WITHIN SIM RADIUS OF 40000m
[17:16:46.897] INFO SODE.FSLOOP : ### Active SimObjects: 10; Active Wind Data Probes: 0
[17:16:46.974] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 26 [VidanDesign_EKBI_Jetway_Static_0]. ID: 6
[17:16:46.975] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 28 [VidanDesign_EKBI_Jetway_Static_0]. ID: 7
[17:16:47.036] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 29 [VidanDesign_EKBI_Jetway_Static_1]. ID: 8
[17:16:47.036] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 31 [VidanDesign_EKBI_Jetway_Static_1]. ID: 9
[17:16:47.036] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 32 [VidanDesign_EKBI_Jetway_Static_1]. ID: 10
[17:16:47.038] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 34 [VidanDesign_EKBI_Jetway_Static_1]. ID: 11
[17:16:47.038] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 35 [VidanDesign_EKBI_Jetway_Static_1]. ID: 12
[17:16:47.038] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 37 [VidanDesign_EKBI_Jetway_Static_1]. ID: 13
[17:16:47.038] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 38 [VidanDesign_EKBI_Jetway_Static_1]. ID: 14
[17:16:47.038] INFO SODE.FSLOOP :  + SimObject VidanDesign_EBKI_Stands:Jetway 1 PARKING 40 [VidanDesign_EKBI_Jetway_Static_1]. ID: 15
[17:16:47.827] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[17:17:33.992] DEBUG SODE.ACFTEXITS : No Custom Data Found for X:\Prepar3D\SimObjects\Airplanes\PMDG 737-800NGX WL\. Using original aircraft.cfg exit data!
[17:17:38.149] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[17:18:36.733] INFO SODE.FSLOOP : SeasonalObjectHandler: Refreshing Season/Time Data...
[17:18:40.363] DEBUG SODE.FSLOOP :  [API::TRIGGER] Received Trigger Client Data: ObjID=8, DoorDesignator='1L', OwnFlag=0, DoorDataOverrideFlag=1, Mode=1
[17:18:40.364] WARN SODE.FSLOOP :  [JETWAY CONTROL SYSTEM] No 'jetway.cfg' found. Unable to move Jetway...
[17:19:13.810] INFO SODE.FSLOOP : SODE disconnected from Simulator!
[17:19:13.811] DEBUG SODE.FSPROCESS : Cleaning up Memory...
[17:19:13.815] DEBUG SODE.FSPROCESS : Removing Top-Menu structure...
[17:19:13.815] DEBUG SODE.FSPROCESS : Closing Connection to FS.
[17:19:13.915] INFO  : Terminate SODE.

Apparently (I've highlighted the problem areas/lines in bold) you can see, that API::TRIGGER tries to call a static jetway (ID=8) and fails...
I'd assume it's something which needs to be fixed in GSX or is it a scenery issue?

[Er!k]

Interesting find! Let's hope it can be resolved.

[virtuali]

We'll surely have a look at this.

[Anders Bermann]

Thanks Virtuali,

I have identical issues with Taxi2Gate LFPG and Drzeweicki Design NYC Package v2.

Haven't tested other sceneries... FSDT sceneries work correctly, FlightBeam KMSP and Aerosoft Oslo 2.0 works too...

I'll be standing by...

[BuddyDog]

I seem to have this problem also with DD KEWR with SODE 1.5.3.

I am in the process of migrating from P3D v3.4 to v4, so hoping for a fix.

[Er!k]

We'll surely have a look at this.

Any news Umberto?

[virtuali]

Any news Umberto?

I'm on vacation until August 22nd, and so is the other main GSX developer so, we still haven't found the chance to verify this.

[Er!k]

No problem, enjoy your holiday