FSDreamTeam GSX for MSFS

Well, despite apparently being found a bit wanting when it comes to IT knowledge, I did still manage to find a way to press the buy button and my first impressions have been very good.

On the latest leg of my Fenix A320 tour of the world’s capital cities, the trip from Valletta (LMML) to Tripoli (HLLT), was greatly improved by having a full range of great looking ground services, without me having to touch anything, apart from prompting the push back.

Thanks to FSDT along with, in this case, Fenix, as the integration/automation makes the whole experience truly immersive. Nice one.

2 Likes

Some time ago FS Dreamteam GSX pro surprised me with the following sequence. I’m not entirely sure whether I was hacked or where the whole thing came from ??

https://streamable.com/p7i1t7

If you land right on the marks they reward you with a dance and some tunes. I like it :slight_smile:

Maybe the platform he was standing on was somehow electrified by something in the cockpit? :stuck_out_tongue:

Joking aside though, it is good to see anything that makes the operatives as human as possible.

Yes you’re right and this has been annoying me for some time, it’s a clear omission. I meant to report it but I think you’ve done a good job there. @Umberto67 reads this and is very responsive, hopefully they can fix it soon so that we can go back up in the parking menu tree.

Yea sure, let me just post a topic on the FSDT support forum, which I can’t access (this being the actual problem that I have).

Or wait, let’s use the Discord channel, which is not listed anywhere as being something “official”, or even if it is listed, it probably is listed somewhere on the forum, where I don’t even have access. Even if I would post my support request / ticket there I would probably have to share my IP address and other personal details to other 100 people, for you to check the root of the problem.

Guess, I’ll have to create a Facebook account just to get some support. Sounds nice.

Fact you are using the term “from scratch”, as if this was something like a complex/lengthy procedure, seems to suggest you are using the menu in the wrong way: by opening it and closing with the mouse, instead of using the hotkey, which will to do unnecessary extra clicks, and will cause other issues as well, like missing all text messages and pop-up menus.

The menu should be opened (if it’s not already from the previous flight) with the mouse only when you first start GSX in a given session. From now on, you should always use the Hotkey to open/close it with the hotkey. You should close it from the Toolbar only when you are done with ground services, usually after pushback.

Now, the hotkey by default is CTRL+Shift+F12, and it’s like that only because we kept the same as the original GSX for FSX/P3D, because long time users might be accustomed to it, perhaps programmed keyboard/Joystick macros to use it.

But you can change it, and I always change it to be just X, which is way convenient because, in your case, if you wanted to “go back” to the gates menu, you would just press X twice (assuming you changed it to X, of course), and when the menu is closed/reopened using the hotkey, it reopens way more quickly, since it doesn’t have to reinitialize the whole html/javascript page, which is what happens if you close it entirely by pressing the Toolbar icon.

The reason why the GSX menu works like this, is because it’s a menu you need to open and close at different times, but it doesn’t need to stay open in the meantime, since you don’t get any benefit by keeping it open all the time (it’s not like a moving map, for example), and the reason why you shouldn’t use the Toolbar icon to close it if you are still using Ground Services, it’s because how the Toolbar systems work: the whole menu code stops to be called the moment you close the menu with the Toolbar, so it must restart “from scratch” again on the next reopening and won’t be able to “pop-up itself” or display messages because they require the menu Javascript code running, which it doesn’t when the Toolbar icon is not active ( dark icon ).

Yes, there are some add-ons using the Toolbar that circumvent this, by they are doing it in a very questionable way: by overriding the code for the stock MSFS Toolbar menu, which is something we’d rather not doing, since we don’t want to touch any of the original MSFS code, and having Javascript code always running in the background have some performance cost: that’s the main reason why Asobo changed the way the menus work back in SU5, which broke lots of add-ons that relied to the menu code always running.

This is of course explained in the GSX manual, where the proper usage of the menu is presented, with all the reasoning why it works in what might seem an “unusual” way, but it’s the only way that complies how the official, unmodified, MSFS toolbar menu works.

