FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: virtuali on March 21, 2023, 04:53:03 pm
-
Today Microsoft released Sim Update 12, which has added lots of important improvements to the sim covering many areas. But for FSDT and GSX Pro, the most important feature is the addition of full Jetway informations to the Navdata API, which will offer big benefits to how GSX works.
The changes are many and their impact so profound, we had to make a presentation video to explain in the detail how much this improves GSX:
We would like to thank Microsoft and Asobo for listening to all our suggestions about this new API, which has been added exactly like we asked, and makes GSX working with jetways so much better.
To get the update, just run the FSDT Live Update.
-
This is amazing news. I have enjoyed your products for many years now, and even though it isn't perfect, GSX has always been a game changer for me. Do you have any insight as to the ability to change the jetway type and customize them per airport like in p3d? Is this a limitation of the sim or are you just not planning on them? I greatly miss that feature
Thanks again for all your dedication!
-
Amazing stuff, keep up the fantastic work!
<3 FSDREAMTEAM! <3
-
👍🏻👍🏻👍🏻
-
Nicely done! I am just trying to figure out why I don’t see people anymore (pilots nor passengers)
Sent from my iPhone using Tapatalk
-
What is SU12 Navadata API option good for except for locating jetways at Standard Microsoft/Asobo and 3rd party Marketplace bought airports? If there is no other use for it, how can I disabled it?
-
What is SU12 Navadata API option good for except for locating jetways at Standard Microsoft/Asobo and 3rd party Marketplace bought airports? If there is no other use for it, how can I disabled it?
And why you would want to go back to the legacy "airport cache" method, which would:
- slow down the startup
- have to be regenerated each time you install/remove a scenery
- affected by any possible issues in your Community folder, like file access problems, possibly corrupted files or just not finding the right .BGL ?
- not future-proof, because it relied opening a non-officially documented file format, which can possibly change at any time ( it has already changed several times since MSFS came out ) ?
While in the SU10 version of the Navdata, it might have been useful to disable it if you didn't use Marketplace airports, because by reading the .BGL we had jetways working a bit better, because at least we could read their positions from the .BGL, which we couldn't in SU10, with SU12 we can, and we also get even more data than we ever had ( even from the .BGL ), because the issues with jetways were not just caused by not finding them ( that was just one of the issues ) but also not being able to detect their status reliably and not knowing where the jetway went after it animated, which caused passengers in the air each the jetway didn't go to the Main Exit.
Since SU12 fixes all of that, it doesn't really makes sense to disable it.
The only side effect of using the Navdata, is that if you use a GSX custom profile, you must to be sure it's for the correct scenery you have installed at the time, since we can no longer associate a .BGL with an .INI, only the ICAO code matters, so you need to be sure the profile you use was made for that scenery.
-
There may be one scenario where cache setting had it's advantages.
I made a profile for an addon airport. The original bgl file of this airport was kinda crappy. For example they didn't connect any of the stands with a taxiway. So GSX did read them as separated stands and wouldn't work with this airport at all.
I took a workaround by creating a new/modified bgl with all stands connected (to copy it into the profile folder and let the profile AFCAD path point to this new bgl file). This worked.
With the cache setting deactivated now, I presume that GSX will use the (bad) original bgl file of the airport developer again... and will stop working with this airport again.
Or am I wrong?
-
With the cache setting deactivated now, I presume that GSX will use the (bad) original bgl file of the airport developer again... and will stop working with this airport again.
Yes, that is correct and, in fact, having a customized .BGL is the only feature we lose when using Navdata.
However, if the scenery AFCAD is really bad, it might be better to simply put your fixed version directly in the scenery package in the Community folder, so its correct data won't be used just be GSX ( through Navdata ), but the whole simulator, including AI, which will also benefit from your fixes.
-
Yeah, but that would produce copyright issues, I think. So I made a bgl only with the taxiways, stands, etc. to be able to publish it. Putting this in the scenery folder would create an airport without objects.
By the way, I also don't see any pax leaving the plane (stairs) with the new update (a32NX, at Corfu FlyTampa).
-
This great news Ali! Finally we have the old trusty GSX back...
-
With the cache setting deactivated now, I presume that GSX will use the (bad) original bgl file of the airport developer again... and will stop working with this airport again.
Yes, that is correct and, in fact, having a customized .BGL is the only feature we lose when using Navdata.
However, if the scenery AFCAD is really bad, it might be better to simply put your fixed version directly in the scenery package in the Community folder, so its correct data won't be used just be GSX ( through Navdata ), but the whole simulator, including AI, which will also benefit from your fixes.
So you’re saying my FlyTampa KLAS jetways don’t work with the update? Because they don’t. “No jetways available here”.
How/when will this be resolved? Do I need another custom profile?
-
I am totally confused now.
With SU12 Navdata option enabled, which .BGL does GSX read and use for its calculation? E.g. EDDL: the Asobo .BGL or my JustSim NON-Marketplace .BGL?
-
So you’re saying my FlyTampa KLAS jetways don’t work with the update? Because they don’t. “No jetways available here”.
Not sure how you derived this information about FlyTampa KLAS, when the user was discussing about a specific scenery with a bad AFCAD that required a modified .BGL. I doubt he was referring to KLAS, and Jetways there works perfectly fine, see the attached screenshot.
Have you checked KLAS has been excluded from GSX Jetway replacement, as it should be for every 3rd party scenery ?
-
I don’t understand your last question. This is a 3rd party add on I bought. FlyTampa KLAS.
Before the latest update, the jetways didn’t work and I had to find a profile to make them work. Should I remove the profile now?
-
@Umberto:
Let me rephrase.
I do not use Microsoft/Asobo airports
I do not buy 3rd party airports on Marketplace.
I only use 3rd party Airports bought from the developers and/or resellers. Hence, they are not encrypted.
Q1: Does enabling the SU12 Navdata option have any advantages for me?
Q2: Does enabling the SU12 Navdata option have any disadvantages for me?
If A1 = yes -> which?
if A2 = yes -> which?
If A1 = no and/or A2 = yes -> how can I disable the SU12 Navdata option?
-
Q1: Does enabling the SU12 Navdata option have any advantages for me?
We are inside a thread that started with a video that explained all of this. Have you seen the video ? If yes, what's not so unclear about the BIG improvement the SU12 Navdata offers with ANY airport that has JETWAYS ?
The Marketplace encryption issue was solved with the SU10 API so yes, if you never bought a Marketplace airport, you have the Standard MSFS ( that doesn't come with any encrypted airports ), maybe the SU10 Navdata option wasn't that useful, apart from the benefits of not having to deal with the airport cache, its regenerations, and any related issues of having to read files in the Community folder.
But SU12 is completely different, because ( as the video clearly explains ), the new data we are getting about Jetways, we never had it before, neither with the Navdata, nor with the .BGL so yes, SU12 Navadata dramatically improves how GSX works with ANY airport with Jetways, completely unrelated to the Marketplace.
-
This is a 3rd party add on I bought. FlyTampa KLAS.
That's the same of my screenshot.
Before the latest update, the jetways didn’t work and I had to find a profile to make them work. Should I remove the profile now?
I'd start with that.
-
Let me see if I got it correctly:
With SU12 Navdata API GSX can now get correct information about the jetways (and maybe taxiways, etc.?) without any workaround.
Does that mean we do not need any GSX airport profiles anymore?
-
With SU12 Navdata API GSX can now get correct information about the jetways (and maybe taxiways, etc.?) without any workaround.
That should have been clear, had you followed the video that opened this thread. And no, we always got correct information about everything else (taxiway, runways, parking spots), SU12 is basically Jetways, at least as far GSX is concerned. Please look the video, it explains everything.
Does that mean we do not need any GSX airport profiles anymore?
Why you think a GSX profile could possibly have anything to do with Jetways ?
The only thing which might have improved how jetway worked before, was the custom jetway floor height, to specify the height of the jetway at its root, and we still need a profile for THIS specific information, since not even SU12 provide it, because it's not something even the simulator itself has. That would only improve passengers walking at the correct height, in case it's different than the default ( both default and GSX jetways have a floor at 4.6 mt from ground, the manual obviously explains that too ).
Other than that, a profile could only be used to improve the vehicle positions, doing custom pushbacks, adding docking systems, adding custom remote deicing areas. Nothing that would change how the jetway worked, other than the aforementioned root floor height.
-
I don’t understand your last question. This is a 3rd party add on I bought. FlyTampa KLAS.
Before the latest update, the jetways didn’t work and I had to find a profile to make them work. Should I remove the profile now?
My case is a very special case. Normaly everything should work with the new GSX version. The only case, where this change could have a negative effect is, when someone provided a modified bgl file (that's part of the scenery/airport, NOT the GSX profile itself) for GSX to read.
If the original airport scenery (default or addon) has a working airport bgl, everything will be fine (which will be the case with most of default or addon airports). If not, and GSX can't handle a faulty original bgl file, we (profile builders) right now have no chance to workaround this issue.
-
Changelog please?
-
This is a 3rd party add on I bought. FlyTampa KLAS.
That's the same of my screenshot.
Before the latest update, the jetways didn’t work and I had to find a profile to make them work. Should I remove the profile now?
I'd start with that.
Ok. Will report back later. Thanks.
-
No dice. I disabled the 3rd party Add-on in settings, removed the custom profile, customized the parking position, etc and the jetway at KLAS Flytampa just doesn’t move at all.
Worked fine before the update.
Wish I could roll it back.
Best I could do is disable the .BGL and let the default jetway do its thing. Now I don’t have the sounds and signage.
Ah well.
-
This update is awesome, well done! Menu is so responsive, jetways working perfectly.
We're pretty much back to full P3D functionality.
Any idea how you'll tackle the multi jetway functions going forward? I assume when PMDG bring out their 777 people will be asking for it - whether that gets done in the core game or a MSFS2020 version of SODE. Either way, it has to happen surely.
-
No dice. I disabled the 3rd party Add-on in settings, removed the custom profile, customized the parking position, etc and the jetway at KLAS Flytampa just doesn’t move at all.
Worked fine before the update.
Wish I could roll it back.
As I said ( and tested, of course, see the screenshot ), Jetways at FT KLAS works perfectly fine.
The problem is not our update, otherwise they wouldn't work at all, the problem must be some conflict you have caused by another scenery. This assumes your report of having disabled KLAS from GSX replacement, which is the most likely cause of the problem but, since you said you have done that and you also said you removed a custom profile as well, it leaves the "another scenery in conflict" as the only possible reason left.
It "worked before", because in the previous version, GSX would need to use a ( very unreliable ) search method to find jetways, now it doesn't do anything like that and it just asks the sim where they are.
This means, however unreliable the old method was, it might be less exposed to scenery conflicts. Now if you have a conflict, GSX will get that as well. But using the proper Navdata is much better, because the old method has all the issues that have been clearly explained in the video so no, we are not going back, you just need to be sure you don't have conflicting sceneries.
-
Hi,
Is there something I don't understand, I already have GSX Pro, do I have to pay again to have this update?
Thanks
Luciano
-
Is there something I don't understand, I already have GSX Pro, do I have to pay again to have this update?
It's just a normal update that is installed automatically by running the FSDT Live Update.
-
Okay. Because I have already done it but in some paying airports the passengers keep walking out of Jetways
-
Okay. Because I have already done it but in some paying airports the passengers keep walking out of Jetways
Please clarify what do you mean with "walking out of Jetways".
If they are just sticking out of it, because the jetway is either too low or too high, that's a completely different issue that doesn't have anything to do with SU12, since nothing in the SU12 give any info about the location of the jetway floor or its height, so GSX by default assume a certain height, but you can customized it. This is of course explained in the manual, in the "Custom Jetway Floor heights" chapter at Page 71.
If, instead, the scenery you are referring to has non-standard jetways, like the T-shaped ones that moves only in one direction, that's not something really supported by the SU12 API, which assumes a jetway made like the default one so, some developers have devised creative ways to make it work, the info we get from the API is not enough, you can find these at ENBR, for example. To support these jetways, it will be required extra customization on the GSX airport profile, and will be included in the next update.
If, instead, the jetways looks standard, you are sure you have update GSX and you still have passengers taking completely wrong routes, it's likely your problem has been caused by Simconnect being too overloaded by other add-ons, most likely AI Traffic products that inject too many AI, exceeding the maximum number of objects in the simulation, which results GSX just not getting the data it needs from the simulator, because Simconnect communication became erratic.
So, please clarify exactly what's your case and where this happens.
-
Can I attach images so you can clearly see what I'm talking about?
-
Can I attach images so you can clearly see what I'm talking about?
That's precisely why the forum has an "attach" function.
-
Hi virtuali - please fix the male accent of GSX in India - it is horrible and not even light years close to what it actually should be.
-
Hi virtuali - please fix the male accent of GSX in India - it is horrible and not even light years close to what it actually should be.
The problem with AI-based accents, is they are perfectly fine for everybody, except users living in that country. Of course, enterprising users that found their local accent to be bad, contacted us offering to do live recordings made by real people, which is the only way to "fix" an accent so, as soon as we get a real person recordings, we can replace the AI based version.
-
I volunteer - what is the process?
-
what a triublesum software not robust at all and not made by profsionals
-
@Ericdeperick
There are thousands of users who think like you do.
Here is the problem:
Umberto and FSDT don't like to here/read this.
I guess he will delete your posts and ban you from the forum, if you continue.
-
Here is the problem: Umberto and FSDT don't like to here/read this. I guess he will delete your posts and ban you from the forum, if you continue.
No, the real problem is you THINK there are "thousands" of users thinking something, without having the slightest amount of proof.
Something that, instead, we have, because not only GSX has been an incredible success, but sales has been going on steadily for months, since what "thousands" of users are REALLY thinking, is that those that might not have bought it on launch, clearly must have noticed the improvement, which are obvious and anybody can see that.
And yes Ericdeperick post DOES deserve to be removed, not because it's factually wrong, but it's because it's offensive. But it will stay there, because the way is written, it's more embarrassing for the poster.
Instead, I banned HIM, because he violated the forum rules, because he spammed the same useless comments AND offending comments in multiple threads, which is not tolerated, because it's very annoying for other users that are obviously enjoying GSX and come here to seek guidance in the proper way, to see somebody piggybacking on every thread by adding something completely unrelated, instead of doing what he's supposed in a support forum: making a proper error report, and ask for help.