AndyM

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?

Have you tried it with no other addons in your Community folder other than just the Heathrow scenery?

To be fair I uninstalled the Asobo version and had the ILS issues, but after deleting the content.xml the problem went. I use Heathrow quite a lot and have not had a problem since, and have used a number of different builds of the EXP and DEV versions of the FBW A32NX. I do use the Addons Linker tool and just load the scenery and aircraft for the particular flight I'm about to do, and once every couple of weeks I delete the content.xml file.

Can I make a suggestion regarding the ILS issue you have if you haven't already tried it. Remove all other addons from you community folder (cut and paste to a separate folder), and again delete the content.xml file, and try it with just the EGLL scenery and your FBW aircraft.

For some of us deleting the Content.xml file has fixed this issue. Personally I uninstalled the default Asobo EGLL and cleared my cache as well.

No, it's easy, just cut and paste to a different directory. The reason I mention it is that there may be a conflict between the addons. If your community folder is empty with just your EGLL in it, and it's still the same, then inibuilds may have used a default texture that you may be missing.

I know you have probably done most of this already, but can I suggest you start MSFS, delete any cache, close MSFS. Delete the Contents.xml, then move all the contents from your Community Folder to a different location so that it's empty. Then do a clean install of just the EGLL scenery, start MSFS and see if there is any difference.

Which ILS? I've just finished a flight using 09L and all was okay. There was an issue with the ILS for some people (including me) which was resolved by deleting the Content.xml file.

Do you mean ALL buildings, or just those over a certain height like the control tower?

If you have the MS Store version, it should be .... C:\Users\xxxxx\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalCache Where xxxxx is you user name. For Steam, I don't know, sorry. ( For Steam it might be ...... C:\Users\xxxxx\appdata\roaming\Microsoft Flight Simulator\Content.xml )

I just switched back from the Development version to the latest Experimental version of the FBW A32NX and just tried exactly what you did, and 09L ILS was working for me. The only thing I've done recently was to delete my Content.xml

Okay, I switched from the Experimental version to the Development version of the FBW A32NX and 09L worked for me this time, so it looks like it may be an issue within some aircraft.

Yes