GSX is causing auto-teleport to not quite the gate

[pinksunshine]

Hi, I thought it was only a problem for the FSDT KORD but it happened also at iBlueYonder KDAL and Drzewiecki Design KDCA. At KORD and KDCA, when I selected a gate and asked for follow me (to save the gate because it won't save if i just used "show me this gate" ) it instantly teleported me to the not quite the gate but near it, without clicking on anything else. And it teleported the aircraft halfway through the ground. When I tried restarting coautl the sim froze.

At DCA, I didn't even pick a gate. It just teleported me to a similar situation during approach. Pretty damn annoying and I hope there's a solution to this.

I only choose to get the follow me car because if I don't my gate selection doesn't get retained and i have to choose it over and over again.

[virtuali]

I can't reproduce what you are reporting. Is it possible you have some other add-on or control or device that might send numeric key presses automatically, so a menu entry gets selected for that reason ?

[pinksunshine]

OK, I tested flying to a random airport but during cruise I closed couatl to avoid the random teleports. I don't think I have anything that's doing key inputs that somehow trigger GSX. Anyway, after landing, I started couatl again and it crashed MSFS. Not sure what's going on, they all seem to be related to couatl. These teleports happen so randomly I can't even draw a pattern, but it's always the same behavior. It seems to have started after the 2.7.2 update.

And the teleport behavior -- it is as if my plane is getting dragged along with all the other objects that need to be at the gate (marshaller, vehicles, etc.)

Is there a way to disable the "Warp me there" feature? I don't use it. Even if it's a hack-y solution.

[virtuali]

The Couatl program, being an external .EXE CANNOT crash the sim, it's just not possible.

However, there's an acknowledged bug in the SU12 Navdata API, which seems to crash the sim sometimes. This has been confirmed in the SU13 Beta release notes, and it's should be fixed in the final release, and since GSX clearly must use the Navdata API to query the airport, you can be easily mislead "Couatl crashed the sim", when the problem is the sim crashed by itself because of this bug.

Since nobody ever reported that automatic warp before, I can't offer you any solution about this, other than the one I already suggested: checking nothing (even an unused joystick) is sending key presses when the GSX menu is open.

[pinksunshine]

It happened again, this time at Am Sim KSEA. All I did was request a Follow Me to save my gate selection after landing. And again, after I chose to restart couatl the sim froze. This seems to only happen when I am using GSX.

[pinksunshine]

dev mode relevant logs:
glTFLoader | Could not merge animation file 'vfs://fsdreamteam-gsx-world-of-jetways/SimObjects/GroundVehicles/FSDT_Tug_660/animation/animation.gltf'.
glTFLoader | Could not merge animation file 'vfs://fsdreamteam-gsx-world-of-jetways/SimObjects/GroundVehicles/FSDT_Tug_660/animation/animation.gltf'.
Loading: 'vfs://fsdreamteam-gsx-pro/SimObjects/GroundVehicles/FSDT_Baggage_Loader_Man/model.02/FSDT_Baggage_Loader_Man_LOD3.gltf'
Loading failed: unsupported file extension: ''

[pinksunshine]

OK -- I think it is kinda related to the Jetway API. Jetways have not loaded yet for that airport but I don't know why it would teleport the plane instead of a CTD.

And the KDCA issue where it just teleports during approach, I still have no clue what's causing it. Only happens when GSX is installed.

[virtuali]

The dev mode console messages are completely harmless, if you had to take them seriously, I'm sure you'll find thousands of "errors" in default airplanes, that doesn't automatically mean there's a problem.

In some cases, we intentionally don't animate distant LODs, and this is allowed and is not a problem, even if it's reported on the dev mode console, because it might not be done on purpose, so the console alerts it anyway.

An issue with the Jetway API would just prevent GSX to recognize jetways, but I can't see how it could cause a random teleport, especially when you haven't explicitly selected the "Warp me" feature. Again, I can't reproduce it, and nobody ever reported something similar.

[pinksunshine]

I have the coautl log for the latest occurrence.  Would you like me to send it to you?
It had a lot of these errors. I have the rest of the couautl.log file but I can't attach it due to ancient forum limits. Perhaps this issue hasn't been reported much because people don't really use it as much either?

requestJetwayData Internal error (dwIndex == 99)
completeJetwayData DONE
onEnteredAirport KSNA
Error: exception JETWAY_DATA in call RequestJetwayData param #99 'KSNA'
{'Airport': 'KSNA', 'Requested assistance services at': 'None 22', 'User Pos': (33.72015952804962, -117.8406856444381, 282.947 m, 260.103 m, 208.92079256984056, -0.008009836077690125, 0.024434609338641167, 0.012385746024442226, 2.553919111633301, 0.0)}
Retrying to request jetway data one by one...
parkingIndex 0

FSDT_GSX_SetGate 10 20 0
17.71 m 24.2211 m
17.71 m 24.2211 m
17.71 m 24.2235 m
17.71 m 24.2235 m
17.71 m 24.2235 m
17.71 m 24.2235 m
GSX SimStop
17.71 m 24.2243 m
Error: exception DATA_ERROR in call SetDataOnSimObject param #1 '-125748368'
{'Airport': '10CL', 'Requested assistance services at': 'None 22', 'User Pos': (33.674141994815244, -117.86646637418286, 15.3068 m, 2.49235 m, 28.119934248869807, 0.021237269043922424, 0.024434609338641167, -0.004743392143934591, 2.553919111633301, 1.0)}
Error: exception DATA_ERROR in call SetDataOnSimObject param #1 '-125749424'

emulateText_MSFS [GSX] A marshaller has been dispatched on site. FollowMe vehicle is on its way 6
Error: exception DATA_ERROR in call SetDataOnSimObject param #1 '-159390656'
{'Requested FollowMe to': 'Gate 20', 'Airport': '10CL', 'Requested assistance services at': 'None 22', 'User Pos': (33.675124490874076, -117.8647135513735, 0 m, 0 m, 297.008739509695, 0.0, 0.024434609338641167, 0.0, 2.553919111633301, 1.0)}

Error: exception UNRECOGNIZED_ID in call AIRemoveObject param #1 '0'
{'Requested FollowMe to': 'Gate 20', 'Airport': '10CL', 'Requested assistance services at': 'None 22', 'User Pos': (33.667820535947286, -117.87015537586078, 0 m, 0 m, 271.91457868296794, 0.0, 0.024434609338641167, 0.0, 2.553919111633301, 0.0)}

[virtuali]

It had a lot of these errors. I have the rest of the couautl.log file but I can't attach it due to ancient forum limits.

You can't attach it because "ancient forum limits" but, instead, because you MUST ZIP and ATTACH it and the reason why you must, is that the log file might be altered if it was posted as text as maybe you wanted to do ( not even considering the incredibly annoyingly long post you would create this way ) and to prevent it to be altered (for example changing some sequence letters into smiley faces, which is what the forum software would do if you posted it as a post ), you should use the proper function to attach files, that is the "Attachments" feature, and ZIP the log before attaching it.

Perhaps this issue hasn't been reported much because people don't really use it as much either?

People use it at lot but that's not really the issue. Whenever somebody reports a problem, you can be sure we tested it before replying it.

requestJetwayData Internal error (dwIndex == 99)

This is the main cause of the problem, and it's an internal Simconnect error that doesn't have anything to do with GSX, it's basically a "panic" message, when the Navdata API is used by GSX to query about the airport jetways. When this error happens, not only GSX doesn't get the list of jetways, but the whole Simconnect API start to throw errors regardless what we do with it.

According to Asobo, in the SU13 Beta release notes, this should have been fixed, although we'll never know for sure until it will be out to all users.

Because, a possible reason for this to be happening, is using too many add-ons that send too many commands to the sim in a very short time, up to the point Simconnect breaks. The same can be caused by having reached the maximum limit of Simobjects in the sim, currently documented at 1000.

As explained so many times in the forum and everywhere else when asked, there isn't a single culprit for reaching the max objects limit in the sim: all add-ons you have contribute a bit to it, even if a single one might not be able to reach it, using several all together will so, your only option is to use whatever options each add-on gives you to keep the number of objects under control, for example lowering AI density if you use an AI generation product.

From GSX, you have the following options that will help limiting GSX own contribution to the number of objects in a scene, and are:

- The Passenger Density slider. The higher the settings, the more objects you'll see at the same time.

- The Extra Clutter option in the GSX Config page. This will help only on default airports where GSX jetways replacement files are used ( on non-default airports, you should always Disable GSX jetway replacements )

- If the airport has a custom GSX profile with many VGDS, the option to disable the VGDS static model in the profile Details page, will help as well.