Products Support > GSX Support FSX/P3D
GSX Not Working with Flightbeam KDEN after latest update P3d V4 & V5
Ray Proudfoot:
I have the following Flightbeam airports... KIAD, KMSP, KPHX, KSFO, LFBO, NZAA and NZWN.
KIAD and KSFO have the same problem as KDEN - only one parking position available. The rest are fine.
Looking at the AFCAD for KIAD and KSFO they're not clean by any means but they did not have this one parking position issue on earlier builds. Not much more I can add really. Good luck trying to find the problem.
joergalv:
--- Quote from: virtuali on September 07, 2022, 11:40:30 am ---I already replied in several threads: there's still a problem with some .INI files which I can replicate, but I still can't understand why it's happening.
--- End quote ---
Looks like it has something to do with the missing "parkingsystem = xx" entries in the ini file.
Flightbeam KDEN:
- In the default ini none of the entries has the "parkingsystem = xx" entries.
- When loading KDEN without having a custom ini in '%APPDATA\virtuali", Gate 16 is the only available parking.
- I then customized that parking position (actually not changing anything, but activating/deacticvating a checkbox, to 'activate' the apply button, and let GSX save the custom ini file in in '%APPDATA\virtuali". => The custom ini file contains now the "parkingsystem = " entry for gate 16.
- Quit P3D, and restart P3D at KDEN, now with the custom ini file available.
- Now, not only Gate 16 is available, but also gate 18.
I assume that adding the "parkingsystem = " entry to gate 18 as well, will make another gate available.
It's like with FSDT LSGG => adding the 'parkingsystem = xx' entry, resolves the 'parking is isolated' issue.
virtuali:
We found the problem with .INI files, and it's fixed with the current Live Update.
Ray Proudfoot:
--- Quote from: virtuali on September 07, 2022, 09:57:02 pm ---We found the problem with .INI files, and it's fixed with the current Live Update.
--- End quote ---
Well done. What was it please?
virtuali:
--- Quote from: Ray Proudfoot on September 07, 2022, 10:02:35 pm ---Well done. What was it please?
--- End quote ---
It was related to parking systems.
We realized having parking systems in the .INI as numbers wasn't a very good idea, because it restricted the ability to add new types in an ordered manner, so we switched to storing their names instead.
Obviously, we thought about not breaking existing profiles so, if an old .INI file with numbers is found, it will be translated to the new names system automatically so, in this case, the translation routine didn't work if there were *no* parking systems in the .INI file but, since we try to manage all possible errors, the problem was hidden by the error handling, so you didn't see any errors, but it resulted in the parking being ignored.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version