| GSX Profile for KBOI Boise Air Terminal by Verticalsim
This profile includes all gates at the terminal and cargo stands.
The profile aims to be as close as possible to real life and every included parking position features:
- Accurate ground handling and catering companies (for most gates)
- Accurate stop positions (based on the PMDG 737-800 and CRJ-550, might be inaccurate for other aircraft)
- Custom vehicle placements
- Custom pushbacks
- Passengers walking inside the terminal
- Walk-in paths for gates that have them
Installation:
Extract the .zip file and move the .ini file to %APPDATA%\Virtuali\GSX\MSFS
Note:
Recommended to be used with the latest GSX update and the "Use SU10 Navdata API" option enabled in the FSDT Installer
If you are not then you will have to edit the .ini and add your afcad-path to the profile
NavyLandSub
I know this one says "Recommended to be used with the latest GSX update and the "Use SU10 Navdata API" option enabled in the FSDT Installer" Does this apply to all your older GSX Pro Profiles as well?
BTW, I love your work and it seems like every time I get on Flightsim.to, you have a new airport I bought, or you have an update to one. Keep up the good work!
reverentan 27 day(s) ago
I have actually stopped adding that recommendation to my profiles because while the API is great for adding compatibility with marketplace sceneries it can cause a few issues with boarding/deboarding using jetways. The easiest way to check if a profile needs the API or not is opening it up with a text editor and looking for an “afcad-path” at the top. If the “afcad-path” is empty or doesn’t exist you will need the API enabled unless you add the “afcad-path” yourself. If it has an “afcad-path” it will work regardless if you are using the API or not. Hopefully this clears things up a bit! Thank you so much for the kind words 😊
NavyLandSub 17 day(s) ago
Perfect, that does clear everything up. So GSX takes the AFCAD Path as priority over API data.