FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: natoseigh on February 16, 2018, 12:54:40 am
-
Hello Umberto
for some reason since i updated to p3d v4.2 anytime i try to use the default command for the GSX menu to pop up,which is CTRL SHIFT F12 the menu pops up and automatically goes to deboarding when i havent even issued it a command for it,and the same happens when am done with catering and trying to start boarding it goes to deboarding or even when am trying to get the menu up to select push back it goes to deboarding,what do i do to fix this please?i have uninstalled GSX and reinstalled ,it still didnt solve the problem.
thank you
nathaniel
-
I think you are referring to this issue: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=128537
I have the same issue. @ Umberto, according to LM this is an issue of the developer?
-
I'm getting this as well. It's a super annoying bug.
-
Hi guys,
Glad i'm not the only one having this issue. Since installing 4.2 i'm getting it too. Its very annoying when trying to bring up the menu it automatically requests deboarding. Does anyone know if a fix? Is this a GSX bug?
-
This issue doesn't have anything to do with GSX, which doesn't require any updates.
The menu bug came up during the beta, and LM fixed it very quickly and, they said to developers it required a Content update, not that we had to update our apps to support changes to Simconnect, because there were none related to the menu, and after the fixed it, all affected apps (GSX, SODE, etc.) started to work again with no changes required on our part.
Could be that you upgrade to P3D 4.2 using just the Client ? If yes, try to update the Content as well. I always update P3D using the full installer, which might explain why I cannot see any issues.
-
This issue doesn't have anything to do with GSX, which doesn't require any updates.
The menu bug came up during the beta, and LM fixed it very quickly and, they said to developers it required a Content update, not that we had to update our apps to support changes to Simconnect, because there were none related to the menu, and after the fixed it, all affected apps (GSX, SODE, etc.) started to work again with no changes required on our part.
Could be that you upgrade to P3D 4.2 using just the Client ? If yes, try to update the Content as well. I always update P3D using the full installer, which might explain why I cannot see any issues.
Hey,
That is strange as this is a fresh install of P3D V4.2 - Is it possible to have anything to do with FSUIPC? As i have rolled back that version as people have reported issues with the latest.
-
That is strange as this is a fresh install of P3D V4.2 - Is it possible to have anything to do with FSUIPC? As i have rolled back that version as people have reported issues with the latest.
That's possible, I don't have FSUIPC installed, so I cannot say, but several people have posted issues with the very latest version of it, and went back to an earlier version.
-
That is strange as this is a fresh install of P3D V4.2 - Is it possible to have anything to do with FSUIPC? As i have rolled back that version as people have reported issues with the latest.
That's possible, I don't have FSUIPC installed, so I cannot say, but several people have posted issues with the very latest version of it, and went back to an earlier version.
Hmm, Well its good to know its not a GSX bug.. But is is so annoying that deboarding automatically starts lol - I guess i will have to wait for Pete to return from holiday and release a new FSUIPC. If that doesn't work its over to Lockheed.
-
Hi,
I also had these issues (auto selecting pushback direction, deboarding, gate selection etc.)
I'm not using FSUIPC for control bindings, just for the FSFX effects. After deleting it my text menus work again. Had v5.1.21 installed, some other users found 5.1.22 was working for them.
-
where did u get the version of FSUIPC?
-
Just to update a little bit. I have checked this issue with FSUIPC not installed and the problem remains. It doesn't seem to matter which versions are installed either.
I contacted Lockheed about it and they are saying that there is no issue there end... So this is becoming increasingly frustrating now.
-
This issue doesn't have anything to do with GSX, which doesn't require any updates.
The menu bug came up during the beta, and LM fixed it very quickly and, they said to developers it required a Content update, not that we had to update our apps to support changes to Simconnect, because there were none related to the menu, and after the fixed it, all affected apps (GSX, SODE, etc.) started to work again with no changes required on our part.
Could be that you upgrade to P3D 4.2 using just the Client ? If yes, try to update the Content as well. I always update P3D using the full installer, which might explain why I cannot see any issues.
This issue seems to be related to the last key press being stored and then when you open GSX it remembers that and executes it. See here: http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=128537&sid=b9406064f1a79a2df114bf5852f8c2b5&start=15 (http://www.prepar3d.com/forum/viewtopic.php?f=6312&t=128537&sid=b9406064f1a79a2df114bf5852f8c2b5&start=15)
You can replicate this easily by pressing 1 and then CTRL+F12 - GSX will start deboarding. Reset GSX and repeat with 2 and it will do catering etc etc. However, if you press 8 or 9 and then CTRL+F12, GSX crashes with a COUATL restart message (pic and log attached). So, whilst not strictly anything to do with GSX, it is getting tripped up by this problem.
-
Thanks for sharing the info. Hope it will be resolved soon. As a workaround I restart COUATL now manually...
-
So, whilst not strictly anything to do with GSX, it is getting tripped up by this problem.
Yes, after several more tests, it's 100% confirmed this is the case and, of course, it will affect every addon that use a menu, and there's just nothing we can do to fix this: only LM can do that.
Even the Sample application provided in the SDK is equally affected by this problem.
-
Solved by me by keep CTRL key pressed for around 5 seconds or more then use the combination of CTRL+F12.
-
i have the same issue, and yes by is also when i press 1-2-3-4 etc. and then open the GSX then is started what i have press bevor :)
The fix is i must wait 5-10sec. and then open GSX have i right ? :)
-
It seems the issue is if you want to press numerical keys (1-9) or something. But also affects Ctr+F12 for GSX menu. Until a solution will arrive, you can use this workaround. Keep pressing CTRL key and after few seconds press F12 (but don't free CTRL key during this) and the menu will stand. I'm using mouse cursor to choose options from the menu, not numerical keys.
-
I was just going to post about deboarding starting while boarding when trying to open GSX menu and have discovered this thread.
Glad I am not alone with this problem. As for P3Dv4.2, I have installed both Client and Content and my FSUIPC is an older version (as suggested by other users).
Since Umberto says it has nothing to do with GSX and is LM's bug, it looks like we will have to wait for a few months for P3Dv4.3.
Providing that, of course, LM does fix it. :-\
-
Since Umberto says it has nothing to do with GSX and is LM's bug, it looks like we will have to wait for a few months for P3Dv4.3.
Surely it's a P3D bug. It happens with each and every Simconnect application that has a menu, even with the sample provided in the SDK.
Note that, normally, nothing happens if you just restrain yourself from pressing a numeric key BEFORE opening the menu. Since the numeric keys, by default, are only used by the menu itself, this is not usually a problem.
The problems will start if you assign the numeric keys to some other addon so, each time this other addon sends a numeric key or you press it to trigger it, this will be buffered somewhere, and will auto-select the next Simconnect menu that will open. We initially assumed it was a problem of Chaseplane, because a users reported it started only when starting Chaseplane, and stopped when closing Chaseplane, but the real problem was that he assigned some of the numeric keys to Chaseplane views, so they were sent each time a new view was selected.
So, the best solution, until LM will fix it, is not use the numeric keys for any addons, which is the default. And don't press them manually...
I doubt we'll have to wait months for a new 4.3 version to get this fix, there will be likely an Hotfix which hopefully won't take long.
-
Umberto, thank you very much for your detailed answer.
One more question to make sure I get it right, okay?
the best solution, until LM will fix it, is not use the numeric keys for any addons, which is the default. And don't press them manually
Do you mean any numeric key (1-0) including the ones located over keyboard letters, or only keys from the right-side numeric keypad?
Because if the first one, these are usually used when using ATC, both default and some add-on ones like PRO-ATC/X.
-
First, should GSX really be crashing when a menu option that is out of range is input, even from a buggy keyboard message handler in P3D? Seems that it should do a range check and simply disregard out-of-range inputs rather than crashing when an errant value is received.
Second, would it be possible to add an option (configurable in couatl.ini, for example) for GSX menu selections to only be made with mouse clicks on the menu window, disregarding the number keys entirely? Seems that could bypass the current issue...and frankly, I'd like the ability to deconflict my number keys for other reasons as well.
One other thing...even if one does not press numeric keys before activating the menu, the panels may be doing that, particularly with door commands sent as emulated keypresses by the panel code as "Shift-E" followed by the door number.
Regards
Bob Scott
-
First, should GSX really be crashing when a menu option that is out of range is input, even from a buggy keyboard message handler in P3D? Seems that it should do a range check and simply disregard out-of-range inputs rather than crashing when an errant value is received.
There wasn't any need to do an "errant value check", because the NORMAL (non bugged) behavior for the Simconnect menu, has always been that, if a menu contains X entries, and you press a key outside its range, the key should not respond.
So yes, we could add such check, which will prevent the GSX error message, but it still won't remove the bug, so key event would still be registered when it shouldn't. IT IS A BUG.
Second, would it be possible to add an option (configurable in couatl.ini, for example) for GSX menu selections to only be made with mouse clicks on the menu window, disregarding the number keys entirely? Seems that could bypass the current issue...and frankly, I'd like the ability to deconflict my number keys for other reasons as well.
You are assuming we have some kind of control over the Simconnect menu. I'm highlighted in bold, to make sure you understand this is NOT a "GSX menu", it's the standard Simconnect menu, and applications don't have ANY control over how it works. The SIM handles BOTH they keyboard AND the mouse.
One other thing...even if one does not press numeric keys before activating the menu, the panels may be doing that, particularly with door commands sent as emulated keypresses by the panel code as "Shift-E" followed by the door number.
That's even more reason why it's urgent LM should fix this as soon as possible. There's no way for us to fix the automatic selection bug, because we cannot possibly know from GSX if the number selection was intentional or not.
I'll repeat it again: the same bug happens with *every* Simconnect application with a menu, including the Sample provided by LM in the SDK!