FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: BuddyDog on December 06, 2014, 06:39:09 pm
-
Ciao Umberto!
I recently installed the GSX 1.9 upgrade and vehicles and the de-icers work just fine, thank you for adding it on!
My problem ( which I guess is an AFCAD conflict) is after landing FSDT KLAX and FlightBeam KDEN, I taxi off the runway, hit Ctrl+F12 and it seems to not recognize that i am at either of those airports. I think at KDEN it thought I was at Aurora, CO with 5 parking spots and at KLAX, it only had parking 1-20 available (no Alpha letter terminal designations). When I just loaded an aircraft at a gate at KDEN to start a flight, it recognized the gate and GSX services were available.
Would it be correct to disable or uninstall all the add-on scenery, then delete the cache and restart. I did note when GSX update was installing it made some mention of AFCADs and I checked the "yes" box, but I must not have understood what it was saying.
Thanks in advance for your assistance!
-
Try to force a scenery cache rebuild, by removing the following folders:
C:\ProgramData\Microsoft\FSX\SceneryIndexes
C:\ProgramData\Virtuali\Couatl
Then, start FSX and wait for FSX and GSX caches to be rebuilt.
-
Ciao Umberto!
I did delete the files as you recommended and re-started FSX, then took a flight from FSDT KIAH to FlightBeam KDEN and still have the same problem at the arrival airport, no GSX services, only 5 parking spaces found.
Would it be best to uninstall GSX completely and do a full re-install?
Grazie!
-
I had a similar issue when landing at the default KOAK. GSX thought I was at Henderson Executive, which I found odd. Restarting GSX a few times eventually kicked it into gear. Similarly, I landed at KDEN later in the day and GSX thought I was somewhere else, though I didn't get a chance to see where. The only other time I ran into this issue pre-1.9 was at KPDX, where GSX would think I was at a small airport across the river, but it was simply a matter of getting closer to the terminal building to have PDX appear. In this case, no matter how clsoe to the "center" of the airport I am, GSX doesn't budge.
-
This sounds like the same issue that I have another thread on. KDEN only gives me 5 or six gates to park at and they are too small. I have not tried any of the other airports to see if it is happening there.
-
If rebuilding the cache hasn't fixed the problem, then it's not likely anything related to GSX, and might be just a conflict caused by another scenery.
Check what AFCAD is in used by GSX, by opening the parking customization dialog, and look what's the name of the ACAD used.
-
Ciao Umberto!
Alright here is what I tried and there does seem to be some problem with GSX when ARRIVING at an add on airport.
I took the Majestic DH8D, put it at Flightbeam KDEN B91 and checked the airport position in GSX which read:
C:/FSX/FLIGHTBEAM/KDEN/scenery/KDEN.bgl
I exited FSX, reloaded and Put the A/C at KEGE (Eagle County regional stock FSX airport), then flew a short hop from KEGE to KDEN. GSX worked at KEGE and noted the stock FSX settings for that airport.
Took off, flew to KDEN, again landing on RWY 35L, exited the runway and activated GSX.
I checked the setting in GSX for KDEN which now read:
C:/FSX/scenery/0202/scenery/APX20170.bgl
Taxied to Gate B91, still no GSX services, just wanted to know which parking space at Aurora, CO I wanted to use.
It would appear when landing at an add-on airport, GSX is reverting to the stock FSX airport AFCAD( at least that is what I think it is called), but in this instance, it thinks Denver is Aurora, CO.
I exited FSX, started it again with the same A/C at KDEN B91, and GSX again recognizes the settings:
C:/FSX/FLIGHTBEAM/KDEN/scenery/KDEN.bgl
I did not have this issue prior to updating to version 1.9.
So, uninstall GSX and start from scratch or some other fix? ???
Grazie!!
-
Ciao Umberto!
I did delete the files as you recommended and re-started FSX, then took a flight from FSDT KIAH to FlightBeam KDEN and still have the same problem at the arrival airport, no GSX services, only 5 parking spaces found.
Would it be best to uninstall GSX completely and do a full re-install?
Grazie!
Did you wait for the cache rebuild to complete? It can take from 5 to 10 minutes. If you want to watch the status, go to a FSDT airport, the cache will start to rebuild. Push control-f12 and the status will display in the upper left corner. If the status goes away, push again to get it back. It's complete when the status disappears and the gsx menu appears.
John
-
I have the same problem. Airports that were normal and some add-on have the wrong AFCAD. I tried also removing the cache and scenery indexes but no luck. Will uninstalling GSX fix this problem? Thank you.
-
Ciao Umberto!
I did delete the files as you recommended and re-started FSX, then took a flight from FSDT KIAH to FlightBeam KDEN and still have the same problem at the arrival airport, no GSX services, only 5 parking spaces found.
Would it be best to uninstall GSX completely and do a full re-install?
Grazie!
Did you wait for the cache rebuild to complete? It can take from 5 to 10 minutes. If you want to watch the status, go to a FSDT airport, the cache will start to rebuild. Push control-f12 and the status will display in the upper left corner. If the status goes away, push again to get it back. It's complete when the status disappears and the gsx menu appears.
John
Yes, I did.
Just for giggles, I put the DH8D at Aurora, CO airport, checked the GSX settings and got this:
C:/FSX/scenery/0202/scenery/APX20170.bgl
The same as I had on arriving at KDEN.
-
Just for giggles, I put the DH8D at Aurora, CO airport, checked the GSX settings and got this:
C:/FSX/scenery/0202/scenery/APX20170.bgl
The same as I had on arriving at KDEN.
I tried doing the same you did: took off from KEGE, and arrived to KDEN, which is basically a straight eastward route.
GSX correctly loaded the C:/FSX/FLIGHTBEAM/KDEN/scenery/KDEN.bgl and the related GSX airport customization file that come with the scenery when it was about 3-4 NM inbound the airport.
I can't explain what happened on your system, but it surely works normally here.
Try to use the "Restart Couatl" option on your approach, and see if the correct .BGL is used then.
-
Thank you, Umberto.
I'll give it a try next time I fly.
-
Ciao Umberto!
I did delete the files as you recommended and re-started FSX, then took a flight from FSDT KIAH to FlightBeam KDEN and still have the same problem at the arrival airport, no GSX services, only 5 parking spaces found.
Would it be best to uninstall GSX completely and do a full re-install?
Grazie!
Did you wait for the cache rebuild to complete? It can take from 5 to 10 minutes. If you want to watch the status, go to a FSDT airport, the cache will start to rebuild. Push control-f12 and the status will display in the upper left corner. If the status goes away, push again to get it back. It's complete when the status disappears and the gsx menu appears.
John
Yes, I did.
Just for giggles, I put the DH8D at Aurora, CO airport, checked the GSX settings and got this:
C:/FSX/scenery/0202/scenery/APX20170.bgl
The same as I had on arriving at KDEN.
Starting at KDEN I assume everything is normal? What about if you fly from KDEN to another FSDT or Flightbeam airport? Does it work fine that way?
John
-
I have not tried from KDEN to another add-on, BUT prior to that, I started at stock KSEA, flew to FSDT KLAX and it would not recognize KLAX, just 20 parking spots with no GSX service at the FSDT gates.
I am now rolling back my config to prior to the GSX update 1.9 (version 1.8.9) and will see how that works, then uninstall and do a full reinstall of GSX.
-
I deleted the files and followed the directions above to reset the cache. I then flew a short flight from the nearest airport to KDEN. I saw a short prompt that indicated that the files were 78% rebuilt (or something like that). I waited a very short time and then checked the AFCAD as directed above. I had KDEN AFCAD and all was well. I did the same thing for KLAS, KSFO and KPHX and it worked at each of the airports.
-
I have now deleted those files twice, let the scenery rebuild (I am running of a SSD so it seems to go very fast), still have the same problem. I decided to restore the system to today, as the roll back seemed to cause FSX to not start.
I think my next step should be an uninstall of GSX, then a full reinstall and paying attention to what the pop-up says on install about AFCADs.
Don't know if it makes a difference or not, but this is Win 7 and FSX is running alone (ie not in C:\program files\FSX but C:\FSX).
I am stumped!!!
-
I am now rolling back my config to prior to the GSX update 1.9 (version 1.8.9) and will see how that works, then uninstall and do a full reinstall of GSX.
Don't try to do that. It will cause a big mess of everything because, after a Major Update, you can't go back to a previous version, unless you install with the network cable disconnected.
So, if you want to do it as a test, that's fine, but just don't do it and if you find any difference, REPORT IT, and don't use the old version.
-
Ciao Umberto!
I uninstalled GSX and did a full re-install with the new installer tonight.
While it was installing I received a pop-up message asking if I wanted to update the AFCAD's. When I first installed it, I said yes ( and had the problem), this time I said no. It does not seem to make a difference, when I arrive at KDEN, it still only has the parking assignments for Aurora airpark, which is about 8 miles S of RWY 35L.
Any suggestions how to clear the conflict? Keep in mind I am not a computer whiz.
Grazie!
-
I also did a fresh install of GSX. Landing at LAX from JFK (both FSDT), GSX showed me the "YouControl" option, but when I went to select parking options it showed me the list for nearby KHHR. I landed on runway 24R and ended up taxiing to gate 37A in Terminal 3. GSX did not recognize I was in LAX until I restarted coutal.
It's almost like GSX picked the airport I was closest to while on final approach and then refused to changed it.
-
Ciao Umberto!
An update to my situation. Today I did a flight from FlightBeam KSFO to FSDT KLAS, using the SUNST3 arrival for RWY 25L at Las Vegas. When I arrived at KLAS and taxied off the runway, GSX recognized where I was and all the services worked just fine, including Follow Me car, SafeDock and luggage cars.
In my experience so far, I only seem to have AFCAD problems with RWY 35L at KDEN and RWY 25L at KLAX.
Next to try is a South landing at KDEN and see what happens at RWY 16L.
Could there be something in the GSX upgrade that thinks KDEN 35L is Aurora airpark and KLAX 25L is another nearby airport.
Grazie for all your time and attention to my problem(s). :)
Buon Natalie! ;D
-
Ciao Umberto!
An update to my situation. Today I did a flight from FlightBeam KSFO to FSDT KLAS, using the SUNST3 arrival for RWY 25L at Las Vegas. When I arrived at KLAS and taxied off the runway, GSX recognized where I was and all the services worked just fine, including Follow Me car, SafeDock and luggage cars.
In my experience so far, I only seem to have AFCAD problems with RWY 35L at KDEN and RWY 25L at KLAX.
Next to try is a South landing at KDEN and see what happens at RWY 16L.
Could there be something in the GSX upgrade that thinks KDEN 35L is Aurora airpark and KLAX 25L is another nearby airport.
Grazie for all your time and attention to my problem(s). :)
Buon Natalie! ;D
I recall reading something in the release notes that mentioned adjusting how GSX determined where you were, maybe by changing the radius for airports? I get the feeling that when you land at an airport like KDEN, or at the edges of LAX and such, you are in an area with overlapping radiuses and so GSX thinks you're not where you are. It just doesn't adjust to the closer airport as you get closer to it, like it used to. (As I mentioned, this used to happen to me at KPDX where GSX thought I was at a smaller, uncontrolled field near the departure end of one of the runways).
-
O.K. I did some more testing and I am optimistic.
Took an A319, used RWY 35L at KDEN as my starting point, activated GSX, which recognized where I was and GSX services were available, along with all the terminals and gates.
Took the same aircraft, put it at RWY 25L at KLAX as the starting point, activated GSX and it recognized I was at KLAX and had all the terminals and services available.
I do not know, but could my problem be cured?
Umberto, does this make sense?
Grazie!!
-
I do not know, but could my problem be cured?
Umberto, does this make sense?
We are looking into it to find a better proper solution, because it seems there are issues when two airports are very close. As a temporary solution, you can disable the less important airport using the disable_on_airports option in the Couatladdons.ini file, as explained on the manual.
For example, in case of KDEN, you might want to disable the 01V icao, in order to not interfere with Flightbeam.
-
Hi Umberto!
I am having the same problem with major default airports that have smaller GA airports close by. For some reason v1.9 prefers the AFCAD for the small airfield rather than the major one. I am excluding the small ones using the technique you outlined in the manual but it seems I am having to do that with every airport. I am eagerly awaiting a better solution. Something different with this version because never had this problem with previous versions/updates.
Cheers!
Craig
-
Please apply the latest Live Update, we found what the problem was, and fixed it.
-
Thanks, Umberto!
Deleted my exclude airports and tested GSX at each and everything now seems to correctly recognize the proper AFCAD. Thanks for your quick fix.
-
Thank you so much, Umberto, for your patience with my problem. I am looking forward to more flights with GSX at arrivals.
Well done!!