FSDreamTeam forum
Products Support => GSX Support MSFS => Topic started by: Yak54 on January 21, 2025, 10:23:32 am
-
Hello,
GSX PRO gets stuck when loading FTDT-LSZH with
"Loading GSX menu, please wait" , but only if
useAirportCache = 1 is set.
GSX profile here is FSDT LSZH Zurich (Flightsim.to) in the directory ...virtuali\GSX\MSFS\ .
FSDT LSZH version is up to date.
The problem only exists in LSZH. No matter where profil.ini and bgl are with the correct afcad path, whether in the virtuali or in the community folder, the start sequence never finishes!
I have also created a log file. However, after each test a different part of the start sequence is in it, with no recognizable error ??
With useAirportCache = 0, i.e. data via simconnect, everything works.
But I need the mod useAirportCache = 1, because the Followme car works much better here.
In simconnect mode, the Followme car drives all over the area at many airports, just not on the taxiway!
So, maybe there is a solution for LSZH from FSDT that I don't know about yet in the mod useAirportCache = 1
-
Same here, no GSX on FSDT LSZH yesterday evening. How I am sick of this tool, it is always a lottery whether or not it works on my scarce simming opportunities.
-
For what its worth:
I am running FSDT LSZH latest version with a profile from Flightsim.to in the directory ...virtuali\GSX\MSFS\ ( version 3.0.1. -> file name lszh-wocetz.ini and .py ) without any problems= GSX Menu loading immediatedly when starting at LSZH.
Maybe not helpful for the persons having problems here, but thought I report that.
Andreas
-
Here is an addition to my LSZH problem:
If the value "useAirportCache = 0" is in couatl_MSFS.ini in the %APPDATA%\Virtuali folder, GSX works perfectly for me in LSZH.
But not with useAirportCache = 1 (data for GSX comes from the airport.bgl)
-
If the value "useAirportCache = 0" is in couatl_MSFS.ini in the %APPDATA%\Virtuali folder, GSX works perfectly for me in LSZH.
But not with useAirportCache = 1 (data for GSX comes from the airport.bgl)
You should not use the airport cache anymore and, since SU12, we automatically set it to 0, unless you explicitly override it, which you shouldn't do anyway, because without it, not only GSX won't work with Marketplace airports, but Jetways won't work correctly, since data about their actual position and points during the movement only come from the Navdata API since they are not found in .BGL.
There won't be any difference about how the Follow Me will work, so if you see any, it means you have a scenery conflict, most common cause is not having disabled GSX replacement jetways for an add-on airport, but in case of LSZH, not having disabled the default one.
While using the Navdata is clearly much better, it comes with more responsibility on your side because, when not using it, GSX only reads ONE .BGL at the time, so as long it found the right .BGL, it can't be confused by extra data from other conflicting airports, and it can also automatically associate an airport profile made for it.
When the Navdata is in use, GSX will get all data about that airport, including conflicts, and since we don't know from which .BGL ( or .BGLs ) this data is coming from, we can't automatically associate the "right" profile, so it's your responsibility to be sure you only have *one* GSX airport profile for that ICAO, and that one IS the correct one for that scenery, and you don't have any conflicts.
-
I cant get this resolved, all I did served nothing (giving my user full admin rights, deactivating and re-activating GSX for MSFS, using different profiles for MK simulations LSZH). I always get the message "GSX has been disabled on this airport by the user settings". If I go to another airport, GSX Pro instantly works as it should. What else can I do? LSZH is unusable for me atm due to this issue.
Might it be because I had FSDT LSZH installed once? But it is completely uninstalled, I do not find any traces of it anymore...
EDIT: just tried it in MSFS2024, MK Sim LSZH works flawlessly in this sim with GSX. So the issue is limited to MSFS2020...
-
I have some additional info from the couatl.err file it just created:
Loading airport LSZH
Using airport customization from GSX.airports.lszh_fsdt_msfs
Using airport customization from user Python lszh-mkstudios-gsx
Loading user customizations from C:\Users\AnkH\AppData\Roaming\Virtuali/GSX/MSFS\LSZH-MkStudios-GSX.ini
jetwayHeightsDict = {'jetway_b': '5.188000000000003', 'jetway_d43': '5.188000000000003', 'jetway_a': '4.580000000000004', 'jetway_e': '5.424000000000005'}
lszh_fsdt_MSFS addOn is not activated, GSX disabled for this airport
onEnteredAirport LSZH
emulateText_MSFS [GSX] GSX has been disabled on this airport by user settings 6
This makes no sense at all, why does it load the FSDT setting if I am using the MK Studios variant?
-
This makes no sense at all, why does it load the FSDT setting if I am using the MK Studios variant?
It shouldn't, unless you have installed them both, so you have a scenery conflict, and GSX is getting data from both sceneries. Are you sure you don't have the FSDT Profile also installed ?
-
Well, there is no folder anymore for FSDT LSZH. Unless the FSDT profile is hidden in another place than the ones I downloaded? And as I wrote, in MSFS2024, the MK scenery works with GSX, the issue is limited to MSFS2020. As the profiles are used for both sims, this is rather strange, no? But on discord you will find several comparable reports for various other sceneries where a FSDT rendition exists. Something is wrong here...
-
Ok, another update: I searched my whole PC for orphaned LSZH files, no surprise, I did not find any. But I found two .pye files named LSZH_FSDT and deleted those. Still the same message when I want to start GSX in MSFS2020: GSX has been disabled on this airport by user settings. Annoying. This is the couatl.err entry this time, slightly different than before:
requestFacilityData LSZH
requestFacilityData DONE LSZH
Loading airport LSZH
Using airport customization from user Python lszh-mkstudios-gsx
Loading user customizations from C:\Users\AnkH\AppData\Roaming\Virtuali/GSX/MSFS\LSZH-MkStudios-GSX.ini
jetwayHeightsDict = {'jetway_b': '5.188000000000003', 'jetway_d43': '5.188000000000003', 'jetway_a': '4.580000000000004', 'jetway_e': '5.424000000000005'}
lszh_fsdt_MSFS addOn is not activated, GSX disabled for this airport
Exception checking AirportDLC lszh_fsdt_MSFS, GSX disabled for this airport: 'NoneType' object has no attribute 'ms_marketplace_files_found'
onEnteredAirport LSZH
emulateText_MSFS [GSX] GSX has been disabled on this airport by user settings 6
emulateText_MSFS [GSX] GSX has been disabled on this airport by user settings 6
Of course I never bought LSZH from FSDT via the marketplace.
-
As I guessed, the problem WAS the .PY file that was part of the FSDT GSX profile you didn't remove so, as soon you removed it, you had a completely different error in the log (fact you saw the same message in GSX is not relevant), and that one will help us fixing it, because that one shouldn't happen.
-
Ok, great. But as a side note: those two FSDT LSZH .pye files were never modified or even created or copied in this specific folder by myself. I never touched the \\couatl\gsx\airports folder. So why should I even know that there is a folder with .pye files for every airport I visited? I thought that the moment I click on "uninstall" for FSDT LSZH, the installer will take care of getting rid of any files related to FSDT LSZH, not leaving stuff behind that potentially cripples further installations of other sceneries for the same airport.
-
But as a side note: those two FSDT LSZH .pye files were never modified or even created or copied in this specific folder by myself.
Not "two .pye files", but ONE .PY file, that is something that is part of a profile and it should be located in the %appdata%\virtuali\MSFS folder. Those are always added by you, opposite to the .INI files, which might also be created by GSX when changing anything in the airplane configuration page, but the related .PY file is never created automatically or installed by the installer.
The .PYE files are part of GSX own code, and you are not supposed to touch them and are located in the Addon Manager folder, so the error you had in the log wasn't a GSX bug, but a result of removing files that are part of the GSX installation, that's why the error.
So, we are back to the original issue, which will require having a look at the MK studio scenery, because it seems something in it seems to be so similar to the FSDT version, that might have been identified as such.
-
The .PYE files are part of GSX own code, and you are not supposed to touch them and are located in the Addon Manager folder, so the error you had in the log wasn't a GSX bug, but a result of removing files that are part of the GSX installation, that's why the error.
So, we are back to the original issue, which will require having a look at the MK studio scenery, because it seems something in it seems to be so similar to the FSDT version, that might have been identified as such.
Ok, my bad removing those .pye files. Regarding the other aspects, I mention again that the issue is limited to MSFS2020 only. When I use the very same MK Studio scenery in MSFS2024 with the very same .ini and .py files, it works without any issue. So I highly doubt that the issue is with the scenery itself, because it would then exist in both sims, no? And the text of the error log is pretty straight forward: "Using airport customization from GSX.airports.lszh_fsdt_msfs", I did not find any file with this name, so it must be something GSX intrinsic, no? Did something go wrong with the deactivation of the FSDT scenery I had installed prior switching to the MK Studio variant? Should I once re-activate and then again de-activate the FSDT LSZH scenery?
-
And now? LSZH currently unusable for me in MSFS2020...
-
I managed to try it finally, and I cannot replicate the problem: GSX works just fine with the MK studios LSZH, no issues whatsoever.
And no, I don't have "Using airport customization from GSX.airports.lszh_fsdt_msfs" in my log. Yes, that's the .PYE file you removed, but removing would cause an error, it's not required to be removed, because even if it's checked at start, if the FSDT version of the airport is not detected, it won't be used, so you shouldn't see the line in the log.
If you see it, it means you haven't removed the FSDT version, this might be either a custom GSX profile for LSZH in %APPDATA%\Virtuali\MSFS folder OR the actual package, either in Community of Official.
COULD BE you have a GSX profile supposedly for MK Studios airport, but it was made by somebody who used the FSDT GSX Profile as a starting point ? That *might* explains it, since I'm not using any profile.
-
COULD BE you have a GSX profile supposedly for MK Studios airport, but it was made by somebody who used the FSDT GSX Profile as a starting point ? That *might* explains it, since I'm not using any profile.
For the third time, the same scenery with the same .ini and .py file works like a charm in MSFS2024, only in MSFS2020 GSX tells me that it is disabled on this airport...
-
For the third time, the same scenery with the same .ini and .py file works like a charm in MSFS2024, only in MSFS2020 GSX tells me that it is disabled on this airport...
Why you think the need to explain me to me "for the 3rd time" it "works" in MSFS 2024 ? The way installed sceneries are detected in MSFS 2024 is different, because they might be streamed. Since in MSFS 2020 they are not, they are only detected if they are installed. So, again, it's only one of these:
- you still have FSDT LSZH installed
OR
- you still have a GSX profile for FSDT LSZH installed
OR
- the MK Studios scenery contains something in its data that is too similar to the FSDT version. Not the version I tried.
OR
- you might have a 3rd party GSX profile for MK studio which used the FSDT version as a startup point, leaving something the MK studio scenery doesn't have, but might still confuse GSX
As I've said, I cannot reproduce it.
-
I said it because in my eyes as customer without knowing the background it seems rather unlikely that an issue is due to a file in MSFS2020 but in MSFS2024, the very same file used by the very same software results in no issues. So thanks for your explanation, which I do not understand technically but enough to get that things are handled different in 2020 vs. 2024, even if the very same files are involved.
Then we go through from the beginning:
- I had FSDT LSZH installed and upon release of MK Studios variant, uninstalled via FSDT Installer
- MK Studios LSZH is bought via Contrail, within Contrail you can select that the scenery is used with a GSX profile (which I did). The GSX profile is from Saurer01 and maintained via flightsim.to for faster updates. I use the current one from flightsim.to.
Considering your explanations, I will try the following things:
- use MK Studios scenery without any custom GSX profile
- use MK Studios with the default GSX profile to see if something is different vs. the current one from flightsim.to
to test if the culprit is the last GSX profile from Saurer01. BTW: he contacted me over in the discord and told me that the message "GSX is disabled on this airport by user settings" can also be if you do not have admin rights on your account in Windows, which I do have. Full admin rights. He also linked a discord post/topic where they suggested to re-activate GSX after giving the full admin rights to the current user. Which I did, even if I already had full admin rights. So it seems not to be this issue...
-
"GSX is disabled on this airport by user settings" can also be if you do not have admin rights on your account in Windows, which I do have.
This would result in GSX not working everywhere, which is a completely different issue than a scenery being identified as FSDT when it's not. In any case, try without any profile installed, which is how I tested it.
-
Ok, first check with the default profile coming with MK Studios LSZH (installed via Contrail under "Configuration" in the MK Studios LSZH tab):
EDIT: wrong, I forgot to click on "check" and re-download those .pye files. I did, now GSX Pro is back to normal in LSZH, with the default profile coming with the scenery. Strange. Now I will try again the "new" one coming from the same author but downloaded from flightsim.to
-
Just as a summary, with the newest update, another "check" in FSDT Installer, the last FSDT, my issue at MK Studios LSZH vanished. Dont ask me what finally led to a success, but GSX Pro is working again on MK Studios LSZH in MSFS2020 on my end.