Mente

Thanks, that is actually very close to the distinction I was trying to make. I probably should have worded it more precisely: I am not suggesting that MSFS has no internal diagnostics at all. The question is why so little of that diagnostic capability is exposed in a useful way to the user or third-party developer when something goes wrong. Safe Mode, package reordering and manually removing scenery can help isolate a problem, but they still leave the user doing most of the detective work. If the platform could at least identify which packages, scenery layers, mesh or other components were involved when an issue occurred, that would already be a major improvement. So for me the core question remains less about “more logging” and more about turning existing internal information into actionable diagnostics.

I’ve been following the SU7 beta discussion here, and what strikes me is how difficult it still is for users to determine what is actually causing a problem. Performance issue, scenery, aircraft, add-on, streaming, memory, simulator regression — from the user side a lot of it still ends up as trial and error. That is also why I raised this question earlier about the diagnostic foundation of MSFS 2024. Not because every issue needs more logging, but because better internal diagnostics could help separate symptoms from actual causes and make feedback much more useful for both users and developers. For anyone interested, this is the discussion I started earlier: https://forums.flightsimulator.com/t/msfs2024-sim-update-7-your-dream-feature/751235/922

I kept the 2020 and 2024 MSFS separate, also because I couldn't manage that.

I'm currently using AddonsLinker specifically for Msfs20 and Msfs24. I'd like to configure it so that Msfs20 uses the same Addons linked to Msfs24. I think that would be possible with the layout I created. Airports, Africa, Algeria, Airports, Ms20, Ms24 Airportslights, Ms20, Ms24 Algm Mods, Ms20, Ms24 Asset, Ms20, Ms24 Buschtrips, Ms20, Ms24 Within the entire file, I could then choose between Msfs20 and Msfs24, and possibly the files compatible with Msfs20 or Msfs24. What would be the best way to do that?

Ik gebruik momenteel AddonsLinker specifiek voor Msfs20 en Msfs24.Ik wil het graag zo configureren dat Msfs20 dezelfde Addons gebruikt die zijn gekoppeld aan Msfs24.Ik denk dat dat mogelijk zou zijn met de lay-out die ik heb gemaakt. Luchthavens, Afrika, Algerije, Luchthavens, Ms20, Ms24 Airportslights, Ms20, Ms24 Algm Mods, Ms20, Ms24 Asset, Ms20, Ms24 Buschtrips, Ms20, Ms24 Binnen het hele bestand kon ik dan kiezen tussen Msfs20 en Msfs24, en mogelijk de bestanden die compatibel zijn met Msfs20 of Msfs24.Wat zou de beste manier zijn om dat te doen?

Ik ervaar hetzelfde, en controleer het elke keer eerst voordat ik ga vliegen. Maar het zou niet mogen gebeuren.