And it came with a nice side effect as well: because of the way the menus in MSFS work (completely different than FSX/P3D, were apps create their menu on the fly, in MSFS is the opposite: the menu calls into the app), we had to redesign the way GSX works entirely, and this resulted in GSX now being possibly remote controlled by 3rd party apps and integration, so it’s now possible to have apps controlling GSX “hands free” without even showing a menu, or possibly even more advanced things like airplane gauges showing the GSX menu inside their gauges/EFBs.

This very lengthy explanation, only to explain why you should always use the Hotkey to open or close the GSX menu, and if you changed the default Hotkey to be a single key, like X, “going back” the menu would basically means just pressing the hotkey twice, which is very fast, if you don’t have to go through the full menu restart.

Finally, your suggestion to use the 2nd Title bar as a “Back” function looks interesting, so we’ll take a look at it.

3 Likes

I have an impression that you develop GSX but don’t actually use it on a daily basis. I explained it to you before but will try again. GSX window when hidden still intercepts mouse clicks, so if a cockpit switch happens to be on the edge of the GSX hidden window you can’t click on it. It’s not GSX fault, every toolbar app in MSFS behaves like this. That’s why I close GSX from the tool bar menu as soon as I request boarding. It’s still doing its job in the background. Yes, you won’t get notifications but in most cases, you don’t need them. The only one I need is when GSX asks which direction to push the plane. I know when it happens, so I open GSX with a mouse, select one of the options and close it again. I don’t leave it hidden.

Regarding the manual you keep mentioning in every response. Would you be so kind and add an index or bookmarks, please? It’s already 118 pages long and finding anything in this document is difficult, unless you know what you are looking for. I bet most new users don’t.

One more thing. Why audio device used by GSX won’t switch automatically when I change audio output in Windows? Why do I need to do it manually and why Couatl64_MSFS.exe requires a restart? When I turn on VR during boarding, GSX audio is still being played on my desk speakers while all other sounds from MSFS are played in my headset. I can go to GSX settings and switch audio manually but it will restart GSX and stop the boarding.

1 Like

But it happens only when your mouse cursor is precisely on the border of the menu window!

It’s not as if the whole menu area covers the instruments preventing clicks, it’s just the border.

Also, the menu is not intercepting any clicks or doing anything with those, it’s not as if, even if an instrument hotspot crossed the tiny border of the menu that, when trying to use the instrument you would send a click to GSX instead: the only thing you could do, if you hover on the hidden border, would be resizing the hidden GSX menu, and only if you drag it to resize, that’s the only event intercepted by the menu, which as you know very well, is the same with every other hidden toolbar menu, because it’s an inherent behavior of the menus, not something we coded.

Yes, of course we and other developers reported it to Asobo a long while ago: it would be best if an hidden menu would just ignore all mouse events, which normally does on the menu area, but it would be even better if ignored them on the border too.

Missing notifications is not the big issue. It only affects first-time users doing something wrong, like trying to park on a too small parking spot, trying to call GSX without parking brakes/engines off, or issues like passengers not showing because jetways didn’t connect, all things that, without a message, would confuse beginners of being “GSX bugs”, when they aren’t. That’s why we added extra aural messages, to supplement the text notification but, again, text notifications are not really a problem.

The main problem is when GSX needed to pop-up a menu in the middle of a service, like the time between when you ask for Departure to the time you have been asked for a direction, with a pop-up menu that cannot be created because the menu is completely closed.

With Pushback we made a specific workaround, with the “Continue Pushback” option, because this issues was too important to not be dealt with but, there are other cases when we need a pop-up later, for example:

  • When you call refueling with a default airplane (one without a custom Fuel system, so it can be refueled by GSX), if you close the menu from the Toolbar, you won’t see the GSX Fuel quantities menu which is supposed to pop-up when the Fuel Truck arrives.

  • During De-icing, you won’t see the request for the various de-icing options (Fluid type, Concentration, etc.) when the Deicing truck arrives.

Maybe these are not a problem for you, you might only use airplanes with custom Fuel systems or never use Deice, of course every user is different but, in my opinion, those issues are more serious the the entirely inconsequential issue of the menu resize controls showing up when you hover the moue on the border of the menu, which is immediately fixable by just panning the view, in case the border happens to pass exactly over the instrument clickspot you need to use.

