25 minutes ago, virtuali said:

At this time, the best option is to trying to obtain an unencrypted version of the airport file from the original scenery developer. Our installer will do this automatically for all our airports, if it finds them in the Official (=encrypted) folder, 

@virtuali Umberto, does that mean I can get the ORD from you, uninstall the marketplace one and reinstall one with the updater? I'd love to do that, how do I go about it?

It was stable after the first few days of release, insta buy imo. I haven't had any CTD's at all, just once that Couatl didn't start with the sim so I started it from the desktop icon and all was good.

8 hours ago, virtuali said:

Who said it will be "months"

Excuse the off-topic, but is KIAH being worked on during GSX update development or is it paused until GSX is updated?

42 minutes ago, virtuali said:

This is not a problem or a bug, read Pages 66-67 of the manual why and when the menu intentionally auto-closes itself.

We are aware this is not very useful in VR, so with the next update the menu won't auto-close anymore, there will be an hotkey to call the menu, and there will be an "pinned" mode specifically for VR.

 

THANKS for your quick and positive reply. I will try it and see how I get used to it, I like the immersion a lot. 

On my absolute simmer list for sure . Havent had a CTD at all . 

A couple of days ago i had a great experience with the VDGS at Tromsø (addon scenery - GSX Profile from flightsim.to) (PMDG736) . It showed me my dep. time and time left for departure. 

Michael Moe

 

Edited September 16, 20223 yr by Michael Moe

4 hours ago, Michael Moe said:

On my absolute simmer list for sure . Havent had a CTD at all . 

A couple of days ago i had a great experience with the VDGS at Tromsø (addon scenery - GSX Profile from flightsim.to) (PMDG736) . It showed me my dep. time and time left for departure. 

Michael Moe

 

Don't forget to select one of those gates on an arrival. They are really great for parking. I'm surprised how responsive they are.

6 hours ago, virtuali said:

This is not a problem or a bug, read Pages 66-67 of the manual why and when the menu intentionally auto-closes itself.

We are aware this is not very useful in VR, so with the next update the menu won't auto-close anymore, there will be an hotkey to call the menu, and there will be an "pinned" mode specifically for VR.

 

Halleluja 

14 hours ago, virtuali said:

The API is not complete as we wanted to be, data about Jetway is still missing so we'll likely have to use hacks and workarounds about this ( as usual ),

This is what kind of worries me... I just don't want software that uses hacks and workarounds related to MSFS

I decided to hold off.  I have the demo version and I have only used to fly between their own airports that I have purchased (not even the few defaults it is supposed to work with).  Over about 5-6 flights I have never been able to get this to continue to work once I have landed and taxied into the gate.  At that point the menu simply will no longer open (multiple clicks) and all services disappear around the airplane.  It is like is simply is no stops running (yes, I manually restart Couatl).   Since I am not a customer for this product I have not asked for support and that's ok.  I will give it 3-4 months and sees how it improves.

Installing can be quite buggy, requiring multiple attempts (unless this has been improved in the last couple weeks.)

I've not seen a CTD, but I've seen multiple sim freezeups that ultimately required a force-close of the sim, since installing GSX.  I have no evidence other than correlation that it's related to GSX, but do note that this isn't related to the MSFS issues occurring at the time of GSX release. I installed it for the first time well after that was all sorted out.

GSX reliably crashes for me upon gate arrival, when I open the menu to request deboarding.  Not every time, but greater than 50%.

VGDS systems work well (other than occasionally seeing a ghosted repeat of the symbology floating in space near the screen.)  Marshallers work well. Quick edit pushback is nice.  Regular push rarely hits the line for me and occasionally does something odd like push me across an alley into the terminal. 

My experience so far. 

13 hours ago, Drumcode said:

@virtuali Umberto, does that mean I can get the ORD from you, uninstall the marketplace one and reinstall one with the updater? I'd love to do that, how do I go about it?

@virtuali l'm in the same position and would like to know this too. I also have your Key West from the marketplace.

7 hours ago, Cognita said:

This is what kind of worries me... I just don't want software that uses hacks and workarounds related to MSFS

