FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: conguero01 on June 03, 2016, 01:59:52 pm
-
Update GSX to the May 2016 Version and I'm not able to use GSX at certain airport TJSJ Saying no parking at this airport
-
Try to Coautl Restart with a cache rebuild. The new Couatl has an option in the Couatl settings menu.
If still doesn't work, perhaps the program is looking at the wrong AFCAD. If you open the parking customization dialog, the window will tell you from which AFCAD GSX is taking data from.
-
Try to Coautl Restart with a cache rebuild. The new Couatl has an option in the Couatl settings menu.
If still doesn't work, perhaps the program is looking at the wrong AFCAD. If you open the parking customization dialog, the window will tell you from which AFCAD GSX is taking data from.
How would we find the parking customization dialog?
How would we get the correct afcad to make it work ?
-
How would we find the parking customization dialog?
From the GSX menu, the customize airport positions menu entry.
How would we get the correct afcad to make it work ?
FIRST, check which AFCAD is in use and, depending on what it says, the solution changes.
-
How would we find the parking customization dialog?
From the GSX menu, the customize airport positions menu entry.
How would we get the correct afcad to make it work ?
FIRST, check which AFCAD is in use and, depending on what it says, the solution changes.
Will there be an update to GSX that will fix the afcads to make them work like they did prior to the upgrade?
-
Will there be an update to GSX that will fix the afcads to make them work like they did prior to the upgrade?
I've asked:
FIRST, check which AFCAD is in use and, depending on what it says, the solution changes.
AFTER we check this, we can discuss what the problem really is, and if a "fix" is really needed. I also suggested to do this:
Try to Coautl Restart with a cache rebuild. The new Couatl has an option in the Couatl settings menu.
Have you done that ? Awaiting for your report.
-
Prior to GSX's update, Gate 2 at MMAA was working with GSX, after the update, many gates/parking has stopped working. I did "rebuild cache" Nothing change.
Same for Winnipeg, it has 21 gates, GSX cut down to only 3 gates. I could not figure how to force GSX to use ALL gates...
-
Prior to GSX's update, Gate 2 at MMAA was working with GSX, after the update, many gates/parking has stopped working. I did "rebuild cache" Nothing change.
The thread is about the supposed misread of the wrong AFCAD but, in that case, you should see either no parkings, or a different list that doesn't show the parkings you are expecting to have.
Your screenshot for MMAA shows that Parking 2 (assuming is the same you called "Gate 2") is there, which means the AFCAD has been read correctly, which is what this thread was about.
What do you mean with "stopped working" ?
Same for Winnipeg, it has 21 gates, GSX cut down to only 3 gates. I could not figure how to force GSX to use ALL gates...
This is not "the same". This, as I've said above, might an issue of reading the wrong AFCAD but, again, since you haven't indicated WHICH AFCAD is used in this case, it's not possible to say why an AFCAD is used instead of another.
-
Before the update, I had no problem having the GSX there before I park at Gate 2. After update, it won't work, it kept saying "The parking is isolated. No Ground service available". I slewed around and tested to see if it works. Nothing.
-
After update, it won't work, it kept saying "The parking is isolated. No Ground service available". I slewed around and tested to see if it works.
AHHH, finally something useful! Warning messages are there for a reason, so you can understand the problem is NOT caused by GSX, but the scenery has an issue that, in previous versions, would probably cause a crash.
The updated version CORRECTLY DETECTS a problem found in so many 3rd party sceneries that had mistakes like these. In this case, it's an orphaned parking. Such parkings would likely cause errors with some services, because they wouldn't be able to reach that parking. Even AI planes cannot use them.
You think it "worked" before, but only because you might got lucky in the random selection of the departure place for the vehicles but, sooner or later, you would have seen a GSX error message, because it couldn't calculate the optimal path for the vehicles to reach that parking, since there are NO paths connecting to it, and this is obviously an error of the scenery.
So, instead of just crashing, we know give a warning, so it would have been clear that GSX is correctly and intentionally discarding a parking for a reason, not because of some GSX "bug".
Or, at least, we THOUGHT the message was clear enough. Apparently, it isn't...
-
Hello:
I'm having the same error at TJSJ. GSX was working fine until I bought and install KMEM. GSX says No Parking available at this airport. I I restarted coualt with airport cache, downloaded GSX again and uninstalled and re-installed it, disable and enable again GSX, check where GSX was getting the afcad and it is getting it from the right location, so I'm out of ideas what to do.
Raul
-
I'm having the same error at TJSJ
What error ? There are two issues being discussed here.
The "The parking is isolated. No Ground service available", which is NOT an error
OR
The "No parking at this airport", which usually indicate the AFCAD being used is not the one containing parkings.
-
At CYYZ, there are several gates available, but it kept saying "No parking at this airport" Before the update, the menu showed all gates with status i.e. available in 5 minutes, etc.
I now regret that I updated my GSX. I miss the original GSX, it worked perfectly for all airports before! :'(
-
At CYYZ, there are several gates available, but it kept saying "No parking at this airport" Before the update, the menu showed all gates with status i.e. available in 5 minutes, etc.
I now regret that I updated my GSX. I miss the original GSX, it worked perfectly for all airports before! :'(
I now have the same issue with FlyTampa Sydney (YSSY). This was working perfectly fine before I did the full installer last night.
Nothing has changed in my system except the new GSX version.
When I go the parking position customize menu option, I see no parking slots available.
-
This new version has left GSX not working at a ton of airports. See my "multiple pye files missing" thread. Major step backwards from the end user point of view. So what is the end user supposed to do now? Wish I had my old version, GSX worked just fine with no errors at all the airports it now does not. 6 think when FSCrew releases Ultimate Ground Crew I'll have to give that a try as this simply is not worth it. Even at places like Flightbeam newest SFO, GSX gives me a grand total of 5 parking spots to choose from upon landing in a 737. Ridiculous...
-
+1 for the No Parking at this Airport issue. I updated GSX last night and now no parking is available at SXAD's KBNA airport. Rebuilding the cache did not help and it is pointing to the correct AFCAD file in the SXAD folder. This issue seems to be widespread so hopefully they will issue a fix or roll it back.
-
+1 for the No Parking at this Airport issue. I updated GSX last night and now no parking is available at SXAD's KBNA airport. Rebuilding the cache did not help and it is pointing to the correct AFCAD file in the SXAD folder. This issue seems to be widespread so hopefully they will issue a fix or roll it back.
I have the exact same issue at SXAD KBNA just a few minutes ago, this was the last of several airports I have had this issue with which prompted me to post here. At least I know I am not the only one having these issues.
-
This new version has left GSX not working at a ton of airports. See my "multiple pye files missing" thread
Which I already replied to, it doesn't have anything to do with this issue.
Even at places like Flightbeam newest SFO, GSX gives me a grand total of 5 parking spots to choose from upon landing in a 737. Ridiculous...
I have several pages of parking positions at Flightbeam KSFO. Just checked now. As discussed in all threads about missing parking spots, whenever you report something like this, the FIRST thing to check is which AFCAD is being used by GSX.
If it's reading the correct one, then we might start investigating why you don't have all the parkings.
-
This new version has left GSX not working at a ton of airports. See my "multiple pye files missing" thread
Which I already replied to, it doesn't have anything to do with this issue.
Even at places like Flightbeam newest SFO, GSX gives me a grand total of 5 parking spots to choose from upon landing in a 737. Ridiculous...
I have several pages of parking positions at Flightbeam KSFO. Just checked now. As discussed in all threads about missing parking spots, whenever you report something like this, the FIRST thing to check is which AFCAD is being used by GSX.
If it's reading the correct one, then we might start investigating why you don't have all the parkings.
Umberto, with all due respect, why is it now much more work for the end user? Why when everything worked just fine with the previous versions and now the end user must go and try to find the correct afcad to use? Why have you all made it more work? I have a ton of airports I have to go through now. I'm not even sure if it's worth it. Why can't GSX scan for the right one? I don't even know what to look for. I assure you from the end user point of view this is a big step backwards. I personally may have to look at going with the upcoming UGC from FSCrew.
-
Umberto, with all due respect, why is it now much more work for the end user? Why when everything worked just fine with the previous versions and now the end user must go and try to find the correct afcad to use? Why have you all made it more work?
Slow down...we ALREADY found a better solution, which is already online now ( requires a Stand-Alone Addon Manager update, since it will have to download an updated Couatl.exe ), that automatically discards such airports, that seem to share the fact they don't have any parkings.
The REASON for this change was, of course, to make the program MORE user friendly, we overdue it, and it kinda backfired...let's explain it:
- Previously, we automatically discarded AFCADs with no parkings, no questions asked, no checks made. However, some users were confused by the resulting message "Cannot find valid AFCAD data at this position", usually because they landed in a very small airfield with no parkings, just a simple strip. There are many like that, in the default scenery.
So, we wanted to display a more user-friendly message, saying that while we DID found an AFCAD, it didn't contained any parkings, so we had to check every file, but flag the ones with no parkings as such, so we could display a more precise reason why the airport couldn't be used.
However, this was a problem when TWO (or more) "competing" airport were in the same place, or very close: in this case, we should have taken into account the aforementioned flag, to silently discard that airport, since there was a "better" alternative.
Now, the updated Couatl.exe which is online now, does this additional check, so it shouldn't be necessary to use the airport_visibility parameter anymore. UNLESS, of course, those additional airports DO have their own parkings so in that case, you'll have to decide if you want to remove them ( setting airport_visibility to 0 ) or KEEP THEM, but with a very low visibility level, such as 0.5 or less, so you could have a separate military base or helipad working with GSX too, with the "main" airport taking control again, when you exit from that small area.
-
Well, that was a fast fix then. Well done gentlemen. Unfortunately I have this Tropical Storm in the Gulf of Mexico to contend with at work but will try this out tomorrow afternoon. Thank you
-
Downloaded standalone manager and updated, now it says "No valid AFCAD for this airport." at MMAA. I am parking at Gate 3 with a jetway. It did work prior to chaos update. I added airport_visibility_MMAA = 0 in Coault.ini, nothing works. Please help.
-
Downloaded standalone manager and updated, now it says "No valid AFCAD for this airport." at MMAA. I am parking at Gate 3 with a jetway. It did work prior to chaos update. I added airport_visibility_MMAA = 0 in Coault.ini, nothing works. Please help.
Oh boy... Not good.
-
Good Morning
I bought this product thinking I could use it at all airports where ground operation , and after this last update I encounter that no longer works , such as at airports ( LEGR , LEAM , LEMG , etc ) as before if it worked properly. What is due ?
Thank you very much
:-\ :-\ :-\
-
Downloaded standalone manager and updated, now it says "No valid AFCAD for this airport." at MMAA. I am parking at Gate 3 with a jetway. It did work prior to chaos update. I added airport_visibility_MMAA = 0 in Coault.ini, nothing works. Please help.
Well, of course it's not working.
You said you want to exclude MMMA (setting the visibility to 0) so, since with the new update, the smaller auxiliary airports with nor parkings are automatically removed, the program doesn't any other choice that follow your orders, and exclude the only MMAA it can find...
-
I removed airport_visibility_MMAA = 0 and finally GSX is back to live, only to see one baggage cart invisible or should I say GHOST! Is there any way to fix that?
-
Scratch that!! I updated again and now it's working. Sorry to be a bother.
Umberto, have you figured out how to get my KIAH to work? I've been eager to fly into KIAH soon.
Cheers ;D
-
Umberto, have you figured out how to get my KIAH to work? I've been eager to fly into KIAH soon.
Have you installed the latest version ? Please reply in the KIAH section, because discussing about KIAH in this thread will just confuse everybody following it.
-
I have the same Problem.
Would it be possible to relocate the afcad folder by our own? At the moment there is no possibility to change the location, even it is wrong located.
-
Hello
I uninstalled all , I have reinstalled with the last update and still does not work . I have tried all the possibilities I have read in the forum and not get it to work . I add screenshots for showing me what I have misconfigured .
Thank you
-
I uninstalled all , I have reinstalled with the last update and still does not work . I have tried all the possibilities I have read in the forum and not get it to work . I add screenshots for showing me what I have misconfigured .
You haven't misconfigured anything and, from your screenshot, it shows that GSX is using what looks like a proper AFCAD.
If you look at the message from GSX on top of the screen, it's different now, and it's not telling you it cannot find the parking or the AFCAD. It's telling you it cannot use this specific parking, because is ISOLATED.
An isolated parking it's a parking that is not connected to anything, so it's surely an error made by the scenery developer, because no AI will use it and surely GSX cannot calculate a proper path for vehicles to reach it.
Detection of isolated parkings with a warning message has been added to GSX, because in previous version you would probably see a crash report.
So, everything's working correctly, you just tried a bugged scenery now, which GSX now handles gracefully without crashing.
-
Hi Umberto,
I just landed at CYYZ. On the way in, I selected the airport and the gate I wanted (Gate 168). I landed and taxied to the gate. The equipment was waiting just like it is supposed to. I parked, shut down and pressed CTL F12 to request de boarding. I got the dreaded NO Parkings at this airport message. That was a first. I checked the AFCAD and it appears to be the correct Fly Tampa AFCAD for CYYZ. I will re start FSX and take a look in a bit.
Scott
-
I selected the airport and the gate I wanted (Gate 168). I landed and taxied to the gate. The equipment was waiting just like it is supposed to. I parked, shut down and pressed CTL F12 to request de boarding. I got the dreaded NO Parkings at this airport message.
This seems to indicate the correct AFCAD was in use when you first selected the parking (otherwise you wouldn't be able to select it in the first place), but when you moved at the gate, ANOTHER AFCAD kicked in, this because it's center was closed to the main one.
So, check again the correct AFCAD is in use even when you are at THAT parking, and note its name/icao. And, you can then exclude it, if necessary.