FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: Mischka43 on February 21, 2016, 08:39:23 pm
-
Hi there,
when starting preflight prep or after landing in EDDB from Aerosoft GSX offers only 4 Parking opportunities (taken from EDDB2 Helipad, this is a murky thing by Aerosoft, somewhat resembling the real chaos building EDDB ;-)) .... instead of EDDBs large number of Gates. It seems a file from Justflight Traffic 360 ist involved: AF2_JFDB.bgl ... but when deactivating this one, GSX does not work on EDDB at all.
Please help!
By the way: Aerosoft service was answering "we do not test our products working with GSX... AES is working fine).... what arrogant sxxxxxs....
-
when starting preflight prep or after landing in EDDB from Aerosoft GSX offers only 4 Parking opportunities (taken from EDDB2 Helipad, this is a murky thing by Aerosoft, somewhat resembling the real chaos building EDDB ;-))
The issue with helipads using fake ICAO code has been discussed here:
http://www.fsdreamteam.com/forum/index.php/topic,9447.msg96082.html#msg96082
You can use the airport_visibility_xxxx = yyy parameter in the GSX .INI file to exclude such dummy ICAO codes and force GSX to use the correct one. A more detailed explanation of this feature is included in the current GSX manual, Page 21.
instead of EDDBs large number of Gates. It seems a file from Justflight Traffic 360 ist involved: AF2_JFDB.bgl ... but when deactivating this one, GSX does not work on EDDB at all.
That seems to be a separate issue. AFTER you solve the fake ICAO as explained above, try to refresh the scenery cache removing the following folders, when the sim is NOT running:
C:\ProgramData\Microsoft\FSX\SceneryIndexes
C:\ProgramData\Virtuali\Couatl
By the way: Aerosoft service was answering "we do not test our products working with GSX... AES is working fine).... what arrogant sxxxxxs....
Well, of course AES "works", it doesn't read the AFCAD, so it's not affected by issues caused by them, but it forces you to pay for each airport!
-
Thanks, a lot, that worked well!
1st: airport_visibility_EDDB2 = 0
2nd: deactivating AF2_JFDB.bgl in Traffic 360 by renaming
3rd: removing folders C:\ProgramData\Microsoft\FSX\SceneryIndexes and C:\ProgramData\Virtuali\Couatl
Without deactivating the traffic 360 file it did not work....
Thanks that is service!
Michael