AndyM

Better to remove it to stop any conflicts.

I don't think so, all airports I've seen tend to have images of the terminals. Not sure if iniScene have done it intentionally, or it's just an error. To be honest I've not noticed it before.

Sorry to hear that it didn't fix your issue, it's strange how issues affect some people, and not others.

I'm seeing the same.

Might be worth trying the following in this order .... 1. Delete any rolling cache, and temporarily turn it off. Ensure you have the default Asobo EGLL uninstalled. 2. Exit MSFS 3. Delete the Content.xml file. For MS store version it's :- (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xml) 4. Delete the simulator .dat files. For MS store version it's :- (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes\*.dat) 5. Remove everything other than the EGLL scenery to the Community folder. 6. Start MSFS and try EGLL. 7. If okay, start to restore options and additional scenery testing EGLL as you go.

Under 'Airport Life' in the TRAFFIC options, have you got 'Ground Aircraft Density' set to 0?

Showing v1..2.2 after the update for me. My community folder is outside of C drive { "dependencies": [], "content_type": "SCENERY", "title": "EGLL Heathrow Airport", "manufacturer": "", "creator": "iniScene", "package_version": "1.2.2", "minimum_game_version": "1.25.7", "release_notes": { "neutral": { "LastUpdate": "", "OlderHistory": "" } } }

Hi, is there any plans to make the fronts of the terminals a little more detailed? I flew out to the US last week on holiday, so have attached the a photo of the stand 545 in T5, and your scenery as a comparison. I appreciate that the scenery is already quite large, but you could always lose a little clutter from area's that no one goes to offset the additions. At the end of the day it's all about immersion, and this is a flight sim, not a passenger sim. thanks.

Okay, I had it working, after the SU9 update, it wasn't working anymore. After some investigation I noticed that SU9 had enabled Rolling Cache (which I have disabled). I deleted it, turned it off, restarted the sim and it is working again, well, definitely with the latest Dev version of the A32NX, not tried other aircraft. Might be worth trying the following in this order .... 1. Delete any rolling cache, and temporarily turn it off. Ensure you have the default Asobo EGLL uninstalled. 2. Exit MSFS 3. Delete the Content.xml file. For MS store version it's :- (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Content.xml) 4. Delete the simulator .dat files. For MS store version it's :- (AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SceneryIndexes\*.dat) 5. Remove everything other than the EGLL scenery to the Community folder. 6. Start MSFS and try 09L, if working start to load and re-enable addons and options, testing 09L as you go.

If you have the deluxe version of MSFS, have you made sure that you have uninstalled the Asobo version?

No, it is recommended that you remove the contents of the Community Folder prior to the Sim Updates, make sure the sim is working okay, then install the addons back in to the Community Folder, maybe a few at a time to make sure there are no issues. I delete the Content.xml file as a matter of course maybe once a month, and let the sim rebuild it. I find it cuts down on some of the issues I used to get. I also don't use Rolling Cache as that has caused me a few problems with scenery addons in the past.

Just tried it once more, set the aircraft up on 09L approach and worked again.

No. Before updating to the latest beta SU9, I removed everything from my Community Folder (cut and paste a couple of permanent items to a backup folder, and disabled the others through the 'MSFS Addons Linker' program). I then updated to SU9, started MSFS to make sure it was working okay, then shut it down. I installed everything back prior to the installation and started MSFS. On the first attempt at 09L the ILS wasn't working. I exited MSFS, deleted the Content.xml file in 'C:\Users\xxxxx\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache' and tried the same scenario with 09L and it worked.

Okay, with SU9 installed, the first time I set up a 09L approach, no ILS. I exited the sim, deleted the Content.xml, retried the approach and it worked.

Something weird is going on, today I flew from Glasgow to Heathrow, 09L didn't work, I then flew from Manchester to Heathrow, and it worked okay.

I believe the location for the Steam version might be ...... C:\Users\xxxxx\appdata\roaming\Microsoft Flight Simulator\Content.xml (xxxx will be your user profile)

No problem, let us know how you get on.

You could try this, worked for me, but for some reason a few people still seem to have problems.

Okay, just checking and trying to figure out why some people are not getting the ILS. I've just switched from the Dev to the Exp version to try out the new VNAV, flew from EDDK to EGLL and did a perfect autoland on 09L, strange.

Okay, so if you are getting the ILS indication on the PFD, but the approach button is not working, can I ask if you have selected the LS (Landing System) button?

Okay, for those of you not already done so, please do these steps in this order ...... Start MSFS For those with Premium Edition, search for the Asobo EGLL in the content manager and delete Enable rolling cache (if not already enabled), delete it and turn it off Exit MSFS Remove everything from your community folder (cut and paste to a different location) Delete the content.xml Start MSFS Exit MSFS Install just the Inibuilds EGLL in to the community folder (and move to your MSFS Addons Linker Folder and enable if using), and the FBW aircraft if desired Start MSFS and see if it is still the same and report back (enable rolling cache is desired).

Is there anyway you can add library excludes to the Concorde area in a future update? I have LVFR static aircraft and noticed dual Concorde's. Thanks. https://ibb.co/gzmqGfG

Okay, just trying to rule out the simple things that people have found to have fixed the issue. Really strange how some people are affected and some not, mine was simply deleting the content.xml file. Hope you find a fix soon.

What about deleting the content.xml file?

You mention that you have cache off, but have you made sure you have deleted any prior to turning off?