Products Support > GSX Support FSX/P3D
GSX with Flightbeam KSFO no longer works
fnav77:
--- Quote from: Papacoach on August 25, 2022, 01:47:16 pm ---I noticed this at KSFO and a few others yesterday, which was the first time I've loaded it since the update. I opened the ini file in the user/appdata/roaming location and noticed that the afcad location listing was not correct. Changed it to reflect the entire afcad path and reset couatl and all gates came back.
I spent another few hours making sure all ini files had correct afcad listings. After that all seemed fine.
--- End quote ---
Hi,
Could you please elaborate on this? I have inserted the location of the .bgl file after the line "afcad_path = C:\etc....) in the GSX .ini file for KSFO, restarted the whole sim, GSX is still recognising only one gate. It does not work for me.
captaingreif:
--- Quote from: fnav77 on August 25, 2022, 11:34:49 am ---
--- Quote from: virtuali on August 24, 2022, 07:00:26 pm ---
You are assuming too many things, the only thing we need to fix things quickly, is for the traffic on the forum to go down.
--- End quote ---
If the traffic is high on this forum it is because you messed up big time...no apologies...nothing! And now you want people to stop people reporting issues? Are you serious?
Liam is absolutely right...The number one priority is to fix what you broke! And quickly!
--- End quote ---
Exhibit A of the rudeness and arrogance of this developer. Absolutely deplorable behavior towards customers.
Papacoach:
--- Quote from: fnav77 on August 25, 2022, 06:13:52 pm ---Hi,
Could you please elaborate on this? I have inserted the location of the .bgl file after the line "afcad_path = C:\etc....) in the GSX .ini file for KSFO, restarted the whole sim, GSX is still recognising only one gate. It does not work for me.
--- End quote ---
Sorry to hear that.
I deleted the ini file inside the flightbeam ksfo scenery folder so there would only be one option, which may be unnecessary. But did it anyway. Like you, I then made sure the ini in the user/appdata/roaming/... listed the [general] afcad_path entry pointing to the flightbeam scenery folder and correctly named afcad bgl file. I then used the restart couatl/rebuild cache option in the addon menu. That's it, I did nothing else. Then it showed all ksfo gates. NOTE: all of the above was actually with the sim running fyi.
We haven't needed the whole afcad path in the past. However, GSX seems to generate it now when you start editing a new airport. So I edited all my ini files with the entire path location and made sure that there were no ini files in the scenery folders for all my payware airports. fwiw.
Hope you can get it to work!
fnav77:
Papacoach, thank you for your reply. 8)
Yeah, the problem seemed to be the kxxx-flightbeam config files in the Flightbeam P3D scenery folder. The kxxx-flightbeam config file has all the gates information for GSX. Once you remove the file from the Flightbeam folder, then GSX registers all the gates and you can edit, etc... at will. Just to explain, kxxx=k+3 letter airport code, ie ksfo, kden, kphx, kiad, etc....
Same solution for KIAD and KDEN.
KPHX does not have that kxxx-flightbeam file, so no problem there. The only thing is that GSX recognises only the P3D v4 .bgl airport file but GSX seems to work.
Why we have to do that now I don't know. There was no such issue before. ::)
jalbino59:
--- Quote from: Papacoach on August 25, 2022, 01:47:16 pm ---I noticed this at KSFO and a few others yesterday, which was the first time I've loaded it since the update. I opened the ini file in the user/appdata/roaming location and noticed that the afcad location listing was not correct. Changed it to reflect the entire afcad path and reset couatl and all gates came back.
I spent another few hours making sure all ini files had correct afcad listings. After that all seemed fine.
--- End quote ---
That took care of this issue for me. Thanks Papacoach
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version