Certain Terminal Buildings Not Loading

[farmm54]

I have an issue where when landing into LHR certain terminal buildings do not load in. The main pier down towards the control tower of T3 never loads in, and on occasion T5A does not load in. The issue is purely with the buildings themselves. Ground textures, jetbridges, stands etc load. But no terminal building. Every flight some part of T3 is missing. No matter how long I am at the airport the building does not load in.

The only time they are present and fully loaded is if I fly out of LHR to begin with and launch the sim there. 

I have tried a clean reinstall of the scenery too. My PC is pretty high spec as well so no issues with that.

 

Anyone any advice...?

[Eddie]

Hello,

Please try clearing your scenery indexes:

To do that locate your folder by following the path below:
MSFS 2020

Quote

MS Store: %LOCALAPPDATA%\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes
Steam: %APPDATA%\Microsoft Flight Simulator\SceneryIndexes

MSFS 2024

Quote

MS Store: %LOCALAPPDATA%\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SceneryIndexes
Steam: %APPDATA%\Microsoft Flight Simulator 2024\SceneryIndexes

Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS.

Let me know if this resolves your issue. 

[farmm54]

On 4/23/2025 at 10:46 AM, Eddie said:

Hello,

Please try clearing your scenery indexes:

To do that locate your folder by following the path below:
MSFS 2020

MSFS 2024

 

Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS.

Let me know if this resolves your issue. 

Unfortunately this did not resolve the issue.

[Rhys Worlock]

Having the same issue here. I have tried clearing the sceneryindexes folder but still having an issue where terminal 3 won't load up

[MrPetroz]

Similar issue for me, v1.0.3 Terminal 5A (main building) doesn't load in. 

UPDATE - fixed this for myself by deleting the install, then deleting the SceneryIndex folder, then reinstalling. 

 

The SceneryIndex folder is here: 

MS Store:   C:\Users\[YourUsername]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Steam: C:\Users\[YourUsername]\AppData\Roaming\Microsoft Flight Simulator 2024\SceneryIndexes
 

Edited April 30 by MrPetroz
fixed

[farmm54]

On 4/30/2025 at 2:25 PM, MrPetroz said:

Similar issue for me, v1.0.3 Terminal 5A (main building) doesn't load in. 

UPDATE - fixed this for myself by deleting the install, then deleting the SceneryIndex folder, then reinstalling. 

 

The SceneryIndex folder is here: 

MS Store:   C:\Users\[YourUsername]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Steam: C:\Users\[YourUsername]\AppData\Roaming\Microsoft Flight Simulator 2024\SceneryIndexes
 

Tried this also without any success. Always T3 that doesn't load. Everything else is perfect.

Uninstallihg now and going to go back to the previous 2020 version which worked in 24 with no issues

[JS2Tango]

Same here with Terminal 3 not showing. In MSFS24 SU2 Beta

[aceridgey]

Same for me

[jay_cee87]

Me too - Any fix inibuilds?

[twright]

Just had the same problem, landed after a flight and no T3, just floating jetways where it should be. Bit of an immersion killer.

I wonder if it's related to VRAM running out as I noticed my frame rates tank when this happened as well.

When I exit the flight to the world map and then zoom back in T3 reappears again.

[Fornax]

Same here. Im on SU3 beta though. So was wondering if it is that. Asobo EGLL disabled.

Not a VRam issue. 5090, 7900x3d, 64GB Ram.

[christos]

Got the same here, su2

[TankMontana]

Also experiencing T3 not loading in when landing at EGLL, probably every 1 out of 3 flights. Have done all the recommened solutions above and none have solved the issue.  This has been on both SU1 and SU2. I've also had T5A not load as well, but that was when starting my flight at EGLL and a restart fixed that.

Are you folks using "Terminal 3 High Detail" in iniManager? I personally am, so I'm going to test with disabling it to see if that makes any difference. Just trying to see if there is any pattern here given no recent official response on the matter.

[christos]

I'll confirm that I am not using high detail.

[ben4muk]

On 4/30/2025 at 4:25 PM, MrPetroz said:

Similar issue for me, v1.0.3 Terminal 5A (main building) doesn't load in. 

UPDATE - fixed this for myself by deleting the install, then deleting the SceneryIndex folder, then reinstalling. 

 

The SceneryIndex folder is here: 

MS Store:   C:\Users\[YourUsername]\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\SceneryIndexes

Steam: C:\Users\[YourUsername]\AppData\Roaming\Microsoft Flight Simulator 2024\SceneryIndexes
 

NICE!  This fixed it for me!

[FerrevmVnion]

Same here ... missing terminals, removed nool .... not that premium..... and the mentioned fix is not a fix, when flying into EGLL and getting a broken airport...

Edited Saturday at 07:11 PM by FerrevmVnion

[operatorjoelski]

Same issue, what’s going on ini! This is marked as premium product, native with MSFS24 yet a large chunk of a major terminal is missing, is there any way to roll back the version to a earlier release?

[widgeboy]

Same for me.  Just returned from LAX, c10 hours of flying and no T3 on arrival.  Its not the first time its happened, seems to happen only when arriving into the field, not if you load into LHR for departure.  I've tried the various fixes mentioned above and none of them work.  If I go back to "main menu" and re-load onto the same stand as I parked at on arrival, the buildings appear as normal.

Very frustrating!!

[AndyM]

I'm also seeing this.

[fzike]

Same for me; T3 missing all buildings on arrival to EGLL but loads fine if originating flight from T3 gates. I've tried uninstalling and deleting the scenery config folder as suggested above but this does not fix the issue. Very frustrating! 

[AndyM]

On 4/23/2025 at 10:46 AM, Eddie said:

Hello,

Please try clearing your scenery indexes:

To do that locate your folder by following the path below:
MSFS 2020

MSFS 2024

 

Then delete the contents inside but leave the folder intact. The indexes will rebuild on next load of FS.

Let me know if this resolves your issue. 

Any news from the Devs on this issue?

[ben4muk]

On 5/24/2025 at 8:26 PM, ben4muk said:

NICE!  This fixed it for me!

I just did another flight, and no Terminal 3 Piers.  Issue still persists.  I checked my sceneryindexes folder and found the following file:

I am deleting this file and trying again.  I have no other EGLL files in my sceneryindexes folder.  Hopefully this will resolve the issue.  Will report back!

[Speedbird193]

There is no workaround - ini need to fix this and it seems to affect a lot of users. I'm back to using the previous 2020 version of EGLL - everything is loading as it should, no blurry runway when approaching and the correct line up point for 09R. This product needs an urgent patch...

[ben4muk]

2 hours ago, ben4muk said:

I just did another flight, and no Terminal 3 Piers.  Issue still persists.  I checked my sceneryindexes folder and found the following file:

I am deleting this file and trying again.  I have no other EGLL files in my sceneryindexes folder.  Hopefully this will resolve the issue.  Will report back!

Didn't help...

[ksp100]

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?