There is still a bug evident in the OP’s original photo. EDDH-EKCH is a relatively short flight, but in that shot, not only is the NAV radio “stuck” on the departure airport ILS frequency, but it is showing the EDDH identifier and DME distance is 12.8 nm which is impossible, because the aircraft is close to EKCH - probably at least 130 miles away from EDDH by that point. Even if the NAV is just tuned to the wrong frequency, it should not be showing a DME reading from a distant ILS.
This plane needs MAJOR work. The ILS doesn’t capture… I was on KDCA ILS rwy 01, when I even re-enter the ILS, 109.9, it won’t change in the FMC – stays at 108.9. Then I tried changing ILS’s and the entire MCDU crashed.
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
ILS never autotunes for me. Either on departure or on approach. I have to manually enter the 3-letter identifier for the ILS to get it to work and even then, LOC capture is very wobbly. By default, when hitting LS button on Approach, ILS freq 108.1 will be displayed, even when there is no freq populated in the RAD NAV page.
Are you using DX11 or DX12?
Are you using DLSS?
If relevant, provide additional screenshots/video:
I’ve done three flights and the ILS has never auto-tuned. It’s always set to 108.1 when I hit the LS button, but going ot RAD NAV and there’s nothing there. Today I tried the 3-letter code for the ILS and that worked but the plane chased it all over the place.
If this is as alpha as I think it is, I’ll be the next patch we get will be night/day difference.