ksp100

So, I ended up uninstalling iniManager, deleting the two iniManager folders in the user appdata/Local and appdata/Roaming folders and then reinstalling iniManager, logging back in and ensuring the settings pointed to the right Community folder. That allowed me to reinstall the A350. Implication is something went wrong with the 'updating' of iniManager at some point. Kevin

Hi, Same here on MS2024. Even tried uninstalling and then ask it to install but it just states ' Queued' and does nothing. Tried the 'alternate downloader' in the Settings options but that makes not difference. I assume some config file for iniManager has been corrupted somehow. Suggestions please? Kevin

Ditto. Working a treat! Much appreciated.

Eddie, Thanks for the update. Good to hear that you understand the problem. If you need any help testing a fix, just reach out. Kevin

I have the same problem and only when I fly into Heathrow. Using the MS Store version of MSFS2024. Disabled the asobo heathrow and cleared the sceneryindexes folder and still the same problem. Uninstalled and reinstalled the scenery but no change. Unlikely to be a vram issue as I have 7900xtx card. Also, I am not aware of the same problem at any other airport. I once lost T5a but most of the time it is T3 buildings. It also mucks up the altitude of some of the banks around the road cuttings to the south of T5b - they end up looking like floating green platforms (looks like something from the kids Minecraft!). I thought it may be something to do with "Dynamic Settings" but disabling that doesn't make any difference (TLOD at 120 and OLOD at 120). I've also turned of all the 'settings' apart from T5A and T5B/C High Detail. I don't recall it doing it in earlier releases and can't really remember when I first noticed it, so my question is it related to SU2 or something related to the v1.0.2 update which the log says changed LODs and elevation issues - or a combination of the two?