Then you shouldn't use anything for MSFS, because almost everybody use workarounds to overcome SDK limitations, especially utilities, since the SDK has been initially designed with an eye towards airplane developers first, it's being (very) slowly expanded into other realms more useful to other kinds of add-ons, but is still not nearly as complete as it should be and is still way behind what is possible with P3D.

I shouldn't probably used the word "hacks", since this is not FSX/P3D where you could create a real in-process .DLL and get the data you need directly from memory if the SDK didn't supply you with the data you need, which could be potentially dangerous, especially if you tried to write back this data.

There's no such thing in MSFS, even WASM modules are heavily sandboxed and can't do even the simplest thing as opening a file outside their own folder, let alone peeking or (even worse) writing in memory, which is something we *did* in FSX, but only because the program never changed in years, once we found what a memory address does, we could be sure it would never change because the program was frozen. We never did anything like that in P3D, because the SDK has been greatly enhanced, but there are lots of popular products in P3D that still do that (all the ones that require an update each time the sim is updated), because they need data not available from the SDK.

In MSFS, we couldn't do it even if we tried, although it is theoretically possible, it would require a software that attach itself to the sim like a debugger, running only in admin mode and with so many security issues that is not something I would never use in a public release. In this case, I would rather drop a feature and hope the SDK will improve to provide it officially.

And example of a feature dropped in GSX for MSFS because of the "safety first" approach is positional audio: since the MSFS SDK doesn't give the location of the camera ( in FSX was hacked from memory, in P3D the SDK supplies it with an official call), in MSFS we still have positional audio, but it only works properly if you are in the cockpit, changing to another camera won't result in a change in audio as it did in FSX/P3D, because we don't know where the camera ( = your eyepoint = your ears ) is. Of course, there's a significant number of developers that have asked Asobo for a "Camera API", we can only hope it will arrive, one day.

When I said "hacks", they are not really hacks, since everything in MSFS is always done accordingly to the SDK. In case of Jetways, the (new) SDK coming with SU10 will only tell us IF a Parking has a jetway, and that's it. It won't tell us where it is and, most importantly, it doesn't tell us if it's docked.

In the current GSX, we already had to use a kind of "hack" to know if a jetway is docked or not, but it's not obviously a real "hack": we check a variable of the jetway hood, which of course is a fully supported technique, and assume if the hood is opened, the jetway must have docked so, it's obviously completely safe, it's just that it won't work if a jetway doesn't have an animated hood, and doesn't tell us if the jetway has docked completely. Again, in the name of safety, we haven't even tried doing something possibly more dangerous to obtain that information so, rather than having users thinking "GSX caused a CTD", we rather have people assuming "GSX has a bug", even if the reality is GSX must fight against an incomplete SDK and a buggy jetway system that have bugs even before the SDK is concerned.

2 minutes ago, steve310002 said:

@virtuali l'm in the same position and would like to know this too. I also have your Key West from the marketplace.

There's nothing you need to do, it's all done automatically, the GSX installer will recognize all the FSDT sceneries installed in the Official folder (=bought from Marketplace) and will download from our site the unencrypted version of the airport .BGL and will place it in the GSX airport profiles folder, which is the only thing GSX needs to work on them properly.

On 9/16/2022 at 10:02 AM, mpo910 said:

Are there currently still users having issues with "disappearing airports" at arrival and is there a work around for this (focus on WorkAround)?

I just started this topic a few minutes ago (Destination airports vanishing) and had no clue that this could be eventually caused by GSX, it happened to me twice in three days. I would be very interested to understand how can one eliminate this. Thank you for any feedback.

Edited September 17, 20223 yr by Bernard Ducret

45 minutes ago, Bernard Ducret said:

I just started this topic a few minutes ago (Destination airports vanishing) and had no clue that this could be eventually caused by GSX, it happened to me twice in three days. I would be very interested to understand how can one eliminate this. Thank you for any feedback.

I really do not know but I saw users containing about this at the FSDreamTeam Support Forum. 

That's why I asked here if others he see this also. 

M.