GSX Crash at ORBX KSBA

[glc100o]

This happened today after SU12 update and GSX updated to latest version  2.4.0. Using PMDG 737-800.Landed, selected gate, taxied to gate, Marshaller guided me in, cut engines, and requested that the jetway be operated. Jetway connected but then got panic log display and had to restart Couatl  and deboarding completed successfully.

Log:

Running in mode: Microsoft Flight Simulator
Python 2.7.16 Stackless 3.1b3 060516 (default, Mar  9 2019, 21:32:11) [MSC v.1500 64 bit (AMD64)] wxPython 3.0.2.0
couatl v4.8 (build 5140)
Traceback (most recent call last):
  File ".\GSX\assistanceServices\jetwayOperations.py", line 422, in _trigger
Couatl.SimConnectRequestError: (3, "UNRECOGNIZED_ID in call RequestDataOnSimObject param #3 '303'")
{'Airport': 'KSBA', 'Requested parking services to': 'Gate 4A', 'User Pos': (34.42510567554521, -119.83721020042667, 5.25522 m, 2.47764 m, 115.72661193952203, 0.01776726171374321, 0.024434609338641167, 0.0, 2.553919111633301, 1.0)}

[virtuali]

Please do not post the log as part of the message but, as explained so many times, ZIP it and ATTACH it to a post.

This because I need to look at the whole actual file, uncut and with no risk of being translated in by the forum software, that's why you should ZIP it at Attach, instead of inserting it in a post as text.

[glc100o]

Will do next time!

Greg

[glc100o]

Here is another log.
MSFS SU12 with latest GSX Pro as above.
PMDG 737 800.
KSJC Default MSFS Airport
Gate 23

Landed, selected this gate. Using shortcut to GSX.
Was occupied, so selected in anyway and then went back and removed Aircraft with option 4. It disappeared.
Arrived at gate, Marshaller present with readout, successfully got into gate, stopped engines.
Pressed operate gateway, GSX Crashed with panic log. All GSX support  vehicles disappear.
Asked to restart Couatl,, replied Yes.
Had to restart GSX from Toolbar.
Asked to operate jetway, jetway wiggles end left and right and stops and does not advance to aircraft.
Asked to deboard, jet way full attaches and deboarding and then all proceeds normally.

[glc100o]

I used Live Updater and it  said afterwards the  version was up to date 2.4.0.
Just FYI.

[glc100o]

I ran the online updater, to be sure about the update, and recreated the flight at KSJC and had the crash when calling for deboarding. Unfortunately the panic log disappeared when I tried to save it.

[glc100o]

Found the log

[virtuali]

Found the log

Both your logs are quite strange. It seems GSX is getting bad data from Simconnect, even from doing the most basic things, like reading your position. Are you using some kind of AI Injection software maybe ?

Also, could you please try to download and install the Offline installer, so we can be sure you are not affected by getting some outdated files from your local Cloudflare node ?

[glc100o]

With the testing I did to supply the logs, I had used the offline installer to update GSX to 2.4.0.
I have been using FSIPanel, which allows one to spawn at an airport, and then choose an ILS approach,a Fix along the approach, and the aircraft is moved to that location and all the settings are programmed to spawn at the fix and just fly it. So is like starting at an airport and returning to it. Maybe that process is creating confusion for GSX Pro. GSX is on from the beginning. I wonder what would happen if I X it off and then restart GSX Pro after the aircraft has been transported to its location to fly the approach.

Greg

[virtuali]

Maybe that process is creating confusion for GSX Pro. GSX is on from the beginning. I wonder what would happen if I X it off and then restart GSX Pro after the aircraft has been transported to its location to fly the approach.

That's possible. And one of the reason why we designed this version to be Restarted on demand, from its Tray bar icon, because we couldn't possibly anticipate which kind of conflicts might happen. Strictly speaking, other than being able to pre-select a gate in flight, you might just decide to close the Couatl engine after departure, and start it again after landing.

[glc100o]

I will give that a try and report back.

Greg

[glc100o]

PMDG 737 800. Went back to KSJC default MSFS, spawned, Closed GSX and then ran  FSIPanel to reposition and then flew the approach. After landing,  Started GSX chose  gate 23 and started deboarding, and there was no crash. All the ground services were fine.So this works, when using FSIPanel.

But the passengers are walking in air to wrong gate. This was not happening before, and should not be happening with SU12.
Did offline update to 2.4.1 prior to this test.



Greg

[glc100o]

This is the log for this air walking event if of any benefit

Greg

[virtuali]

But the passengers are walking in air to wrong gate. This was not happening before, and should not be happening with SU12.

To be accurate, we should say "should not happen with SU12, provided the data we get from the API arrives and there are no conflicts".

In your case, there are many errors in your log, which I suspect might be caused by your custom .INI profile, maybe it was made for a different version of the scenery, which has been updated, so now the updated parking spots are not matching what you have in the GSX profile, so when we ask for jetways, they don't match what we have in the .INI, because the scenery has changed.

You can verify if this is the case, by opening the scenery customization page: if you see a message about mismatched parking spots, that was the problem, so you'll be asked to either create a new profile which will include only the parking spots matching, or if nothing matches, it will create a new profile from scratch.

[glc100o]

This is the default MSFS version of KSJC. It has no GSX Profile associated with it.
With essentially every gate, the marshaller and or digital readout was hidden behind the terminal walls, so I decided to move the Marshaller to 12 meters at Gate 23, and just use one gate, gate 23.
I am including the ini file that I found which reflects the customized Marshaller distance for this airport in the Virtuali folder. I assume that is the one you are referring to?
I am not familiar with the Scenery Customization Page or where to find it. I Use this program at a pretty basic level.
Maybe Asobo updated this airport, but I am not aware of that being the case.
Should I just delete the ini file and recustomize the marshaller distance?
Thanks,

Greg