P3D 5.1 hangs on shutdown with gsx services running

[p3dx3]

P3D 5.1 hangs on exit when I park and deboard. a prepar3d.cfg.txt is created to show a crash.
I think that when I load in the sim and request pushback without any services, fly, land, request deboarding, it hangs p3d on exit.

[p3dx3]

second flight
No hang on exit!
Because I restarted gsx after landing and requested deboarding.
It worked

[virtuali]

As explained so many times, GSX cannot possibly "hang" the sim, because it runs entirely separate from it.

Instead, there's a known bug in the P3D 5.1 new Simconnect Html menu, which hangs by itself, without this having anything to do with GSX, but can easily mislead users assuming it's GSX's fault, because users always associate what is really the "Simconnect menu", to be the "GSX menu", but of course the problem happens with every add-on that use it, and even with the default ATC window, it's just that opening it from GSX is done more often, so the chance the menu will hang is higher with GSX, just because you call it more often.

Some users reported that switching to the previous Scaleform-based menu, will fix the menu hangup.

[p3dx3]

As explained so many times, GSX cannot possibly "hang" the sim, because it runs entirely separate from it.

Instead, there's a known bug in the P3D 5.1 new Simconnect Html menu, which hangs by itself, without this having anything to do with GSX, but can easily mislead users assuming it's GSX's fault, because users always associate what is really the "Simconnect menu", to be the "GSX menu", but of course the problem happens with every add-on that use it, and even with the default ATC window, it's just that opening it from GSX is done more often, so the chance the menu will hang is higher with GSX, just because you call it more often.

Some users reported that switching to the previous Scaleform-based menu, will fix the menu hangup.

I am using the old window and it is hanging on exit. It almost 100% hangs only when NOT using gsx when I depart, like departing from a hard stand with no pushback required and I am rushing to fly I do not select any boarding, then I arrive at my destination and select deboarding, connect sode/gsx jetways. A while later I quit the sim and it hangs on exit. prepar3d.cfg.txt is created after p3d takes a long time to exit sometimes it is not shutting down itself.

[virtuali]

I am using the old window and it is hanging on exit. It almost 100% hangs only when NOT using gsx when I depart

Nothing that happens inside GSX can possibly hang the sim, since GSX is running entirely outside of it. But GSX is calling the menu and, while the "old menu" might not hang in game, like the new menu does, it doesn't mean the old menu is 100% reliable, because it's being phased out and it's there just because there are known issues with the new HTML menu.

[p3dx3]

I am using the old window and it is hanging on exit. It almost 100% hangs only when NOT using gsx when I depart

Nothing that happens inside GSX can possibly hang the sim, since GSX is running entirely outside of it. But GSX is calling the menu and, while the "old menu" might not hang in game, like the new menu does, it doesn't mean the old menu is 100% reliable, because it's being phased out and it's there just because there are known issues with the new HTML menu.

Did another flight, loaded in, no requesting of services just pushback, landed at destination and requested de-boarding. After finished, quit p3d. Sim hangs on close. prepar3d.cfg.txt created

[virtuali]

After finished, quit p3d. Sim hangs on close. prepar3d.cfg.txt created

You only said you used GSX, but that doesn't indicate GSX was the cause, you surely used other things, like an airplane or a scenery so why, exactly, this could an indication of GSX being the cause ?

And even if you uninstalled GSX and your crashes stopped, this also doesn't mean GSX was the cause because, as I already explained in my previous post, it's a known fact the new HTML menus sometimes hangs the sim so, GSX is not the cause other than the fact it use the Simconnect menu but, in this case, any other add-on using that menu could be affected so, it's up to LM to fix this, everytime something happens with the menu, people immediately put the blame on GSX, but it's always LM that fixes it in the end, it already happened many times and not a single time we had to patch GSX because of a bug in the Simconnect menu.