On 1/27/2023 at 10:57 AM, DAD said:

interesting, thought by myself today that EGLL with ini v3 is a bit too high

I experienced exactly the same only yesterday flying into RWY02 at Barcelona.

@DAD @Rockliffe I think i found the issue here. Watch your PFD. Its in 'FAC' and 'G/P' mode. Meaning, the glidepath data and "localizer" coming from the FMC and not from the actual ILS. Now, if while on approach you start messing with baro qnh, you will notice how it changes the glideslope location. In ILS it does not relay on the QNH but intercept the ILS glideslope radio signal to determine the plane position in the glideslope. 

One thing I did not figured out yet is how to make the plane follow the 'real' ILS signal and not the FMC path. 

 

Update- i think i figured it. you need to make sure you set both nav radios to the ILS frequency. it will than change from 'FAC' 'G/P' to 'VOR/LOC' 'G/S'  

Edited February 1, 20233 yr by roi1862

Sorry to bring this back from the "past", but i found this video from 2 weeks ago. apparently its a known thing.  

 

The difference between the Fenix and PMDG is interesting.  I have been flying the 737 almost exclusively lately, though I do have the Fenix, and have gotten used to just undershooting the ILS.  Yes i have the ILS tuned on both NAV radios and the course set.  I also use the HGS frequently.  It's not a big deal to adjust visually in decent weather but i was basically down to cat iiia conditions the other night with a 20 kn crosswind.  Much harder to confidently fly below glideslope to hit the touchdown zone in those conditions.  It seems like it's for sure an MSFS issue as pointed out by the always wonderful 737NGDriver.  Till someone actually takes ownership and does something about it..... it'll just make flying a tad bit more interesting.  

I thought it was just me but since watching that video, now I follow the green cross on the FD and not the diamond and i'm spot on every time.  I now ignore the diamond and papi lights. Sucks until they fix this...if they ever do...