April 29, 201214 yr Byork, I have noticed that the FO "glide slope alive" call occurs some time after G/S has been captured and the aircraft is stable on ILS and not when the g/s magenta diamond becomes visible on the ND, which should be the right time for the call. Is that a bug ? Thanks Regards AMD Ryzen 7800x3d, Asus ROG Strix RTX4090, Asus x670e-e, G-Skill F5-6000J3038F16GX2-TZ5NR
April 30, 201214 yr Commercial Member At what altitude are you capturing the glideslope? B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
April 30, 201214 yr Author Usually as per the approach profile and charts, typically around 1500-2500 ft AGL AMD Ryzen 7800x3d, Asus ROG Strix RTX4090, Asus x670e-e, G-Skill F5-6000J3038F16GX2-TZ5NR
April 30, 201214 yr Commercial Member When are you tuning the ILS? B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
April 30, 201214 yr Author Usually I tune ILS frequency on NAV1 & 2 and LOC course on PF side just before initiating the STAR or vectors to approach if flying on line, and then select VOR/LOC during last turn to intercept Localiser, and then select APP when LOC is captured and the G/S is alive on the ND. I believe this is the standard procedure... Thanks for your time anyway... Regards AMD Ryzen 7800x3d, Asus ROG Strix RTX4090, Asus x670e-e, G-Skill F5-6000J3038F16GX2-TZ5NR
April 30, 201214 yr Commercial Member Which airport and which ILS approach? FS2Crew is reading the Glideslope position directly out of FSX, and not via the PMDG SDK. It generally matches up with what's displayed in the NGX. Perhaps, under some circumstances that maybe the FS glideslope data does not match up with what's displayed on the NGX's PFD. Maybe the NGX is doing something "custom". B. York FS2Crew Web Site / FS2Crew Facebook Page / FS2Crew Discord
Create an account or sign in to comment