Pushback-triggered error state

[leftos]

I've had this happen numerous times now, where at airports (mostly during icing conditions), as soon as I unset the parking brake, I get the "Commencing Push" line, immediately followed up with "You must set parking brakes to request ground services". I notice that the GSX toolbar icon now appears to be deactivated, without me touching it, and Ctrl+Shift+F12 doesn't bring up the GSX toolbar. The pushback flow continues fine, and when the end position is reached I get the "set parking brakes" call-out. Once I set them, however, the toolbar doesn't come up to allow me to confirm a good engine start. If I click on the GSX icon in the MSFS toolbar, I get the gate selection main menu, instead of the pushback submenu I'd expect. The nose wheel remains locked, and the pushback tug doesn't disconnect. At that point, my only option is to Restart Couatl, at which point it realizes that there's a bad half-done pushback state active, and it unlocks the nose wheel and repositions the aircraft in the same position, at which point I can continue with taxi.

This issue predates the wingwalkers release, for what it's worth.

Two logs from two separate instances attached.

P.S. .log extension isn't allowed as an attachment? Seriously? lol

[Captain Kevin]

You'll want to ZIP the log file and post the ZIP file.

[leftos]

Well, I just renamed them to add a .txt extension, and attached them both that way.

[Captain Kevin]

The problem with doing it that way is the forum could mess up the text formatting, which won't be helpful.

[leftos]

Any updates on this?

[Captain Kevin]

First of all, did you read the part where I said attaching it to the forum as a text file could cause the forum to mess up the text formatting of the log files, which won't be helpful.

[leftos]

First of all, did you read the part where I said attaching it to the forum as a text file could cause the forum to mess up the text formatting of the log files, which won't be helpful.

Yes, I did, and I downloaded the attachments from the OP and checked the formatting, and it was fine, just to make sure. Did you?

Here they are, again, zipped.

[Captain Kevin]

Yes, I did, and I downloaded the attachments from the OP and checked the formatting, and it was fine, just to make sure. Did you?

I'm not tech support. I don't know what the formatting itself is supposed to look like. All I know is in the past, Umberto has said that attaching it directly as a text file has messed up the formatting, which is why he tells people to put it in a ZIP file and attach it that way.

[virtuali]

I don't see any errors in your log file, other than GSX asking you to release parking brakes to continue. Of course, proper parking brakes detection requires:

- the parking brakes *are* set by the airplane

- if the airplane uses a non-standard parking brake system (possibly using a custom variable), it must be set correctly in the airplane customization page, as explained in the manual, Page 75, the Parking Brakes Test paragraph.

[leftos]

Same aircraft every time. Same livery every time. It happens once every ten pushbacks. Fenix A320 IAE United livery. This doesn't feel like a matter of how the parking brake works. And the fact that there's no errors in the logs could just as well mean that there's not enough logging for the error to be forensically analyzed.

Please read the log again. There's no timestamps in the log, no idea why, but here goes:

emulateText_MSFS [GSX] Release parking brakes 2.0
MSFS always use CheckIcingConditionsSimple() + surface condition
Icing test =  0 19.380279541 False
emulateText_MSFS [GSX] Commencing push. All engines clear. Start at will 2.0
emulateText_MSFS [GSX] You need to set Parking Brakes or Parking Brakes to request ground services 6

Why am I being told that I need to SET parking brakes to request ground services the moment I RELEASE them as instructed in order for the pushback to start?

Again, as shown in the logs:
I'm asked to release parking brakes. I do so. I'm told that push is commencing. It is. And less than a second later, I get a repeated message that I need to set parking brakes to request ground services. I'm not trying to request ground services. I'm in the middle of pushback. The message is literally heard just as the tug begins to push back the plane. It's clearly an error state. Which is validated by the fact that as soon as this happens, the GSX toolbar appears to have turned itself off without me clicking it off, and I get no prompt to confirm a good engine start. I've already said all of that in the very first post, but I'll quote it here again:

I notice that the GSX toolbar icon now appears to be deactivated, without me touching it, and Ctrl+Shift+F12 doesn't bring up the GSX toolbar. The pushback flow continues fine, and when the end position is reached I get the "set parking brakes" call-out. Once I set them, however, the toolbar doesn't come up to allow me to confirm a good engine start. If I click on the GSX icon in the MSFS toolbar, I get the gate selection main menu, instead of the pushback submenu I'd expect. The nose wheel remains locked, and the pushback tug doesn't disconnect. At that point, my only option is to Restart Couatl, at which point it realizes that there's a bad half-done pushback state active, and it unlocks the nose wheel and repositions the aircraft in the same position, at which point I can continue with taxi.

[virtuali]

Why am I being told that I need to SET parking brakes to request ground services the moment I RELEASE them as instructed in order for the pushback to start?

You shouldn't, and in fact I cannot replicate it, and I use the Fenix quite a bit. It looks like as if something (another app ? The Fenix automation ? ) called the GSX menu immediately before you got clearance to release brakes.

As I've said, I cannot replicate it, so check all apps that might possibly automate GSX. And be sure there are no double-commands being sent when operating the brakes either.