6 hours ago, virtuali said:

Now, there's another yet undocumented feature, which we added in THIS update, which I haven't time to write any docs for, because I'm spending all my time to chase something I can't reproduce and it's the ability to load a separate AFCAD made JUST for GSX by placing, of course, in the %APPDATA%\Virtuali\GSX folder, together with its eventual GSX .INI profile.

Cache regeneration for me is 1-2 seconds. I have 981GB of P3D installs across 2 SSD's and 1 M.2 drive. All relevant folders including the Documents Prepar3D v5 Add-ons folder are excluded from the Windows anti-virus software.

Thank you Umberto for adding the feature of putting a AFCAD BGL file in the ...\AppData\Roaming\Virtuali\GSX folder. Had a chance to try it out by editing some vehicle paths and saving the BGL file to the GSX folder. Worked flawlessly. Don't have the baggage cart drivers running into each other.

23 hours ago, virtuali said:

No, it will be lost ONLY if you directly edit the stock rules files in the Addon Manager\texture folder.

Like many other files ( GSX airport profiles, airplane profiles, etc. ), you can work on your own custom rules file, which will override the stock rules, if it's located in the %APPDATA%\Virtuali\GSX\texture folder.

So, just create a copy of the stock rules files there, and edit them to your liking, the updater won't touch them and, like anything in the %APPDATA% folders for GSX, they have an higher priority over the stock files.

I'm sorry because it's not really documented, we explained the 3rd level of customization ( the single rules.cfg for a single custom operator with a custom texture, that works only with P3D4 ), but not this 2nd level, which is a custom overall set of rules files.

Thanks for the reply, that seems only like a basic solution to me... Is there any way to match one handler to one airline at one airport and a different handler to the same airline on a different airport?

For example look at Frontiers Jobs page here to get an idea of how many different entries and options would be needed for one airline only... Then again there are major airports that have only one ground handling provider for all airlines but this one is missing from GSX so every given option is not real (Ok I admit this is complaning on a high level because there are thousands of ground handlers world wide...!)

BTW I noticed a small bug on the afcad scan, I only ran into it once with a scenery, this one came with an add-on.xml where all paths came like this:  

<AddOn.Component>
    <Category>Scenery</Category>
    <Path>.\XXX</Path>

P3D and some programs like EFBs where able to find the AFCAD in this path starting with ".\" but GSX was unable and selected the stock AFCAD, had to change the add-on.xml manually to get GSX started.

3 hours ago, DLH7LA said:

Thanks for the reply, that seems only like a basic solution to me... Is there any way to match one handler to one airline at one airport and a different handler to the same airline on a different airport?

Of course there is, that's how the rules.cfg works, in relationship with airline *parking* codes.

But I suspect with "airline" you meant the airline you are flying ? GSX doesn't match the airline you fly. It only use the parking code of the airport to give a better preference amongst multiple candidates at an equal score, provided they are assigned to that airport in the first place, to prevent silly situations as having your own crew following everywhere in the world. 

The airline you are flying affects only the choice of ULDs so, if your aircraft.cfg has the right airline codes, the airplane won't load an ULD on departure and unload a different one on arrival.

And yes, of course this logic might be improve to add an extra level, that is "the handler your airline would PREFER (if available) to use on a certain airport", which might add an extra layer of customization, but we just don't have it yet, that doesn't obviously mean we don't understand it might be useful.

 

3 hours ago, DLH7LA said:

P3D and some programs like EFBs where able to find the AFCAD in this path starting with ".\" but GSX was unable and selected the stock AFCAD, had to change the add-on.xml manually to get GSX started.

Noted, I think it has always been like this.

Edited September 10, 20214 yr by virtuali

The FSDT forum is giving me a database error when I try to post this, but I have been able to reproduce and propose a workaround for those who still have an "unrecoverable error" when selecting catering service...

I had the same issue as ChuckOman and cfso6342; an "unrecoverable error" when selecting catering service. Deboarding, fueling, boarding, and pushback operations work as normal. Only the catering option would throw an "unrecoverable error". This error condition would trigger no matter which airport or catering operator was selected. I then removed the GSX.CFG file I had made for the PMDG 737. 

No "unrecoverable errors" were thrown once the airplane configuration file was removed from the %APPDATA%\Virtuali\Airplanes\AirplaneName folder.  I then created a new configuration file for testing. At first, I only unselected "Use GSX traffic cones" to create a new GSX.CFG for the PMDG 737. Again, all GSX operations worked normally without error.

However, when editing the service door 1 position to “No door at this position”, this new configuration would throw an "unrecoverable error" when selecting the catering option.

Please check for an airplane configuration in a GSX.CFG file, (located in the %APPDATA%\Virtuali\Airplanes\AirplaneName folder) and remove to test.

In my case, I can reproduce the exception CREATE_OBJECT_FAILED in call AICreateSimulatedObject param #1 'FSDT_Catering_Van_CZ' every instance an user airplane configuration file is used, with a “No door at this position”  selected at a catering door position.  Again, this will occur when selecting any catering operator at any airport.  It is the GSX.CFG file that will lead to the error.

I hope this will help lead the team to a robust solution to this issue.

-Thanks, Scott

This problem is already fixed by running the updater. As I've said on our forum too, not all users will get the latest files at the same time, but everybody eventually will, usually in about 24 hours ( but normally less )

Edited September 20, 20214 yr by virtuali

36 minutes ago, virtuali said:

This problem is already fixed by running the updater. As I've said on our forum too, not all users will get the latest files at the same time, but everybody eventually will, usually in about 24 hours ( but normally less )

Thank you, all is working great on my system after today's update.

The FSDT_Catering_Van_CZ file finally updated via Live Update! 
All is well again.  😀

Thank you for the excellent customer service that you always provide. 

Just checking in before reinstalling the latest. Is everything fixed, like the problem with the airport config program and all? One thing I had noticed was I the Lorby scenery tool had flagged a GSX conflict when I was having all the trouble. FWIW. Don't want to go through the trouble of putting it back in if people are still having issues. Thanks.

Ya, is GSX back to how it was before 2.9.4 was released with respect to stability and any other errors that people posted in this thread?

Mine seems to work fine now following the live updates. I don't have any custom configs though as some with those had reported some issues.

Be sure to run the live updates. 

All I can say is that I reinstalled and updated with the updated updater dated as of the date of this post. GSX isn't even on the menu. I posted over at their forum, but thought I'd mention it here since I asked. Have been using UGCX in the meantime, which is okay for what it does, but is not really a full-service graphics program. I do enjoy getting towed around the airport, though. I have had GSX for a long time, and am wondering why I'm having to troubleshoot an update so much this time. The install folders do not even look the same as before, so I don't know what is going on, except it doesn't even look like it installed. If I get an appropriate response over there, great, if not, I'll just move on.

Okay, this was apparently my mistake in installation. It is now installed and working as expected. If the problem with the airport cache and Coautl scripting engine not closing repeats, I'll revisit this. Thank you.