FSDreamTeam forum
Products Support => GSX Support FSX/P3D => Topic started by: nathantw on August 23, 2022, 06:43:15 pm
-
I ran FSDT Live update and now Flightbeam KSFO GSX doesn't work. It's as though it's back to the trial version. Only 1 GSX jetway is available. All the other airports appear to work though.
(update) I restored the Addon Manager folder from backup and all is working now. However, that update really did a doozy on KSFO.
-
all of my airports work fine except the flightbeam ones...
-
Same here....Flightbeam's KDEN, KIAD and KSFO do not work, GSX only recognises 1 gate at those airports and so does the GSX Customization tool ("customize Airport Positions").
KPHX seems to be working with GSX recognising all the gates.
These sceneries used to work fine before.....
-
Same here....Flightbeam's KDEN, KIAD and KSFO do not work, GSX only recognises 1 gate at those airports and so does the GSX Customization tool ("customize Airport Positions").
KPHX seems to be working with GSX recognising all the gates.
These sceneries used to work fine before.....
Yup +1
-
Same here....Flightbeam's KDEN, KIAD and KSFO do not work, GSX only recognises 1 gate at those airports and so does the GSX Customization tool ("customize Airport Positions").
KPHX seems to be working with GSX recognising all the gates.
These sceneries used to work fine before.....
It’s hit and miss which airports work with GSX currently.
Did some tests after the most recent update that has fixed the vanishing jetways.
Uk2000 egcc, GSX recognises all gates, but there’s no jetway animations.
Uk2000 egll, only 1 gate recognised, but when at it “gate is isolated, no services”
Uk2000 egkk, all seems to work ok.
T2G othh, all seems to work.
FlyTampa omdb, no jetway animations.
GSX is massively bust right now and I think it’s going to be a while before it returns to pre Thursdays destruction.
-
GSX is massively bust right now and I think it’s going to be a while before it returns to pre Thursdays destruction.
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.
-
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.
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!
-
People on the forum want admins to tell us whats happening, but that shows the fixes down.
Maybe let FSDT get on with fixing GSX and allowing them to read the comments when there are several feeds that are the same... .
-
Damned if I do, damned if I don't. You want "fixes quickly" but at the same time you want to be constantly assured fixes are coming.
-
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.
-
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.
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.
-
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.
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!
Exhibit A of the rudeness and arrogance of this developer. Absolutely deplorable behavior towards customers.
-
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.
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!
-
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. ::)
-
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.
That took care of this issue for me. Thanks Papacoach
-
+1
I can confirm this method worked out great for me as well! Thank you :)
-
Yes this method is working, all gates are back. BUT, i cant request any services by GSX. its like freezing again. the enable/disable in the dropdown from addon menu works but still i cant request any services. nothing happen! Refer the attachment
-
What is the format you guys are using? I think mine is
A:\P3D\Flightbeam\Flightbeam - KSFOHD\scenery\KSFOHD.bgl
but I restart and rebuild the couatl cache and still no options for gates at KSFO, KDEN, or KIAD. prior to this I did delete the .ini files in the flightbeam folders, which did not work.
P3D 5.3 latest hotfix.
-
Thanks Papacoach, I simply rem'd out that line in the config and away I went. You da man
Regards, Verne
-
Damned if I do, damned if I don't. You want "fixes quickly" but at the same time you want to be constantly assured fixes are coming.
The reason being Umberto is because YOU have not taken any responsibility whatsoever for this disastrous 'Update". As you typically do, you deflect and blame us as users or, some third party for this cockup... Honest communication is a key in any successful business.
-
GSX is massively bust right now and I think it’s going to be a while before it returns to pre Thursdays destruction.
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.
On the positive way, do you have an ETA on the problem fix, please?
-
Well guys, I got Flightbeam KSFO to work but not so fortunate with Flightbeam KDEN. Any ideas?
Cheers,
Verne Cotton
-
Can you share what you did to get it working? I did the same but my Ctrl+Shift+F12 and Addon Menu options aren't even working. I can't get anything to work.
-
For me, the only way to get it to work is to let GSX use its internal database. And start a new edit if you want. The pre update ini file is useless with or without the correct path. So;
- 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
You get only the internal database. Any edits or custom pushbacks you may have had before are lost for the moment. I have not tried text editing the information back in but kept it like this for now.
Also, please let's refrain from arrogance and demands :-( It is not easy to get something so complex going in MSFS and please everyone. So take a step back and look at ourselves. It's not the end of the world ...
-
Well I don't know why it worked but I just deleted the ini file in the Flightbeam KDEN and all is okay. As for the Flightbeam KSFO, I just remmed out the afcad path in the ini file and cured KSFO. Now if I could only fix the FSDT KMEM that I just bought the day before this mess, I would be in happy land. Right now all the KMEM gates throw an "Isolated parking" error.
Cheers,
Verne Cotton
-
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....
-
I opened the ini file in the user/appdata/roaming location and noticed that the afcad location listing was not correct.
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.
-
- 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
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.
It is not easy to get something so complex going in MSFS
By the way, all of the issues discussed in these posts are support for the FSX and P3D, not MSFS 2020.
Ken.
-
- 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
By the way, all of the issues discussed in these posts are support for the FSX and P3D, not MSFS 2020.
Ken.
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.
-
- 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
By the way, all of the issues discussed in these posts are support for the FSX and P3D, not MSFS 2020.
Ken.
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.
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.