Products Support > GSX Support FSX/P3D

GSX with Flightbeam KSFO no longer works

<< < (6/6)

Alphatango2:
Well, I don't know what happened but I checked my scenery library and all my FSDT were not installed. (Area in the p3d scenery library) All were active but not installed. Manually reinstalled the area into the p3d scenery library and now everything works as it should including all the gates everywhere.... 

kmanning:

--- Quote from: Papacoach on August 25, 2022, 01:47:16 pm ---I opened the ini file in the user/appdata/roaming location and noticed that the afcad location listing was not correct.

--- End quote ---

Can you elaborate more? You're not providing enough details about where the .ini file is. There is no .ini file in the Roman folder. Will you provide each and every folder that takes us to the exact folder that the .ini file is in, and provide the exact file name.

Ken.

kmanning:

--- Quote from: MD-82 on August 31, 2022, 05:41:43 pm ---- Rename to .off the FlightBeam config file.
- Rename to .off any pre-update ini file you may have had in the past.
- Restart GSX with a rebuild

--- End quote ---

What do you mean by "Rename to .off?" I don't understand what you mean by the term "off" and why it has to be renamed.


--- Quote from: MD-82 on August 31, 2022, 05:41:43 pm ---It is not easy to get something so complex going in MSFS
--- End quote ---

By the way, all of the issues discussed in these posts are support for the FSX and P3D, not MSFS 2020.

Ken.

MD-82:

--- Quote from: kmanning on September 01, 2022, 10:55:06 am ---
--- Quote from: MD-82 on August 31, 2022, 05:41:43 pm ---- Rename to .off the FlightBeam config file.
- Rename to .off any pre-update ini file you may have had in the past.
- Restart GSX with a rebuild

--- End quote ---

By the way, all of the issues discussed in these posts are support for the FSX and P3D, not MSFS 2020.

Ken.

--- End quote ---

Hey Ken,

it means that all GSX config files have an extension "airport icao code-random numbers and letters.ini". To make GSX not see the airport you either have to change the airport name or change the extension so it is not an *.ini file. In flight simming the general procedure is to rename the extension to *.off.

For example:

"ksfo-sigju.ini" becomes "ksfo-sigju.off". This way you still have your original file for when this issue is fixed, but GSX no longer knows what the file is.

Other ways of achieving the same result:

- Rename the airport part, e.g. "k_fo-sigju.ini". however I don't like it because GSX will still see the file and might wonder what airport "k_fo" is.
- Keep the file name as it is, but remove it from the folder. However now you have files laying elsewhere that in the future you have no idea what they are or where you have placed them.

kmanning:

--- Quote from: MD-82 on September 02, 2022, 10:26:31 am ---
--- Quote from: kmanning on September 01, 2022, 10:55:06 am ---
--- Quote from: MD-82 on August 31, 2022, 05:41:43 pm ---- Rename to .off the FlightBeam config file.
- Rename to .off any pre-update ini file you may have had in the past.
- Restart GSX with a rebuild

--- End quote ---

By the way, all of the issues discussed in these posts are support for the FSX and P3D, not MSFS 2020.

Ken.

--- End quote ---

Hey Ken,

it means that all GSX config files have an extension "airport icao code-random numbers and letters.ini". To make GSX not see the airport you either have to change the airport name or change the extension so it is not an *.ini file. In flight simming the general procedure is to rename the extension to *.off.

For example:

"ksfo-sigju.ini" becomes "ksfo-sigju.off". This way you still have your original file for when this issue is fixed, but GSX no longer knows what the file is.

Other ways of achieving the same result:

- Rename the airport part, e.g. "k_fo-sigju.ini". however I don't like it because GSX will still see the file and might wonder what airport "k_fo" is.
- Keep the file name as it is, but remove it from the folder. However now you have files laying elsewhere that in the future you have no idea what they are or where you have placed them.

--- End quote ---



Okay, I see what you mean now. I would be like renaming it to .bak, or something like that. I just never heard of .off being used as an extension.


Ken.

Navigation

[0] Message Index

[*] Previous page

Go to full version