Jump to content

Wrong docking guidance animated


Recommended Posts

I have base plugin v2.1.8 and world jetways 1.0.4

Under v2.1.7 I added Safegate docking guidance (and some marshallers where necessary) to gates at the default gateway EHAM scenery. The dockings were all added successfully in the authoring tool.  Since 2.1.8 I'm noticing a different behaviour: I approach the gates at 90 degrees to the direction I'm going to park in, but as I swing the nose round towards my gate it seems to trigger a neighbouring gate (as I temporarily point towards it) and this neighbouring gate continues to stay animated whereas my target gate stays blank until finally the 'too far' animation occurs.

I don't recall this happening under v2.1.7 and I wonder whether it has been introduced by the update to prevent multiple marshallers being seen? It looks like the wrong gate is coming into range and being triggered a my nose points towards it, and this prevents my target gate from being triggered even though it is closer? (although the 'too far' animation does happen, and is accurate in that I have gone just beyond the parking line).

There's no point in posting the full log.txt, but here is the relevant section as I go to dock nd call the jetway (which works fine):

[15.46.32] [sam:debug] ObjectStore: Registering new object at 52.30861714109998 / 4.766139632223625 / 359.7893992960453 (lat)
[15.46.47] [xp] 4:35:44.021 xPilot/XPMP2 DEBUG Aircraft.cpp:569/DestroyInstances: Aircraft 0x00006A: Instance destroyed
[15.47.20] [xp] 4:36:11.227 I/TEX: Target scale moved to 2.000000
[15.47.20] [xp] 4:36:17.510 xPilot/XPMP2 DEBUG Aircraft.cpp:569/DestroyInstances: Aircraft 0x00006B: Instance destroyed
[15.47.27] [sam:info] Weather data loaded successfully
[15.47.27] [sam:info] ActiveSky replied with: EHAM 111525Z 24017KT 9999 FEW022 BKN028 07/02 Q1012 NOSIG 
[15.47.27] [sam:debug] Weather Data : 111525Z 24017KT 9999 FEW022 BKN028 07/02 Q1012 NOSIG
[15.47.28] [xp] [AOS] [2021-01-11.15:47:27] :> ActiveSky replied with: EHAM 111525Z 24017KT 9999 FEW022 BKN028 07/02 Q1012 NOSIG
[15.47.30] [sam:info] User connecting to jetway Jetway (anim=true)
[15.47.31] [sam:debug] Created sound source 1 for buffer 1
[15.47.31] [sam:debug] Playing sound source 1
[15.47.58] [sam:debug] Fading out sound source 1
[15.47.59] [sam:debug] Destroying sound source 1

I've checked in WED and the new object above does not correspond to either my target safegate or the neighbouring one that was triggered, nor to any position my aircraft would have been in.

Link to comment
Share on other sites

Hi Marten.  I first noticed this approaching D52 via A9. As I pulled abeam D52 and started to turn in, D48 came alive and D52 stayed dark until I'd overshot the line. 

I'd noticed the thing with marshallers popping up late so I like the extended draw distance in principal...we just need to maybe use the bearing from the parking spot as part of the equation? 


Link to comment
Share on other sites

OK. Probably just needs tweaking to find the best balance then. I don't think EHAM will be much different from most other large airports. The guidance units seem to be mostly 40-50m from the parking spots and aircraft will approach them on a perpendicular taxi line then turn in, potentially sweeping through neighbouring 'cones'? In my EHAM case the impression I got was that once D48 was active it stayed active even once I was clearly better aligned with D52. It's a maths problem... Which I'm no good at! Would be great if you can take a look at whether it's a more common issue and whether it can be fine tuned in a future update. 

Link to comment
Share on other sites

Just a thought on this... Is aircraft heading part of the equation? In my example, when I was coming abeam D52 and about to turn on I must have been closer to D52 than D48, even though their +-45 cones will overlap. But as I turned right onto the stand D48 passed through my 12 o'clock while D52 would have been between 1-2 o'clock. 

In other words, I was heading 'towards' D48, and within its detection cone, before I was heading 'towards' D52, even though I was closer in a straight line to D52. 


Link to comment
Share on other sites

Thank you. It is the default EHAM scenery downloaded from the gateway into WED, where I have added the Safegates on Piers C and D (where my VA fly from) and some marshallers on the stands on Pier C that don't have Safegate docking.

As a side-issue, I flew out from Gate C8 this evening and the info from my FP (EOBT etc) only appeared once I started pushback despite being accurate in the SAM dialogue box throughout my preflight setup. 

+52+004.dsf apt.cache apt.dat earth.wed.bak.xml earth.wed.xml sam.xml validation_report.txt

Link to comment
Share on other sites

I am experiencing the same issue since the 2.1.8 update with the marshaller one stand further away activating when turning into a stand on my own EBCI scenery (https://forums.x-plane.org/index.php?/files/file/62144-ebci-charleroi-brussels-south/)... I guess that with the extended detection distance the pretty much in front positioned nose wheel of the A321 swings beyond the center line between the two neighboring positions during the 90 degree turn which activates the wrong marshaller... It would be good to be able to set the detection distance on a scenery basis.

Link to comment
Share on other sites

Thanks @Papickx... Good to know I'm not dreaming it. It is going to be hard to find the sweet spot as pairs of neighbouring gates will be different distances apart.  My suggestion would be to narrow the detection 'cones'. Start with +-15 degrees and keep expanding till it becomes unreliable. 


Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Don't have an account?

    An account is required to interact with and download content from the Threshold Forum.
    Forum is currently also locked down for guests because of heavy bot invasions. Sorry about that.

  • Threshold News

  • image.png.5d3ebd5638179a05dc5cfa67eaf4bf3a.png

  • Create New...

Important Information

Please read the Terms of Use