Author Topic: "Interrupt pushback?" on landing  (Read 448 times)

westbros

  • Newbie
  • *
  • Posts: 18
"Interrupt pushback?" on landing
« on: January 17, 2025, 08:00:46 pm »
I have had this problem for the last few flights. This is in MSFS2020 using the Fenix. On landing when I want to select a gate GSX is asking me whether I want to interrupt pushback. I cannot get rid of this. Choosing to abort pushback doesn't help, and neither does restarting Couatl. It is impossible to get any GSX options for arrival. It is completely stuck on pushback. I have the latest version 3.3.2. Please advise.

Thanks.

kingnorris

  • Jr. Member
  • **
  • Posts: 81
Re: "Interrupt pushback?" on landing
« Reply #1 on: January 17, 2025, 09:55:27 pm »
I've had this happen before with my PMDG. I had to restart the Coatl and it worked. Don't know why it's not working for you. Definitely a bug though.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51949
    • VIRTUALI Sagl
Re: "Interrupt pushback?" on landing
« Reply #2 on: January 18, 2025, 02:40:28 pm »
There are two possible reasons for this:

- the Couatl engine crashed in flight, usually because of issues with the Navdata API or the Navdata itself. With the "Disable GSX in cruise" option, combined with the fact the GSX menu is automatically Disabled, will prevent GSX from making any queries to the Navdata API during flight, so it's very unlikely it will crash in flight, since it's not doing anything, other than checking if you would eventually descend under 10k feet. However, even if the unlikely event the engine will crash in flight, the auto-restarter should restart it automatically.

- in some very rare occasions, Simconnect itself might get stuck, usually because you exceeded the maximum number of Simobjects during flight, so it just stops responding. Sometimes this is fixed by restarting the Couatl engine, but in some even more rare occasion, it's not, because the max number of objects has been exceeded by too much, so it won't come back until the next flight.

westbros

  • Newbie
  • *
  • Posts: 18
Re: "Interrupt pushback?" on landing
« Reply #3 on: January 18, 2025, 11:28:28 pm »
Thanks for your reply. However this issue has only appeared the last few weeks, which may well coincide with version 3.3.2. It has never been a problem before. My setup has not changed. I have no way of telling, but I assume my sim is generating the same amount of Simobjects as before. My guess is that this problem is a bug at your end.

There will be a new airac in the next few days. I will update to version 3.3.3 and see what happens.

virtuali

  • Administrator
  • Hero Member
  • *****
  • Posts: 51949
    • VIRTUALI Sagl
Re: "Interrupt pushback?" on landing
« Reply #4 on: January 19, 2025, 03:01:16 pm »
There will be a new airac in the next few days. I will update to version 3.3.3 and see what happens.

With "new airac" you mean default updated Navdata or Navigraph Navdata ? Because, those issues seems to be more frequent with Navigraph navdata.

I'm not saying it's Navigraph fault, but remember there was a brief time where the sim *crashed* because of a problem in the Navdata (it was two different issues, one in Navigraph, another in the default Navdata so yes, even default Navdata can have issues) and again I'm not saying it's Navigraph's fault, I'm just saying there's no "bug at our end", because while cruising (if the menu is Disabled and the "Disable in cruise" option is checked), GSX is not doing anything other than checking your position and speed, which a very simple and lightweight task that cannot be compared with the complex array of tasks and traffic that happens when operating ground services, the one and only interaction with the sim while cruising is either the (limited or null) Navdata interaction OR the chance that Simconnect might get stuck or return erratic results because of the max number of Simobjects reached during the flight.

Of course, the problem is not GSX-specific. We heard reports of add-ons like the Fenix (which I'm sure it's a very solid and well coded product) starting to behave strangely in flight, with auto-pilot disconnecting, airplane going almost out of control, see here:

https://www.avsim.com/forums/topic/662231-the-ultimate-fenix-vs-fslabs-a321-side-by-side-comparison/page/3/#findComment-5339750

Those symptoms looks like a Simconnect problem, getting stuck or returning erratic results, something similar to might happens with GSX: some kind of simulator bug that requires flying for a longer time to manifest itself.