LSZH GSX PRO load Problem

[virtuali]

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.

[Ankh]

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...

[virtuali]

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.

[Ankh]

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...

[virtuali]

"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.

[Ankh]

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

[Ankh]

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.