KMDW Chicago Midway MSFS

[DD Stanislaw]

Hi.
Do you get any particular errors?

[richbonneau]

I just purchased KMDW from the inibuilds store and confirmed that it is activated with MSFS addons linker. The scenery is not showing up in the sim. When I enter KMDW in the airport dialog I do not see the 'star' indicating that there is an updated scenery installed and only the default scenery is loaded.

I disabled all other addons with the addons linker but the problem persists.

Any ideas?

[Martin_Starski]

Have you already asked the developer of this addon linker? I think it should be the first step because we do not use it.

[DD Stanislaw]

Inibuilds create their own installers, please ask their support directly.

[Dadriel]

I can confirm the issue, it was the same for me after installing the most recent version of Midway via the Orbx installer into MSFS2024. The airport ground was loading correctly, but there were no buildings shown.

In the end, the layout.json that was delivered with the update is broken. After I recreated the file with the Layout Generator tool, the scenery is now working correctly in MSFS2024 and all buildings show up as expected. I have not tested the 2020 install, but I would guess it's probably the same issue there, if no buildings are showing up.

[Martin_Starski]

In our installers, it seems to be solved. Have you reported this issue to ORBX? They create their own installer, which probably needs to be updated.

[John Burgess]

This issue (no buildings appearing when selecting the nostatic option in FS2024) was reported on the ORBX forums and I've posted an edited layout.json file in the following thread which hopefully solves the problem.

https://forum.orbxdirect.com/topic/2234 ... messed-up/

As far as I know there are no problems in FS2020

All the best,

John

[browns5011]

Hello!

I am experiencing a problem installing the latest updates (from Aerosoft and SimMarket) for KMDW, EPMO, EPWA, EPWR, EETN and other DD airports for MSFS 2020 & 2024. When attempting to install any of the airports to 2020 or 2024 (as administrator), I get the error: "Simulator path could not be located. Please check your configuration and try again".

My 2020 Community Folder has been the same for almost 5 years and I have had no problem installing your airports or any others in that past. I have installed 2024 on a different drive. I am only having this problem with DD airports. Older DD airports (e.g. KBFI V1.1) install fine. Can I ask for your advice or help?

Thank you for any insight!!

Best Regards,
Mike

P.S. I looked for a "general" support forum, but did not see one I could post to. Forgive me if I overlooked it!

[Martin_Starski]

Hi, it has to be something with the incorrect path in the file, from which our installer reads the path. Can you check what is mentioned in this file:

MS Store:
%localappdata%Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\UserCfg.opt
Steam:
%appdata%\Microsoft Flight Simulator 2024\UserCfg.opt

[browns5011]

Hello,

Thank you for your reply!!

Roger all! That was my first thought as well.

I have always had a customer community folder for MSFS 2020 (E:\MSFS 2020\Community). I have also set one for MSFS 2024 (F:\MSFS 2024\Community).

I checked and both are correct in the UserCfg.opt files Both 2020 and 2024 are seeing all other installed scenery fine.

Right now I am still flying 2020 as my primary.

All older versions of DD airports (2020) still find my Community folder and install just fine. It is only the latest updates just released with the 2020 and 2024 install options that I get the error. With that said, I was trying to figure out what might be different to cause the issue? Do the new versions only install to a default folder now? Just a guess on my part.

My sincere thanks! I've been "flying" MSFS for 40+ years and own most all DD airports for 2020; thoroughly enjoy them!!

[Martin_Starski]

Can you share your UserCfg.opt files here as a zip file, please?

[browns5011]

Certainly!

I just added the version to each name for clarity.

[Martin_Starski]

As far as I understand, you are sure that “InstalledPackagesPath” entry points to the path where your Community folder is installed.
I also assume that your UserCfg.opt files have all "Allow" permissions in their properties -> security tab.

Currently, it's hard to say what is the reason - it seems to be the incidental case caused by your specific setup.

Can you maybe try to:

1. Remove the patch from UserCfg.opt file, which means that it looks like this: InstalledPackagesPath ""
2. Run our installer, which should ask for the path to the main MSFS folder (incl. Community and Official)
3. Complete the installation
4. Revert the original path to the UserCfg.opt file

[browns5011]

Thank you again for your time and help!

I have resolved the problem. It appears another developer's path setting installer may have corrupted my UserCfg.opt files in MSFS 2020 and MSFS 2024.

Thanks to your suggestions, I was able to make corrections and all airports installed properly.

Best Regards,
Mike

[Martin_Starski]

I was able to make corrections and all airports installed properly.

Great that it's working. Please just share with everyone here what corrections have to be done.