FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Kurt on August 09, 2012, 11:14:07 am
-
At the new airport from Aerosoft "Fairbanks" PAFA got this message:
There are no parking available at this airport >:(
-
Same here. I would suspect this not being a GSX problem. No mentioning of this problem on the Aerosoft support forum sofar.
But still very intrested in a solution !
b rdgs Dick
-
Aerosoft distributes the competitor to GSX, I wouldn't expect any help from them.
-
"No parkings" seems strange, because it means GSX has read the AFCAD correctly, but couldn't find any parking spots, or maybe *usable* parking spots, meaning they should be properly connected to the taxiway network.
Another possible reason, is that the AFCAD is not self-contained, meaning it's not a complete AFCAD but, it just overrides something of the default one, so some information is in the default AFCAD and other in the one that comes scenery. OR, if the data is split through multiple AFCADs supplied with the scenery, which is basically the same issue. GSX do not support such configuration, which is not very common (although FSX itself can handle it), since most of the scenery developers (especially commercial ones), usually supply a self-contained AFCAD.
If someone could send me the AFCAD in use (indicated by GSX in the parking customization dialog), we can have a look at it.
-
Checked the files and there are actually 6 afcad files. The customization window indicates (when on the ground in PAFA) the afcad in use as the 2Z5 one... which seems to be "Chena River" and is recognized by FlightSimCommander as a very closeby bush airport. I changed the extension for the 2Z5 afcad file to .bak and GSX works fine now. The GSX manual does indicate an option to disable GSX on certain airports ( which I would have preferred) but as far as I understand the format to do so requires an Icao code which in this case we do not have. Or am I mistaken here ?
Virtuali : you still want the afcad files ?
b rdgs Dick
-
as far as I understand the format to do so requires an Icao code which in this case we do not have. Or am I mistaken here ?
It's not necessary the ICAO code being a real one, just that matches the one used by the AFCAD designer, there must be one for sure, regardless if it's real or not so, if you put that code in the GSX exclusion list, it should exclude the airport.
-
ok... I made an exception for this airport in the inifile using 2Z5 as airport code and renamed the 2Z5 afcad again with a .bgl extension. Now when I want to use GSX while on the ground at PAFA I get the reply : "GSX has been disabled on this airporty by user settings'. The customization window option is not active so I cannot verify which afcad is being used but seems likely that we are back on the 2Z5 afcad. Is there another way to force GSX to read the appropiate afcad apart from renaming the 2Z5 afcad with a .bak extension ?
thx your help !
b rdgs Dick
=
-
We'll need to update GSX to handle these special cases.
-
ok... I made an exception for this airport in the inifile using 2Z5 as airport code and renamed the 2Z5 afcad again with a .bgl extension. Now when I want to use GSX while on the ground at PAFA I get the reply : "GSX has been disabled on this airporty by user settings'. The customization window option is not active so I cannot verify which afcad is being used but seems likely that we are back on the 2Z5 afcad. Is there another way to force GSX to read the appropiate afcad apart from renaming the 2Z5 afcad with a .bak extension ?
thx your help !
b rdgs Dick
=
@ Umberto,
This is exactly the same issue I encountered with Simwings/Aerosoft PANC airport : http://www.fsdreamteam.com/forum/index.php?topic=6810.0
Thank you in advance,
Best Regards,
Richard Portier
-
At the new airport from Aerosoft "Fairbanks" PAFA got this message:
There are no parking available at this airport >:(
The reason is that there are multiple AFCAD files used for the airport to represent more realistic traffic. Some times when you click
on a spot such as the gate when you load up, it shows in the FSX screen as Fairbanks seaplane base. GSX is reading what it is
told. Not to likely to get pushback services in the water or anything else for that matter.
-
Could this be Aerosoft's subtle way of forcing AES use at their airports? ;)
-
Could this be Aerosoft's subtle way of forcing AES use at their airports? ;)
Not really, it's just that we haven't handled such cases in GSX, but we'll surely will.
-
Could this be Aerosoft's subtle way of forcing AES use at their airports? ;)
Not really, it's just that we haven't handled such cases in GSX, but we'll surely will.
Thanks Umberto, this not being a GSX problem, you are still willing to find a way around it. Your support is great.
-
Here is a quick fix, be it only a temp fix. I removed the two BGL's, AFX_FAI1-02.bgl & AFX_2Z5.bgl & placed them in a separate folder. Now the GSX works at the gate and cargo areas. Do this at your OWN risk.
FYI, the jetways do NOT move, they are only setup for AES. ( I think they only want people to use AES.)
-
I suspect you'll see more developers going the static jetway route because of AES, too much work to animate them.
-
I suspect you'll see more developers going the static jetway route because of AES, too much work to animate them.
I would definitely agree with that statement. No worries, my money is on GSX and it is a great product.
-
I suspect you'll see more developers going the static jetway route because of AES, too much work to animate them.
Also because it's an easy way to raise fps, without worrying too much about optimizing the rest of the scenery. From slower to faster, it works like this:
- A scenery with animated standard FSX jetways (SLOWER)
- A scenery with static jetways, disconnected from the terminals, so it can be AES-able
- A scenery with static jetways embedded in the terminals, so it can't support AES (FASTER)
Of course, this is a comparison with all things being equal.
We always used animated standard FSX jetways, and our sceneries never were slower than anyone else (especially considering their usual size), and there are sceneries out there with static embedded jetways which are slower than ours so, doing FSX animated jetways on top of requiring more work to do them, will require more careful optimization for the REST of the scenery, in order to recover the performance loss due to the standard FSX jetways animation.
-
We'll need to update GSX to handle these special cases.
just asking if you have this still on your ToDo-list ?
Happy Landings
Juergen
-
there seems to be solution for the "PAFA" Problem.
I moved the "Airport reference Point" for 2Z5 to a point near the (AFCAD) tower location.
The ARP in the Aerosoft AFCAD was far east - inside the PAFA AFCAD.
This and disabling 2Z5 in the coatlAddons.ini fixed the problem for me.
maybe this helps
Happy landings
Juergen
-
That's good to know, but we'll try to fix it anyway.
-
Was this fixed?
Regards,
JC.