Hi,

I've been experiencing this weird problem with gsx on P3Dv4.2 wherein every time i ask GSX to deboard, refuel, cater etc. and when everything's done I cant open the GSX menu again. I tried restarting the airport cache but i still cant open the menu. Whats causing this problem and is there a fix for this? I already sent an email to FSdreamteam but still no reponse.

Thanks,

Francis

Edited March 12, 20188 yr by francisp320

You don't need to send an email to support. Post on the GSX support forum here. Umberto provides very good support.

http://www.fsdreamteam.com/forum/index.php?board=50.0

Its a new issue since 4.2 came out. I had a similar issue too, so I hopped over the to FSDT forum and it seems there are lots of problems with the menu's at the moment.

 

If I recall correctly, according to the dev its a LM issue and there's not much he can do to fix it.

There is indeed 1 issue with v4.2 when selecting menu options by pressing keys on your Keyboard: the last pressed number key will be instantly "virtualy" pressed when you open the next window.

E.g.: Open ATC window and select an option pressing the requiered number on your KB -> open another window e.g ASPv4 or GSX (or whatever) Menu and instantly the same number get's choosen without you doing anything.

This issue is LM dependant! Nothing else that a 3rd party developer could do!

-> Workaround: select the options with your mouse!

Now I don't think that the OP has an issue with this because as he stated he can't open the menu! In the first case the menu will flash (show then dissapear) because the previously pressed key will be as an imput to GSX but if you press again Ctrl+F12, the menu will show up!

So I do guess that the OP has another issue than the known one.

This was driving me crazy, thought it was my keyboard but I saw no other application affected. Just pressing Ctr+F12 it would already select an option. Ran the live updater several times and no dice. Until LM releases a hotfix I'll just have to select it from the menu bar then.

9 hours ago, FrankSalo said:

This was driving me crazy, thought it was my keyboard but I saw no other application affected. Just pressing Ctr+F12 it would already select an option. Ran the live updater several times and no dice. Until LM releases a hotfix I'll just have to select it from the menu bar then.

You can still call the window with Ctrl+F12 (or Ctrl + F11 for ASPv4, or standard Scroll for ATC window) just don't choose an option from that window by Keyboard but select it with your Mouse. If you choose your option by Keyboard, the Key you pressed will be given automatically to the next Window you call up.

Edited March 16, 20188 yr by GEKtheReaper

Interesting that the mouse selection works for you guys.  For me I simply select (mouse) the AS option via the Addons menu, let it quickly flash by and then disappear and then I select (mouse) the GSX menu (which then acts like normal).  

 

If if I were to select (mouse) the gsx menu straight it quickly flashes and automatically selects an option.  Note I do use numbers for my CP views.  Some have suggested changing CP assigned keys (ie don’t use numbers), but that didn’t make a difference for me.  

10 hours ago, Hilkiah said:

Note I do use numbers for my CP views.

I'm certain that this is your issue then. All choiches presented in windows are selected by Numbers. Since you use numbers for CP views, the last number will be transmitted to your next window ;).

On my end I assigned letters to CP views like: R-Radio, O-Overhead, T-Thrust, F-FMC,....and therefore those keys will not interfere with GSX/ASPv4/ATC choiches.

Just assign shortcuts to keyboard letters instead of numbers and you’ll be fine, no need for mouse. 

It is amazing/astounding/unbelievable/annoying/unforgivable that this hasn't been fixed by now already. Shame on LM. Wouldn't surprise me if this won't get fixed until v4.3. I myself use numbers all of the time and I don't like to change my 'workflow' because LM added this bug to P3D. I don't even have P3D installed due to this bug: I am waiting for the fix but never expected it to take this long. Really terrible bad support.