Noel

I discovered how to avoid the need to hit Continue Pushback and here it is: during the time when the tow connects to the plane and you are starting to wait for the Direction menu to appear one can hit the hotkey to bring up another menu which offers the user the option to Interrupt Pushback. If you choose NO to this option, invariably now the Direction menu appears. If I don't do this step, then must use the Continue Pushback option. Cheers

I just checked on SLC's Discord channel about this issue of needing to hit Continue Pushback because the Direction menu does not spontaneously appear like you think it should. I just posted this yesterday and here is the response from two who responded--the first one is the developer of SLC, the second another SLC user that confirmed what I experience: FPVSteve — Yesterday at 9:19 AM ...I've noticed too. It happens even without SLC running. So the developer notes it's not SLC that is the culprit.

I know for a fact that I don't CLOSE the GSX menu from the MSFS toolbar. And I also know for a fact the direction menu does not appear spontaneously--it certainly used to half the time, but not now. After the tow just connected at ENBR in the Fenix 320 I waited a good 60 seconds after the announcement that the pin was inserted, and no direction menu, so 'unhid' the GSX menu and used the Continue Pushback button. This only suggests to me you're yet aware of how this can misfire, which you admit to here: "Now, why it doesn't for you (and from your description it seems "random") ? No idea, I doubt it's another add-on..." I don't use the MSFS EFB so that's out. I guess the only solution for me is to just wait until the main menu shows the Continue Pushback option and proceed from there. It's messy though because once again, you have to wait until that menu offering Continue appears because if I 'unhide' the menu too quickly then I'm presented with the option to Interrupt pushback, which we don't want to do of course. Sometimes I end up doing this a few times until finally the Continue option appears.

The over and over part is the fact that I never close the menu using the MSFS toolbar. I think you are saying 'hiding' an open menu is done by using the hotkeys or perhaps hitting the X on the upper right part of the GSX menu, whereas 'closing' the menu happens when you use the MSFS toolbar to turn OFF the menu, correct? Just understand I NEVER close the menu using the MSFS toolbar. To be clear, when you refer to the 'toolbar menu', are you referring to the MSFS toolbar at the top of the screen? What is the GSX EFB app? I do use the newly formatted pretty GSX menu if that's what the 'EFB' is. As for 'random', no it's really 90+% of the time regardless of which of 5 planes I am using, that the Direction menu does not appear automatically. I can say once, recently, when the GSX menu option to Interrupt Pushback appeared, I hit the X button on it to close the menu before it timed out, and then the Direction menu did appear a little later if I recall correctly. So obviously we are doing something different and I still can't tell what it is. I will do a video soon to show you what I'm doing and will include SLC so you can see how it interacts.

This is where you and I disconnect as I've said this over and over. No, I'm not forgetting how I closed the menu, please. Once again, I NEVER close it from the toolbar. I only use the toolbar to open GSX initially, and after that, never touch it again, period. There is a possibility perhaps Self Loading Cargo is playing a role in this? Right now, SLC which integrates fairly well with GSX, will display a message to this effect: Wait until GSX displays the menu for you to choose a pushback direction and wait until told to release parking brakes. I'm paraphrasing but that is the basic message. Is it possible it is interfering somehow w/ GSX in this regard? When this message appears in SLC, this is when I will sit and wait. 30 seconds goes by, no direction menu appears. I use the hot keys to open the GSX menu only to see the menu offering an option to Interrupt pushback, which I ignore. At that point I hit the keys to close that menu, wait another 15 seconds, try again, and this time the full menu w/ option to Continue appears, after which the direction menu finally appears. I'm pretty sure now that this has to do with SLC and perhaps you're not familiar with it and how it interacts with GSX. Next time up as a test I will not start SLC and see if this changes the behavior. Cheers

Thanks for that. I was aware of the timeout and have played around with the maximum, 120 seconds, and recently put it back to default. The issue is that when the tow connects I never know whether the pushback option panel will automatically appear, or whether I need to reopen the menu to hit Continue. Previously, most of the time it would appear, now it virtually never does automatically appear, necessitating this extra step. As you know, until enough time has passed opening the menu will not offer the Continue option. So it's just kind of messy. Is there any process I can follow to avoid the need to open the menu to hit Continue? By the way, thank you for making the pushback walker stop when I choose to cut the straight pushback short. Cheers

