GSX caused the iFly MAX8 1.0.0 to crash due to being overstressed?!

[WebMaximus]

After I updated the iFly MAX8 to version 1.0.0, I just learned that something odd is happening over here.

I start the GSX services as normal (connect ground power, ask for fuel, catering and boarding). Everything starts normal with the GPU arriving and being connected, the fuel truck stops in the right position, catering arrives and the stairs are moved into position for the PAX to board. However, just at the same moment the aircraft doors start opening, I get the same message like you would get when overstressing the aircraft in flight as seen below.

Never had this happening to me before. I tried several times and same thing 3 times in a row. At that point, I had no choice but to leave GSX out of the picture for all services except for pushback which worked OK thankfully.

https://i.imgur.com/MaQ6OoV.jpg

[virtuali]

However, just at the same moment the aircraft doors start opening, I get the same message like you would get when overstressing the aircraft in flight as seen below.

Clearly not caused by GSX.

At NO TIME GSX ever changes, affect or touches the airplane status (any of its variables) except in ONE single moment: when you see the message about the Bypass Pin being connected. At that time, GSX freezes the airplane and takes control of it for the whole Pushback, and will release it when you'll see the message about the Bypass pin being attached.

This is the only time where GSX could theoretically affect the airplane. Anything out of the ordinary happening in other situations, is not caused by GSX.

If this doesn't happen without GSX, it doesn't mean it's caused by GSX either. It might be some kind of custom code running in the airplane that is doing something related to its own internal GSX automation, and it's not even granted it's completely caused by the airplane, some other add-on might interfere, like FS Realistic with the "Ambient Wind" feature, which should always be disabled.

[Captain Kevin]

Richard, if you have crash detection or any similar settings turned on, it would be better to disable them. Having them enabled has been known to cause issues, such as crashing into invisible holes in the scenery or flying a 14-hour flight only to crash into an invisible wall on short final. Really, you'd know if you slammed it in on the landing.

[WebMaximus]

Seems to be working OK today. This time in LIEO at gate 102 if that is of any importance. Last time when I had this issue, it was in LFLL at gate L11.

So either it was some off one-time issue (so I hope) or if there was something weird going on at that specific gate and that specific airport. Or if something changed in the latest version of GSX. Because I applied the latest update just before I started this flight.

I know crash detection can be switched OFF and in some cases like you mention for good reasons. However, I still can't help feeling a bit like I'm cheating having it like that and never used it/had it enabled. I guess if you're flying into many new places and in new areas, it might be more beneficial. In my case though, I only fly to a limited number of payware airports and then, I think it's fine having it enabled. Or at least it has been fine for the last few years until the other day when I had this weird issue.

Will keep my fingers crossed I won't see it again in the next couple of years.

[Captain Kevin]

I've seen weird issues happen with both freeware and payware airports like the issues I've mentioned.