1 hour ago, virtuali said:

somiller thinks GSX should just ignore the airplane type, and load a Simbrief flight plan made for another aircraft in any case, even if it could then cause in a massively inaccurate variations in the number.

Many of us, including me, agree with you Umberto.

If the briefing is valid for the flight as we currently have things configured in the sim, then use it. If the airport(s), time(s), or aircraft type in the brief does not match what what we have loaded in the sim, then ignore the brief. It was clearly for a different flight than we are using and is useless to us. 

His opinion and my opinion cancel each other out. I guess that leaves it up to you to decide how to write your own software. 🙃 

12 minutes ago, psolk said:

I find all of this talk of manually editing gates and airports pretty amusing considering since it's release there are almost 200 GSX profiles on .to   It will probably be over 200 by the end of the day!  

In P3D I leveraged the incredible work that produced Cartayna files but that still required some fiddling and quite some time to amass so this is the equivalent but community driven and at scale.  

In P3D I customized maybe 5 gates that I used most and leveraged Cartayna files for the rest, in MSFS I will do the exact same thing.  

It's amazing what took years to accomplish in the past by one dedicated individual has been surpassed in weeks by the community.  

Don't see much need for fiddling, chances are someone already did it for me and I am incredibly grateful!  🙂  

Just think how many will be out there in a few months. I've never completed an entire airport, so I've never shared any. But if I ever do, I will be sure to share em.

1 hour ago, psolk said:

I find all of this talk of manually editing gates and airports pretty amusing considering since it's release there are almost 200 GSX profiles on .to   It will probably be over 200 by the end of the day!  

This is only needed for addon airports, right...? I only use default airports (plus the handcrafted ones that come with MSFS and the WU's). I almost always depart and fly to different airports and always use random gates so for me even all this file handling, easy as it may be, would be a bit of a chore...

41 minutes ago, tup61 said:

This is only needed for addon airports, right...? I only use default airports (plus the handcrafted ones that come with MSFS and the WU's). I almost always depart and fly to different airports and always use random gates so for me even all this file handling, easy as it may be, would be a bit of a chore...

No... Even default airports will need some editing or you will run into goofy things. I don't think this is the right SW for you based on what you are saying.

11 minutes ago, MDFlier said:

No... Even default airports will need some editing or you will run into goofy things. I don't think this is the right SW for you based on what you are saying.

I think so too. 😉 Which is a shame. I was hoping it would be a case of 'install-and-it-works-everywhere'.

33 minutes ago, tup61 said:

I think so too. 😉 Which is a shame. I was hoping it would be a case of 'install-and-it-works-everywhere'.

Well, GSX can be used like that. You don't even have to start it, because GSX Pro is in fact made of two separate products, which are installed together by our installer:

- "GSX World", which is quite similar to other offerings from LVFR or Simultech, but it combines Ground vehicle replacement + Jetways replacement in a single product, and instead of being limited by region and with a single Jetway model all over the world, if can offer specific by-airport ground operators and by-airport jetways. It doesn't require any software to run, and it's really all automatic, you use it from the default ground services menus, and you can even use the free Pushback Toolbar add-on, with the GSX Pushback truck, because all the vehicles in this packages has been designed to be stand-in replacements for the default ones.

- "GSX Pro", which is the "full" GSX, with all the customization and the other advanced features which require starting the Couatl engine to run. Which you can foreseeably do even just before you need it, since we designed it to be Started, Restarted and Quitted multiple times, at any time.

If you want an extremely easy to use experience, without worrying about customization, you might use it this way, just getting the new vehicles/jetways which looks better and more varied. Call them from the default Ground services ATC menu, and when you need to Depart, start the full GSX from its icon, select Departure, and just do the Pushback and Eventually the Follow me. The Pushback will work 90% of the time with just Left/Right preset, and the Follow Me doesn't require any customization, it will work on the airport provided its reasonably well designed.

Edited August 30, 20223 yr by virtuali

2 minutes ago, tup61 said:

I think so too. 😉 Which is a shame. I was hoping it would be a case of 'install-and-it-works-everywhere'.

It does work everywhere. Perfectly fine. However, if you choose not to edit things to help GSX vehicles avoid crashing into objects that are invisible to them, or to tell the airplane where it should be positioned at the gate,  well... You'll see collisions and other weird stuff like floating passengers.

Example: If you park an airplane where a jetway can't reach the door of the plane, MSFS will move the jetway as close as it can, and drop the hood. Even if there us a gigantic gap between the two. All GSX knows is that each passenger needs to walk straight out of the door of the airplane a couple of feet, and then turn towards the only thing they can "see", which is the point where the jetway connects to the terminal or bridge. The GSX passengers behave the same every time. Go out the door the proper amount and turn to the building. In this situation, the pax end up walking through the air to the terminal because MSFS did not place the jetway where it should be. The actual reason for the problem is that is that the aircraft position is wrong. It is too far away for MSFS to connect the jetway.

If you are following my example so far, you can see that MSFS is operating correctly (there is no "jetway stretcher" built in that will make a jetway that is too short connect to an airplane that is too far away). GSX is working properly as the passengers are walking exactly where they should be, but the jetway isn't there to cover them up. GSX does not appear to be working correctly, but it is 100% working correctly.

The solution is: put the airplane where the jetway can reach it.

GSX provides a wonderful editor that makes it easy to tell the airplane where it should be. After you edit the gate one time to tell MSFS and GSX where the airplane should be, it will be saved forever and you never need to touch it again. If you move the vehicle start positions while you are there you can eliminate most of the collisions and other vehicle issues. 

For Gods sake!!! So Pyreegue have another update with cryptic instructions. I just don't understand. So you have to edit the file so it points to the file in the community folder. But with all the other profiles I've downloaded you have to point the file to the GSX MSF file? And in the Pyreegue download there's a folder which looks like it should overwrite files in the community folder but there are no mention of this folder in the instructions.

I would be grateful if some one could just let me know, in the simplest language possible, where to put profiles downloaded from flightsim.to and whether any editing is necessary and if so what. My community folder path is G:\MSFS\Community and my GSX addons path is on my C drive and is hidden but findable eventually. Thanks 

(If I could get ONE AIRPORT to work properly my blood pressure would return to safe levels.)

Edited August 30, 20223 yr by jarmstro

I’ve been following this (though haven’t read every post in this lengthy thread) and I want confirm my understanding on how this would work for me.

I’m primarily interested in this as a pushback tool and as a marshalling tool for arrival.  I’ll use the boarding etc on occasion when I have extra time but that’s not my main interest.  I read above that without any tweaking the pushback should work 90%, which is great.  

Will the marshalling have a similar success rate?  I’ll download the airport profiles that are available and don’t mind a bit of tweaking here and there but primarily I want something that will complete a pushback for me and Marshall me into the gate in a reasonable manner for both default and addon airports using primarily third party airliners.

I used GSX in P3D and was satisfied with that experience if that helps as a reference point.

Thanks for any insights.

Edited August 30, 20223 yr by regis9

13 minutes ago, jarmstro said:

For Gods sake!!! So Pyreegue have another update with cryptic instructions. I just don't understand. So you have to edit the file so it points to the file in the community folder. But with all the other profiles I've downloaded you have to point the file to the GSX MSF file? And in the Pyreegue download there's a folder which looks like it should overwrite files in the community folder but there are no mention of this folder in the instructions.

I would be grateful if some one could just let me know, in the simplest language possible, where to put profiles downloaded from flightsim.to and whether any editing is necessary and if so what. My community folder path is G:\MSFS\Community and my GSX addons path is on my C drive and is hidden but findable eventually. Thanks 

(If I could get ONE AIRPORT to work properly my blood pressure would return to safe levels.)

You don't have to edit the files for the right path, this is wrong by Pyreguee (it was like this a couple of years ago on P3D, but no longer; GSX auto detects the folders). So no editing necessary. And that other folder in the download, this is only if you have bought the airport on MSFS marketplace (and it's therefore encrypted).

So what you have to do:
1) Download from flightsim.to
2) Extract the egaa-... . ini file to: c:\users\YourName\AppData\Roaming\virtuali\GSX\MSFS