GSX Users: do you find you have to choose 'Continue Pushback' after the tow is connected? I find 90% of the time now it never presents w/ the panel of pushback options the user is to choose from, without opening the GSX menu and choosing Continue Pushback, after which immediately the pushback options panel appears. Umberto insists this has to do with opening the menu on the Toolbar, but I never do that except for the very first time in a flight because the hot keys do not work until it's done once. This is a useless annoyance here. It might be possible it's because I'm using Self Loading Cargo but that seems odd because I would assume SLC just reads what GSX is doing, and GSX would not be waiting for responses from SLC.

What exactly is that? Some planes just have dim VC's and I used to use GFE filters to help there but since using NV DLSS FG the filters don't work for me. What is a cockpit light mod and is it for any plane?

I'm still puzzled by something. I create a new Tower view location on the map, set its elevation above ground, name it, then click SAVE. When I select the Spotties button, the saved location is indeed there. But....its elevation isn't it's back on the ground, that is to say when I chose the TOWER button and CAM, it's back on the ground. I'm pretty sure I'm using the latest version of Spotty26, 1.5.1. Do I have to select a particular tower location? For example let's I save a location at KDEN. I now start a new flight at KLAS to KDEN. As I arrive into KDEN, is there a way to make that saved tower work, I mean hitting TOWER and CAM should bring it up, no? Does it sense proximity and chose the saved tower location closet to the plane?

I did a x-country motorcycle trip in 2016, and we took off from coastal California, headed thru the Sierras to Las Vegas then St George UT, and just loved Canyonlands after Zion. I live in the Front Range area near Denver and really love a good part of the Colorado Plateau, which is on fire right now 😬

I of course can manage my own descent but when ATC tells you to descend to X and MAINTAIN? It's just leaving you hanging, waiting for the release from maintaining a specific altitude you were instructed to descend to. Yes, it works fine sometimes but again, 113 miles out and it asks me if I can see the field in sight? And frequently when mountains are involved it's just pathetic. Not always, but way too often. And to not have error traps that prevent ATC from asking you if you can see the field 113 miles out? I don't get it.

I am stunned by how bad vectoring is in BATC. Any time mountains are involved it's just worthless and more often than not I just close it down. Just now, flight from KDEN to KPVU in the MAX 8 it tells me to descend and MAINTAIN 28K feet and never says another word re descent. So we're now 37 miles out and it asks me if I can see the field in sight. The other day on a different flight it asks me this when I'm 113 miles from arrival. I swear they are LOST IN SPACE when it comes to even this basic business. They get the grand prize for stellar UI and audio, but in terms of basic ATC?

Fenix A320 as I find it friendliest to hand-fly, works perfectly with GSX and with Self Loading Cargo, has the best set of liveries for my needs, whereas the others in my fleet have a few quirks to deal with. TBH they're all great though but for 'only keeping one' it would have to be Fenix.

Mikael, I notice when I use the "Close All Doors" option the doors close to the plane, but the EFB still displays RED status of left front and back doors, and cargo doors that I was closing after passenger loading. I assume it's not supposed to do that so letting you know. Cheers and Thanks Also, please consider using the External model for the MAX, instead of the VC interior. Because of this, the very nice app, Spotty26, displays the MAX in a corrupted view. They state the reason the MAX does this is because the VC interior model does not play well with the new Camera SDK which is what they are using to bring FlyBy and Tower and other views back to users for a very reasonable cost. All my other planes display Flyby sequences very well, except for the MAX because of this issue:

Malcolm, You said this started recently essentially which I assume implies it was running okay prior to lately. The giant elephant in the PC is that it freezes outright, not just MSFS failing or locking up. At this point my bet is it is absolutely hardware related--possibly temperature related. Are you monitoring CPU temp? If not, that would be my next move. As a short-term test, if you haven't already, blow out your PC case completely, then leave the side cover off and aim a fan on lower speed direct into it. If that doesn't improve things do a memory test next. Your issue is not MSFS per se, though it is causing the issue to manifest. If you discover memory test and CPU/GPU temps are fine the next step would be a complete reinstall of Win 11 and MSFS.