AndyM

You could try deleting the contents of the SceneryIndexes folder

Do you have Bing Data and Photogrammetry turned on in the MSFS options?

Seems to be working okay for me now

Same issue here

I don't have this scenery, so can't test it myself. In general, if I have had terrain problems, I have found that having Bing Data and Photogrammetry turned off can cause these issues, and also clearing out Rolling Cache and the SceneryIndexes can sometimes help.

Do you have Bing Data and Photogrammetry turned on in the MSFS Settings?

Okay, I got mine directly from IniBuilds, but is showing the same 1.0.3 version. Good luck with the troubleshooting.

I'm seeing some differences to my scenery. May I suggest that firstly check that you have the latest version. Then remove ALL other addons from your Community folder, and do a fresh install of KDTW so that just KDTW is the only addon in your Community folder and check the issue. If that doesn't work, maybe delete your Scenery Indexes and Rolling Cache to see if that works.

I'm not seeing that, have you uninstalled Asobo's KJFK?

If I were you, I'd remove EVERYTHING from your Community Folder, start MSFS, clear out the Rolling Cache and close MSFS. Do a fresh install of the airport (no other addons), and start MSFS to see if you still have the issue. If you don't, start installing other addons to see if any of those are conflicting with the scenery.

It's in the General Options - Data - Photogrammetry within MSFS

Have you tried removing everything from your Community folder, and doing a fresh install of the scenery? Also, check that Bing Data is turned on.

Standard thing (other that what is already been suggested) is to remove EVERYTHING from the Community Folder other than the PHNL scenery. Start the sim, clear/delete any rolling cache, then restart the sim, check and report back.

Okay, just realised that I didn't have photogrammetry turned on, just retried it with PG on, and I'm still getting a bump on 4R

Also seeing some bumps at 4R, and 31R.

Same here

I'm not seeing the bump. It may be worth clearing any 'Rolling Cache', and ensuring that you have 'Bing Data' and 'Photogrammetry' turned on.

I had that when I first got EGLL, funnily enough it was a static aircraft addon by LVFR that caused it. Not sure what else to suggest as I'm not familar with the XBOX file structure and what you can, and can't do, sorry.

Are you able to remove all other addons and just leave the Ini EGLL scenery installed? I don't know how the XBOX works, but on the PC it's easy to remove addons temporarily to see if it's a conflict with another addon. Also, are you able to delete the Rolling Cache in the options? If so, try that.

Did you add them one by one so that there were other addons in the folder when you got to EGLL, or was EGLL the only addon in the folder when you encountered the crash? If you haven't, remove all addons, open MSFS, delete any rolling cache, ensure the Asobo Default EGLL is uninstalled if you have it, close MSFS. Delete the Scenery Indexes (typically ... C:\Users\YourUsername\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes). Do a fresh install of EGLL, then start MSFS (with just EGLL in the Community Folder) and try again. Good luck.

It's in Marketplace ...

I don't have the steam version, but my exe.xml file is located .... C:\Users\xxxx\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache For Steam users I believe it may be located in .... xxxx/AppData/Roaming/Microsoft Flight Simulator Where xxxx is your username. If you find it, right click on it and open it with notepad.

Did you update, or do a fresh install? I use Addons Linker, so most of the time I do a fresh install of scenery packages when updates appear, and I'm seeing the SD and HD buttons active. I think the default installation is SD as that was showing after the download. I have HD active now.

Are there any plans to increase the texture resolution on parts of T5C? They are quite low res compared to T5B.

Is that error code when you try to download, or run the installer? If it's when you try and run the installer, maybe disable any antivirus software, and run the installer as 'admin'.