virtuali

Yes, it's exactly that, and is in fact very easy to fix. No, GSX 3d editor doesn't use the Slew mode camera, that would move your airplane too. It uses the standard Showcase/Drone camera and, by default, the arrow keys are assigned to some camera views. Just enter the MSFS control settings for the keyboard, filter by "Assigned" and look for the various functions assigned to the 4 arrow keys, and remove them all.

GSX only supports standard jetways which reads using the Simconnect Navdata API, it can't detect custom systems. It might be possible that, once we'll release the GSX multi-jetway update we might support other custom systems in addition to GSX own (the one that will be introduced with that update), but I can't promise they will because no work has been done to analyze the issue. Surely, GSX own multi-jetway system will work with every 3rd party airports that has standard jetways and, in most cases, will be able to use multi-jetways with no need to update the airport.

GSX reads the only thing that can read: the sim official variables for the engines. Some airplanes use a custom engine simulation that normally is supposed to sync their internal variables with the standard ones and sometimes they might fail to do that, or take longer than usual, especially when starting from a specific state (like cold and dark) so when you call GSX the standard variable (which is the only thing GSX can read) is still reporting the engines running but you might just open the menu again later and it would work, assuming the airplane completed its job properly in time.

Yes, this is in fact a bug, it doesn't work on first spawn but if you press shift+c twice, it works. Will be fixed in the next update, of course.

That's one method, but it's not the normal one and it's a side effect of the still unknown reason why on your system the direction menu doesn't auto-popup, which normally does if the toolbar menu is not completely closed.

You can't do it from the installer anymore, it's done only from the menu, by double-click on the hotkey in the menu, left of the gsx logo in the black band.

I checked again, with the Fenix, and it works as expected: If the GSX menu toolbar is closed (dark icon), the pushback direction won't pop-up, which is normal and is as it always was If the GSX menu toolbar is only hidden (light icon), the pushback direction pops-out automatically, exactly as it always was. I'll see if we can use the same method to make the hotfix work with the menu closed, to pop-up menus, but I can't say right now if it's possible.

It's installed automatically, you must have the current GSX update. Of course, if you use an airplane with a custom EFB, you must open the 2d version of the EFB and it won't show in the airplane 3d EFB like it does with planes using the standard EFB. However, integrating the GSX menu in a custom EFB is so criminally easy (as in a couple of lines of code, since all the work is done by the GSX remote web server), that I expect every developer using a custom EFB would add a GSX page shortly.

You can say it "over and over" but, it doesn't change the fact: GSX opens pop-up menus automatically when the toolbar menu is hidden (not closed) GSX won't open pop-up menus automatically when the toolbar is closed (not just hidden) This is exactly as before. The ONLY major change from previous version is that now, the hotkey would always work, even if it's fully closed but pop-up menus would still require the menu to be just hidden, not closed. Of course I re-checked it again and again just to be 100% sure, because before posting anything, especially in reply to someone reported a possible bug, I always verify first. So yes, I can confirm that, if the menu is only hidden (not closed), the Pushback direction pop-up comes out automatically, exactly like it always did. Now, why it doesn't for you (and from your description it seems "random") ? No idea, I doubt it's another add-on. If GSX crashed that might happen, but I guess you would realize if it crashed. Note that, if you open the GSX EFB app, the toolbar menu WILL be closed (completely) from GSX itself, this is of course normal and intentional, so you won't have the normal menu pop-up together with the same menu in the EFB each time you act on the EFB version of the menu so yes, in this case, it's GSX that would auto-close entirely its menu, for good reason.

It will always open automatically if you didn't closed it from the Toolbar. Nothing changed from before. It will still open automatically if you didn't close from the Toolbar, and it won't open automatically if you closed it from the Toolbar, there's nothing "random" about it. If your airplane uses the standard EFB, I suggest using the menu from that, it's completely removes any of these doubts caused by not remembering how you closed it last time. That's not correct either. If you close the direction menu before the timeout expires, you would always get the Continue option when you opened it again.

Maybe I should clarify menu usage better: ALL menus have an automatic TIMEOUT, which changes depending on context, longer for normal commands (default 30s) and much shorter for things that you might also want to skip without confirmation, like the operator selection. This means, if you open the menu and don't do anything for more than the timeout time, the menu will hide and you'll have to open it again and, in case of the Pushback, you'll use the Continue pushback option, to continue where you left. What changes is HOW you re-open it: with PREVIOUS version, before the EFB update came out, IF you closed the menu from the Toolbar instead of the Hotkey, you had to open it again from the Toolbar, because the hotkey didn't work after the menu was closed from the Toolbar. AFTER the EFB update, the hotkey works even if the menu is closed, that's the main difference but, if you let the timeout expire you would still have to open the menu to CONTINUE.

I suggest you look at the native flightsim.to integration in GSX, in the Additional Services: It comes with an integrated browser for flightsim.to and downloads, uncompress and installs a profile Before a profile is installed, it will check all its parking spots against the data GSX has loaded from the actual airport, and offer a reports about the profile, with how many parking spots are matching. Based on the matching report, you can decide to install it or not. If it's reported as a Perfect match, you can be sure the profile is good to be used for that airport. If you see lots of parking spots not matching, it's possible the profile might not be good for the airport, either because the scenery has been updated (common when the airport has a 2020 version and a 2024 version), or because it might have been made for a completely different version of the same airport. If you accept to install it, the profile will be loaded by GSX automatically without even a restart of GSX All of these inside the simulator, without interrupting a session, no restarts required at any time.

Could be you are using the menu in the wrong way ( closing it from the toolbar instead with the hotkey ), so the menu is disabled, and you don't see what GSX is trying to tell you, which would be the confirmation for a good engine start, that normally comes out as a menu after pushback, but if you closed the menu, you'll lose all the subsequent pop-up and text messages, so you don't know what GSX is waiting for. A complete explanation of this, with all the reasons and suggested workflow, starts a Page 113 of the Manual, the chapter named The GSX Toolbar Menu

But you still have either FSX or P3D installed (or at least their keys still in the registry) , and the installer can't possibly decide if you are still using any of these, it only checks that, if you have either FSX or P3D still installed, you must install SODE or update it if it's too old. When you got that message, the installer used to open the SODE website, but this function has been removed because the SODE website has been down for a while so, it's up to you find a downloaded version, which you had.

Of course it was installed. Or, more likely: you had very old version which you haven't uninstalled correctly, so the SODE registry key was still in your registry, so the Installer that checks everything that can possibly cause issues, as alerted you to either remove it or upgrade it.