The .PDF is searchable. I don’t know how much better would be, when you need to “search” something, to first go to the index page, (which might end up being longer than one page by itself) and search for some keyword in the index, take note of the page number and go to it, when you could just use the Search function directly on the actual text.

Yes, I vote for that.

5 Likes

Default passenger loading is ridiculous can we please have a manual input for passenger numbers for those that do NOT wish to use Simbrief. Today i did a flight in the 737-800 and it loaded 213 well over its capacity and the B787-10 in which it only loaded 137 well under its capacity

The FSX/P3D version has the option of entering the number of passengers which was the method I used back in the FSX days. The MSFS version integrates more with Simbrief or other 3rd party aircraft that supports it in pulling the passenger numbers from a 3rd party aircraft payload setup. Without either, GSX has to do a general estimate based on the aircraft’s weight(which as Umberto would say, it’s clearly explained in the manual and even shows the formula they use)

Personally, I love the Simbrief integration, but I do get the frustration from users who are finding that more 3rd party addons require Simbrief to operate.

Well, simbrief is free to use, so it’s not a hindrance. And you can still enter passenger numbers manually on the FMC of the PMDG 737, so I don’t understand the complaints.

1 Like

I do not want to use Simbrief i see no need to use a piece of software to do something i can do without it. Of course it is a hindrance if you have to add extra steps i dont need, in fact some aircraft don’t even have simbrief integration but do work well with GSX
My complaint is you cannot specify a passenger load in GSX directly and its calculations/formula are woefully wrong, ive tried different weights and it does not affect GSX at all. Not all aircraft are filled to capacity. Inputting passenger numbers directly in the PMDG does not affect GSX at all and has nothing to do with GSX so does not affect how many passengers GSX loads and even if it did there is a life beyond PMDG believe it or not. for example my current flight has 148 standard class and 12 first class so that’s 160 yet gsx loaded 213 well above the 737 max capacity.
All that is needed is a simple box to type a number in that controls how many passengers are loaded it would take 5 seconds to add a number over the how long to use simbrief. I dont see why a passenger number input is hard to fathom . Maybe i should get a refund if to use the software properly i need another piece of software to use it

1 Like

Well, simbrief gives you not only your route, but number of passengers, weights, winds, meteo and much more information. It’s clear you can’t do things without it, but it’s your choice to get it or not. I repeat, it’s free, and a great tool. I can understand people don’t expend money in some addons despite they are great addons, but not getting a free (FREE) tool that everyone uses nowadays is…

what about planes that do not have simbrief integration?
Too many people are too short sighted they can only think of the PMDG’s and other similar airliners and there is more to GSX than those.
It is unacceptable that for GSX to run properly i need simbrief, no one needs simbrief it is and always should be a choice, GSX is not simbrief . To enter 150 in a gsx box i can do quicker than downloading simbrief why on earth if i choose not to use it should i be forced too? and previous versions of GSX had this ability so why not this one?

1 Like

You don’t need a plane with simbrief integration, GSX is integrated with it already.
Also simbrief is not only for airliners, I use it for all sorts of planes.

Tell me one single plane that has no simbrief “integration” (whatever this should be). At least in my hangar, none is sitting around, and I have by far not only PMDG. And for a Piper Archer, we do not really use GSX passengers, no?

DC3, Dragon Rapide, EMB110 , Trislander, Islander, DHC 7, DH Dove,concorde you can use GSX on all of these but you cant input passenger numbers. i seriously cannot understand the opposition to a small text box .
In Fairness i tried Simbrief a long time ago when it first came under Navigraphs and i don’t get on with it and i found i don’t need it, it fills no purpose

2 Likes

No one is opposite to a small box or whatever is required to implement custom pax feature in GSX. We are just baffled it’s such a big issue for someone to use free Simbrief as a workaround. I don’t see you have many options: you either start using Simbrief, accept random pax numbers generated by GSX or … stop using it altogether.

1 Like