I've put this on the forum for GSX, but no one, not even the manufacturer has come back to me about this software.  It is particularly annoying because it was good software that doesn't do anything anymore, despite the forums containing other people with the same problem. Here is what my issue is:

• Before today, I have had no problems, but for some reason, now I have loaded up my aircraft in the same position as yesterday, at the same airport, and from CTRL+SHIFT+F12, I - for some reason get the SELECT PARKING FACILITY screen...? 
  
  I told P3D what gate I want - the same as yesterday (when GSX didn't bring this screen up - yesterday it gave me the proper loading options, etc...).   But for some reasons, today, GSX doesn't think I'm at a gate - and the only thing I can therefore think, is that it's getting it's data from a different place to P3D for gate positions.  I have checked out the Scenery Library and it looks no different.  I have also rebuilt the airport cache.
  
  What has changed for this airport today?  Other replies talk about the Scenery Objects list - well here is mine - perhaps you could point out the problem! https://photos.app.goo.gl/tgt7ymbVWwTXhWfg9

Anyone being able to tell why the software I bought suddenly doesn't want to see where gates are in the airport - if you ask GSX to warp your plane to gate x, it is different to asking P3D to to take it to gate x - your plane ends up in a different place!

Any help would be appreciated....

Thanks, Gaz

 

Edited August 23, 20187 yr by Gary McCluskey

Could be that there is an afcad issue and that GSX is "reading" the wrong afcad. This could happen if there is more than 1 afcad for the airport in question.

When you open the GSX airport customization menu you will find ( at the top) an indication which afcad GSX is using for its actions. You could either disable a possible  wrong afcad or follow the procedure that GSX has ( as explained in the manual) to tell GSX to only use the afcad of your preference.

The scenery library will not give you any information in this aspect.

b rdgs Dick

Edited August 23, 20187 yr by dick

Thanks for getting back to me - you're the only person who has!

I've looked in the settings in the APP, and I can see it seems to be looking at the wrong AFCAD file. (I assume AFCAD files are BGL files??). See here : https://photos.app.goo.gl/j1N7wJwHJxrJ3KaG9

There is nothing there though to click and point me to another BGL file... I have found the BGL file that was originally being used (and correct), but I don't know how to tell GSX to look at a different file.

I have found  an ini file in %AppData%\Roaming\Virtuali\GSX\ egnt-qrpvuk.ini and I don't know why that's there. In it, it points to a BGL which is NOT part of the scenery I want to use.  If I edit the file, and point it towards the correct scenery it makes no difference at all! I'm back to square one.

Gaz

yes, afcad's are mostly bgl files. Just put ".off" behind  "bgl" in the name of file and GSX and P3D will ignore it.

So it should look like this  ###_egnt.bgl.off

Read the GSX manual.. it is all in there..

b rdgs Dick

This isn't a GSX problem; it's a bigger problem with you having multiple ADE (aka AFCAD) files active for the same airport, which can cause all sorts of unhappiness.

This particular ADE you are seeing is part of ORBX's FTX England regional scenery.  If you are using another airport add-on for EGNT (like UK2000), you have to disable the ORBX ADE or both will be active.  Additionally, there are often other (e.g. objects and cvx) ADE files associated with the fields ORBX buffed-up in its regional scenery that should be disabled when running another airport add-on.  Usually, searching for any file with the ICAO airport identifier (i.e. EGNT) in the ORBX "FTXxxxx_05_Scenery" subdirectory will find those files for a particular airport.  Also, be aware that ORBX' FTXCentral configuration manager program looks for missing bgl files as part of its housekeeping and can/will reinstall that bgl file you disabled without you realizing it, putting you back into the same position.  I created a batch file that disables all of the conflicting ORBX airport ADEs (I move them to a hold directory rather than using the .off method Dick describes above), and I run that batch file every time I finish with FTXCentral to make sure that all the conflicting ADEs remain disabled.

Regards

 

Also, if using My Traffic 6, this will create havoc with UK2000, FTX England Afcads as I once found out when GSX used MT Afcads and the aircraft positioning were out of sync.

15 hours ago, Gary McCluskey said:

I've put this on the forum for GSX, but no one, not even the manufacturer has come back to me about this software. 

You posted this on FSDT forum yesterday in the late afternoon (our time, which is CET), and you have been replied to this afternoon (our time).

http://www.fsdreamteam.com/forum/index.php/topic,18295.0.html

I'd say it would be customary to wait AT LEAST 24 business hours (considering timezones), before complaining about a supposed lack of support, but when you made this post (15 hours ago), it was about 3:00 AM HERE!

Yes, an AFCAD conflict is the most likely cause. Why is why GSX will tell you from which file is taking the parking data from.

Edited August 23, 20187 yr by virtuali

I now have this fixed, but I will go into the forum for the GSX software and let them know because I haven't heard from them, despite logging the problem yesterday, and also the fact that I think their software sucks!

I have changed NOTHING on my system. I was using ORBX before, which gave me two files: ADE_FTX_ENG_EGNT_CVX.bgl and ADE_FTX_ENG_EGNT.BGL.  I have renamed them with the '.old' file extension, and it has fixed it after I regenerated the airports in P3D.

WHY have I had to use a rubbish piece of software that does not even give me a front-end to do this? I have to go through the back-end of the Windows file system to fix something, and I don't know caused the problem!  If it gives you a front end to change the docking/gate positions, I can understand it will want to override the setting in the Scenery Objects library, but surely someone can say why this becomes a read-only area of the airport manager in GSX...?  Why can't you browse for another BGL file, or revert to the original???

By the way - I HAD read all of the documentation, and it didn't help...

Gaz

34 minutes ago, Gary McCluskey said:

I now have this fixed, but I will go into the forum for the GSX software and let them know because I haven't heard from them, despite logging the problem yesterday, and also the fact that I think their software sucks!

FSDT replied to you in the post you replied to.  Take it easy, take a breath.

I had the same issiue but for me it was traffic global.  After disabling some of the .bgl`s it worked flawles again.

1 hour ago, Gary McCluskey said:

I now have this fixed, but I will go into the forum for the GSX software and let them know because I haven't heard from them, despite logging the problem yesterday, and also the fact that I think their software sucks!

I have changed NOTHING on my system. I was using ORBX before, which gave me two files: ADE_FTX_ENG_EGNT_CVX.bgl and ADE_FTX_ENG_EGNT.BGL.  I have renamed them with the '.old' file extension, and it has fixed it after I regenerated the airports in P3D.

WHY have I had to use a rubbish piece of software that does not even give me a front-end to do this? I have to go through the back-end of the Windows file system to fix something, and I don't know caused the problem!  If it gives you a front end to change the docking/gate positions, I can understand it will want to override the setting in the Scenery Objects library, but surely someone can say why this becomes a read-only area of the airport manager in GSX...?  Why can't you browse for another BGL file, or revert to the original???

By the way - I HAD read all of the documentation, and it didn't help...

Gaz

Umberto (Virtuali), the guy posting above you, is "them."

Your configuration had multiple ADEs active for the same airport.  Whether or not it appeared to work before or not, duplication of ADEs is a potentially serious configuration error.  There are tools you can use to locate ADE duplication problems, like Simple Airport Scanner, found on the ScruffyDuck website.  GSX is not a scenery manager, was never intended to be and was never marketed as such.  It only reports the highest-priority airport file it found by parsing the P3D scenery configuration--and that's what it then uses.  If you want it to use something else, then you have to properly manage your scenery configuration to that end.  A rubbish scenery configuration rife with duplicates, out-of-order entries etc will lead to rubbish results--not just with GSX, but with the core sim and many other add-ons.  It's really not reasonable to trash an add-on for not dealing with the bad data in your system the way you would like.

Regards

 

1 hour ago, virtuali said:

Yes, an AFCAD conflict is the most likely cause. Why is why GSX will tell you from which file is taking the parking data from.

That doesn't answer any of my other questions -particularly the front end!

- Why do I have to use the file operating system to tell your software what bgl to use. If it finds a bgl for the airport i'm using, and I don't like that bgl, there's no buttons to allow me to browse for the original bgl.

- I have made no changes to my system. One day it worked, the next it didn't, and I could find that GSX had created it's own BGL file for EGNT, with completely wacky parking areas!

 

Sorry for me sounding like I'd gotten angry really quickly, but when I read other threads with the same problem, and the answer from yourself is to either 'read the manual' or 'there's an easy fix, read the forum', then surely that should be telling you something; you have to look at this from the end users point of view...

32 minutes ago, 331BK said:

I had the same issiue but for me it was traffic global.  After disabling some of the .bgl`s it worked flawles again.

Indeed.  MyTraffic and the ORBX regional sceneries both add hundreds of airport ADE files to the scenery configuration that are not directly visible in either the scenery config or in scenery manager programs.  Every time I install a new add-on airport, I check both the MyTraffic and ORBX regionals and freeware scenery folders for individual bgls, and disable them when found.  MyTraffic, in particular, has airport files for the vast majority of medium-to-large airfields around the world, so most new addons need a corresponding "fix" in the MyTraffic folder.

Regards

 

12 minutes ago, w6kd said:

Your configuration had multiple ADEs active for the same airport. 

Why? If no changes had been made in my system, why did it decide to create its own extra ADE? where did it get its parking locations from? 

 

13 minutes ago, w6kd said:

It only reports the highest-priority airport file it found by parsing the P3D scenery configuration--and that's what it then uses.  If you want it to use something else, then you have to properly manage your scenery configuration to that end

The highest Priory file was the UK2000 scenery for EGNT. that has always been the case and still is, see my screenshot of my Scenery Library above. I can understand if you want to override this so that you can change settings for gates, but I didn't do that, and without going into the file system there was no way of me telling GSX that it had to use the one it was using before (the original) . Where it got the extra rubbish for ENGT, that overrode the original settings, I don't know. 

18 minutes ago, Gary McCluskey said:

Why? If no changes had been made in my system, why did it decide to create its own extra ADE? where did it get its parking locations from? 

 

The highest Priory file was the UK2000 scenery for EGNT. that has always been the case and still is, see my screenshot of my Scenery Library above. I can understand if you want to override this so that you can change settings for gates, but I didn't do that, and without going into the file system there was no way of me telling GSX that it had to use the one it was using before (the original) . Where it got the extra rubbish for ENGT, that overrode the original settings, I don't know. 

You have (had?) two ADEs for Newcastle--both of which you (perhaps unknowingly) installed...one was installed with the ORBX FTX England regional scenery, the other with the UK2000 Newcastle scenery.  That, right there, is your problem!!  When you put a second scenery over another, there is a tangled morass of exclusions, conflicting/overlapping objects, etc.  One at a time is the Golden Rule...been like that in the MS based sims for a very long time.  As you discovered, getting rid of the ORBX ADE allowed the UK2000 one to work properly.

There is no safe way to leave both of those sceneries active at the same time and just switch GSX between them.  A "front-end" that would allow you to tell GSX which of two conflicting ADEs to use would not address all the other conflicts that result from having the two ADEs (and other scenery files) stepping all over each other.  The "A" answer is to manage your scenery config so that there is one and only one airport file for any given airport.

One exception to this is within ORBX itself, in that they do have airport files in their regional sceneries and duplicates in their full-featured add-on airport sceneries layered above the regional stuff...but they have detailed insider knowledge of where all the exclusions and objects are, and they can layer one on top of the other with all of the pieces dovetailed together properly.  That pretty much never works when putting a non-ORBX airport on top of one defined in an ORBX regional scenery.  You need to disable the ORBX airport file (and any associated bgls, including objects and cvx files plus any elevation bgl in the scenery\world\scenery folder) to make the 3rd party airport work right.

Regards