Done.
This is the basic procedure for EVERY airport config you want to download.

2 minutes ago, Fiorentoni said:

You don't have to edit the files for the right path, this is wrong by Pyreguee (it was like this a couple of years ago on P3D, but no longer; GSX auto detects the folders). So no editing necessary. And that other folder in the download, this is only if you have bought the airport on MSFS marketplace (and it's therefore encrypted).

So what you have to do:
1) Download from flightsim.to
2) Extract the egaa-... . ini file to: c:\users\YourName\AppData\Roaming\virtuali\GSX\MSFS

Done.
This is the basic procedure for EVERY airport config you want to download.

OK and thank you so much. 

18 minutes ago, regis9 said:

I’ve been following this (though haven’t read every post in this lengthy thread) and I want confirm my understanding on how this would work for me.

I’m primarily interested in this as a pushback tool and as a marshalling tool for arrival.  I’ll use the boarding etc on occasion when I have extra time but that’s not my main interest.  I read above that without any tweaking the pushback should work 90%, which is great.  

Will the marshalling have a similar success rate?  I’ll download the airport profiles that are available and don’t mind a bit of tweaking here and there but primarily I want something that will complete a pushback for me and Marshall me into the gate in a reasonable manner for both default and addon airports using primarily third party airliners.

I used GSX in P3D and was satisfied with that experience if that helps as a reference point.

Thanks for any insights.

Marshalling works 100%  without any profile/config on every airport for the PMDG, Fenix, CRJ and probably anything else.

It would only "fail" when the scenery developer somehow has painted the parking spots completely different than how he set the data (like: he set the airport data for parking spot 1 on coordinates XXX/YYY, but somehow painted the parking spot with 5m offset to the right. In this case the marshaller would stand where the data tells him to, which would be 5m to the left). But I've not seen this on MSFS yet; this would have been detected already because MSFS default also uses this data for its ground services. So no worries.

2 hours ago, jarmstro said:

So you have to edit the file so it points to the file in the community folder.

You shouldn't as long as the .bgl file is the exact same name. Which it should be.

Edited August 30, 20223 yr by Tuskin38

4 hours ago, Fiorentoni said:

Marshalling works 100%  without any profile/config on every airport for the PMDG, Fenix, CRJ and probably anything else.

Perfect, thanks very much for the quick response.  Looks like I'll be taking the plunge on this shortly.

@virtuali Umberto, on a lighter note, now that this is out of the way, how are we looking on KIAH? I know you're probably still drowning with GSX support, but do you have timeframe now? 

Really hope there's a robust support and patching plan in place because this addon has been a disaster for me.

Have spent the last 5 hours troubleshooting and still haven't seen a single ground service. Torn between waiting for an update and just doing a chargeback. Anyone with more experience with this dev able to say with confidence that the issues will be fixed?