Nice - those release notes are a really welcome addition. Noticed this version also tweaked the 737 refueller truck choice, so off to check that out.
Forgot to mention that in my post. I was flying the 738. Make sure to update. Youāll get the new vehicles.
Iām glad Umberto is getting the bugs fixed and adding better fueling vehicles for the 737. I do hope he gets profiles sorted out for the -800 BCF and BSDF models though. By default they are still not properly configured. I didnāt spend any time seeing if heās fixed the āsaved aircraft customizations donāt workā bug though.
thank you for your detailed answer, it was indeed the update which set back the exclusion list.
Have any UK users managed to use the online update yet or are we still having to download the installer from the forum?
Cheers
I got the updates that made it work correctly with the PMDG 737-800. But I am not sure after that. I just tend to update it every couple of days. I dont think the Updater actually tells you if there is an update which is crazy.
Totally agree. If it seems to be downloading the same files each time (which it does for me) then itās not actually doing anything and youāll need to get the offline installer from the forum. This issue with these cloudflare nodes should be long since sorted.
Itās a ok to good product, but this update faff is an absolute mess.
Does anyone know if I have to manually set the correct afcad file location into downloaded airport.ini files so they match my local file paths? Or is it not necessery?
It depends - if the profile youāre downloading is for a 3rd party airport, then generally yes. If itās a profile for a stock MSFS airport, then no.
Thank you for answering. Yes, mostly 3rd party addons. What I saw when checking the ini files for some stock airports was, that there might be an afcad file path to the steam version path that is different. Also I do not use the default path for a store version. My content folders are on an extra ssd. So these file paths do not match either. Guess I have to manually edit all ini files I download and repeat when they are updated.
Thanks to all of the gsx profiles on flightsim.to (which require updating path in .ini file so not just drop-and-drop), Iām finding GSX works very well. Especially for those profiles that have been well done (e.g. EGAA from official dev) they just work.
I adjusted passenger density to āinsaneā to speed boarding process but sometimes skip that. To me this is worth it just for pushback (with regional accents), gate arrival and all of branded ground vehicles. Havenāt tried follow-me car yet. The update process seems unusually lengthy but the latest version from yesterday seems stable.
You are wrong, it is in the manual and I asked in the FSDT forums: you do NOT have to adjust the path in the .ini file, as long as the .bgl (the AFCAD) has exactly the same name, what should be the case for 3rd party airports (unless you do not use the one coming with the product).
Everytime I try this I get a new issue.
āLoading GSX menu, please waitā on a constant loop at a standard msfs airport.
No, YOU are incorrect. Anyone with a different file path for their Community folder, or who has the sim installed on a different drive from that of the creator of that specific folder, will absolutely have to edit the .ini file.
Further, if you have Marketplace airports, not one purchased directly from the developer, you have an additional step: you need to determine what generic .bgl file is being loaded by GSX (since it cannot yet access encrypted Marketplace airport data) and use that path in your .ini file.
Please donāt try to ācorrectā people about this: Iāve already had to do this for KBOS, LGAV, KBUR and several others.
LL, could you provide a quick āstepsā list on how you prepared KBUR, for example?
Thanks!
Sure. There may be a somewhat faster/more efficient way but hereās what I did:
- Loaded up MSFS and spawned into any airport. Doesnāt matter, just need access to GSX for now.
- Called up GSX and entered the Settings, then Troubleshooting page.
- Enabled GSX logging.
- Exited the first flight, then spawned into KBUR.
- Called up GSX, navigated to the Troubleshooting page again, then opened the folder location by clicking the button on that page.
- Open the log file in Notepad or any text editor. Find the entry where it shows the AFCAD file being loaded by GSX.
- For a Marketplace airport, which will not be in \COMMUNITY, it will be some generic airport .bgl file. Copy that whole path back to the drive letter.
- Find the .ini file you downloaded from flightsim.to and open it as well.
- Paste the AFCAD file path you just copied from the GSX log file into the .ini file.
- Save that modified .ini file to %APPDATA%\virtuali\GSX\MSFS (double-check that file path - Iām going from memory here!). Pay close attention to the formatting of the line youāre changing and be sure the backslashes, question mark, etc. are still there after you paste in the new path.
- Quit the sim and restart
This has worked for every Marketplace airport Iāve got where someone has created a GSX profile to share, with the exception of LGSK (I hope I have that ICAO right - Skiatthos, Greece). That one just isnāt working for me for some reason but Iām not sure exactly why. Iāve resorted to just creating my own there, which is fine. Thereās only like 8 - 9 stands, and a couple of them in the Marketplace version have static aircraft you canāt remove, which makes it even easier.
So, whatās the general opinion now, is it already worth the money?
It is when it works.
There are a few airports (I think KSFO, LIMC, EDDM plus any fsdt airports) which you can use in ātrialā mode (just enter random numbers for serial when installing), so you can give it a try before committing. The passenger loading can be hit-or-miss, but for me it is worth it for all the other features as I probably wonāt use the passenger load/unload often.
Todayās update seems pretty flakey. Getting frozen baggage handlers. Itās good that it keeps getting updated, but itās a bit of a lottery on what happens . Iāll try again tomorrow.
Question: am I right in thinking you need to have rear stairs at the aircraft to be able to see any passengers boarding in the jetway? I donāt really understand that logic, so wondered if I understood it wrong.