AstralNought

Cycle the light switches from their current position all the way to the other end, whichever ones have an on/off switch. If something is off, cycle it all the way to on and then back off. There isn't a particular one that causes the bug but cycling them (like the emergency lights, dome, etc) will fix it. It's a bug from not being compatible with FS2024.

Until it is officially made compatible with 2024, yes, anytime there is an update to the aircraft or the navdata, the step needs to be repeated.

After you update the navdata from Navigraph or the product via TFDi Manager, run the 'MSFS Layout Generator' on the layout.json file of the MD11. That will fix the issue. More here.

No way! Does that really work?! And to think I'd kept a detailed note of the arduous install process.

Thanks for catching that. I can't edit my response anymore so hopefully others read the full thread.

Steps listed on page 1.

I assume you're referring to updating the product, not a fresh install, as for a fresh install in 2024 (without 2020), you definitely need to create the folders to fool the installer.

I have 2024 from Steam so these are the steps involved: 1. Browse to C:\Users\<YourWindowsUserName>\AppData\Local\Packages\ 2. Create a folder with the name 'Microsoft.FlightSimulator_8wekyb3d8bbwe' and within it, create another folder called 'LocalCache'. 3. Within Local Cache, create a txt file and add the following content to it: InstalledPackagesPath "C:\Users\<YourWindowsUserName>\AppData\Roaming\Microsoft Flight Simulator 2024\Packages" Note(1): The text file should be named 'UserCfg.opt', not 'UserCfg.opt.txt'. 4. Run the TFDi installer. It will detect MSFS and will install the product in your 2024 Community folder. Once it's done, you can now delete the entire 'Microsoft.FlightSimulator_8wekyb3d8bbwe' folder and any future updates will automatically detect your installation without the need to repeat these steps. 5. Update the navdata from Navigraph. Once done, grab MSFSLayoutGenerator (LINK) executable. Copy it over to your TFDi installation directory, and drag & drop the layout.json over the MSFSLayoutGenerator executable and you're ready to fly. You'll see a blank terminal window pop up for a second or two which is normal. Once it closes, your layout.json should have its date/time stamp change to whenever you do this step which means it was done successfully. Note(2): I don't know if the new version fixes it, but after every navdata update, you need to re-do step 5, or else you may find incomplete SIDs/STARs in your FMC.

I just did. No 2020 installed.

Works fine for me in 2024. Need to use the scroll wheel on them, not the click switches on the mouse.

Not necessary. I have it installed & running in 2024 without 2020 installed.

It's something I haven't understood either, likely because I don't have the necessary technical knowledge but: Isn't it a port-over of the XP variant which has all the systems? Why haven't they been able to duplicate it for MSFS? Is the development environment that different between the two that it has to be done from scratch?

Thanks for this! I've disabled everything I don't intend on using including default aircraft, challenges, discovery flights, etc.

Great update to an already excellent aircraft. Reinstalling liveries isn’t necessary—only the configuration files need to be removed before uninstalling and added back after installing v1.0.

It doesn’t seem very appealing from what I’ve seen during my brief look at the videos. I wish they had invested in something like the King’s School lessons from the FS2002/4 days. With the growing MSFS customer base leading to more traffic online, it would have been incredibly helpful, especially for those of us who enjoy network flying and expect a certain level of knowledge and professionalism. Nowadays, it feels like driving in traffic—just assume everyone else got their license from a cereal box, and you’ll be better prepared.