Author Topic: GSX didn't recognize SODE jetway  (Read 1710 times)

RobertO1035

  • Newbie
  • *
  • Posts: 35
GSX didn't recognize SODE jetway
« on: October 01, 2018, 06:26:33 pm »
This is Flightbeam KPHX.  GSX didn't know there was a SODE jetway in place.  Is there any way to tell GSX when there is one there?

Thanks!

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: GSX didn't recognize SODE jetway
« Reply #1 on: October 01, 2018, 06:58:56 pm »
Are you using a custom GSX configuration for that airport ? The customization editor will tell if you do.

RobertO1035

  • Newbie
  • *
  • Posts: 35
Re: GSX didn't recognize SODE jetway
« Reply #2 on: October 02, 2018, 04:46:08 pm »
The customization drop down box for jetways states there are none for that parking position.  When I select 1 jetway, GSX inserts one of its own jetways, which I don't want).  I just want GSX to recognize the default SODE jetway.

Thanks!

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 50741
    • VIRTUALI Sagl
Re: GSX didn't recognize SODE jetway
« Reply #3 on: October 02, 2018, 11:26:23 pm »
I suggest asking Flightbeam about this.

I do recall that, at a certain point, SODE was updated to require a more strict naming convention for the jetways and the gate, and this caused a problem with some earlier sceneries made with SODE, which required a fix in their XML file.

GSX asks SODE for a list of its own jetways, it doesn't try to read any of the scenery files directly.

RobertO1035

  • Newbie
  • *
  • Posts: 35
Re: GSX didn't recognize SODE jetway
« Reply #4 on: October 02, 2018, 11:47:10 pm »
Thanks, Umberto!