9 hours ago, virtuali said:

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.

I thought the positional audio was connected to the model? The Fenix 320 does this perfectly. To name a few, avionics cooling (in- and outlet), airco (also in- and outlet) and APU. You move the drone cam closer to them and they sound louder, very realistic. In the cockpit you won't hear these sounds, but different ones. So this seems not very cam related at all to me.

1 hour ago, Gerwil said:

I thought the positional audio was connected to the model?

It's connected to BOTH the model and the camera, as confirmed by what you said:

Quote

You move the drone cam closer to them and they sound louder, very realistic. In the cockpit you won't hear these sounds, but different ones. So this seems not very cam related at all to me.

So yes, it's connected to the camera as you can see, and this works if the airplane uses the standard MSFS audio engine.

GSX has its own separate audio engine, and it's a Simconnect application that runs almost entirely outside the simulator so, like any other Simconnect application, it doesn't have access to the MSFS audio engine, because there's no integration between Simconnect and audio.

So, as I've said, we already have audio connected to the models, but without having access to the camera position, the positional effect is only valid from the default eyepoint position in the cockpit.

And of course, having the camera position is not useful "just" to get positional audio, that was just an *example* of one thing we used for, but there are many other good reasons for having more control over the camera. In P3D we could create custom camera views in the fly programmatically, this is not possible in MSFS.

 

15 hours ago, Stearmandriver said:

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

glad I am not the only one, for me it is 100% between FSDT airports.  I may try again in a few days, who knows - maybe something in the updates.

So...after 2 days GSX in MSFS. I AM REALLY ENJOYING THIS. I find the menu really a bit clunky. This automatic closing should be adjustable either with longer times in seconds adjustable by user (min 10 maximum 60 or so) or it should be possible to choose stay open or close automatically. 

Also I would prefer a button or key "open menu" assign option. This would be great in VR. 

I habe made 2 custom profiles incl. Pushbacks Safegates etc for LFSB(incl all the walk gates) and GCRR. Just stunning. 

Thanks to all for pointing me into the right direction. 

Love the product. 

Finally nice pushbacks. And much more

M.

 

7 minutes ago, mpo910 said:

Finally nice pushbacks. And much more

M.

 

I agree, it offers a whooole lot, just to mention the regional voices of the pushback guy/girl.

@virtuali

What really would be cool is an option that users who want it, can assign an arrival gate prior departing from the departing airport. So if you land and taxi to your gate no need to interact with the menu. 

Do you think this is something others would like too?

I would enjoy this because of flying in VR not fiddeling with Menues would be great. 

Should this take 5 hours and counting to install,,,or ?

14 minutes ago, warbirds said:

Should this take 5 hours and counting to install,,,or ?

Not sure what you mean. Does your installation lasts 5 hours+?

Five hours so far, still downloading and installing

2 minutes ago, warbirds said:

Five hours so far, still downloading and installing

Yikes. Took me a couple of minutes (maximum 2 - 4) 

1 hour ago, warbirds said:

Five hours so far, still downloading and installing

No, something is not right.

Assuming you have a reasonable internet connection (anything over 50 Mbps/download), it shouldn't take more than a few minutes to download the files. I think the total download is around 2.5-3GB, and on my 1Gbit Fiber connection it only takes maybe a couple minutes to download and decompress. 

GSX ""Pro"" is total garbage. On top of the atrocious limitations imposed by Asobo, it's just chock full of game-killing bugs that land squarely on FSDT. The latest and greatest one is that GSX vehicles are now disappearing and even restarting couatl 47823749327598347895347 times doesn't bring them back. You have to quit MSFS and restart the entire sim to get it working again. I don't even care of Umberto replies to this with a 10 paragraph essay telling me all the reasons this is out of his control. Shove it back in the oven, give everyone refunds, and just don't' release utter $h1t like this again.

I do wish making the custom routes was more simple. I've watched YouTube videos, read the manual. It's a lot to understand. My pushbacks always end up being wide turns. Idk ill Give it a few days and see if I can comprehend it later hopefully better. 

7 hours ago, warbirds said:

Five hours so far, still downloading and installing

Mine took about 3 hours at least to complete to 100% and I have fast Internet. There are others saying theirs installed in a matter of minutes. 

9 hours ago, Chapstick said:

GSX ""Pro"" is total garbage. On top of the atrocious limitations imposed by Asobo, it's just chock full of game-killing bugs that land squarely on FSDT. The latest and greatest one is that GSX vehicles are now disappearing and even restarting couatl 47823749327598347895347 times doesn't bring them back. You have to quit MSFS and restart the entire sim to get it working again. I don't even care of Umberto replies to this with a 10 paragraph essay telling me all the reasons this is out of his control. Shove it back in the oven, give everyone refunds, and just don't' release utter $h1t like this again.

No, just two lines to say it doesn't happen.

Do you maybe use AIG traffic controller ? Then check this one:

https://www.fsdreamteam.com/forum/index.php/topic,27609.msg181401.html#msg181401

Let's quote the relevant bits:

Quote

Again, after yesterday's testing: I had no problems using FSLTL Traffic in the latest beta! Three take-offs and three landings: GSX is operating normally, no vanishing airfields. Worth mentioning: I was finally able to use the A320 by Fenix normally, I didn't have any major fps drops like with AIG Traffic. GSX does not cause any problems.

 

Quote

the GSX is innocently the same as it was when many users complained that it was the GSX that caused the CTD, and after turning off the better terrain it was Asobo's fault, but everyone cursed the GSX because it was just released with the error MSFS?
Same problem...  it will be here too. AIG Traffic has some bug and connects to GSX right away???  ahh... I wonder how many users have apologized to the creator of Virtuali for the false accusation.