Sign in to follow this  
JRBarrett

Version 4.2, P3D4.3 Glideslope Indicator problem

Recommended Posts

I did an ILS approach to runway 24 at KELM this morning, my first flight since updating to version 4.2 of the Falcon. I am still on P3D version 4.3

I have a single instance of the RXP GTN-750

I was established on the localizer, in APP mode,  level at 3,200 feet, waiting to intercept the glideslope at the IAF, (ALP NDB). The autopilot mode indicators were showing localizer captured, and glideslope armed.

The glideslope flag on the ADI was out of view, and the needle was deflected fully up as would be expected.

As I approached ALP, I would normally expect to see the glideslope needle begin moving down toward center, but that did not happen. It remained deflected fully up. However, just as I crossed ALP, the autopilot captured the glideslope, and began descending, just as it should.

The glideslope needle remained fully up, even though the autopilot flew the glideslope perfectly, and I was able to make a normal landing. I.e. the glideslope is working (as far as the autopilot is concerned), but the ADI (and the HSI) vertical deviation indicators are stuck fully up.

I restarted the sim, and re-spawned the aircraft on the threshold of runway 24 at KELM, and tuned the ILS I-ELM (109.1) on both Nav 1 on RXP GTN, and the stand-alone #2 NAV radio coupled to the copilot ADI and HSI. I put the aircraft in slew mode, and began slewing up. The glideslope needles on both pilot and copilot sides remained deflected fully up, until the glideslope flag finally deployed at about 460 feet AGL.

I repeated this test at the same location using the default Baron, and the glideslope needle in that aircraft worked correctly, coming off of the upper limit when I was at about 60 feet AGL, centering, and finally going full down as I continued slewing higher.

I know the Falcon glideslope indicator was working previously (I last flew an ILS in Rev 3.9), so something has changed recently.

 

Jim Barrett 

Share this post


Link to post
Help AVSIM continue to serve you!
Please donate today!

20 minutes ago, JRBarrett said:

I did an ILS approach to runway 24 at KELM this morning, my first flight since updating to version 4.2 of the Falcon. I am still on P3D version 4.3

I have a single instance of the RXP GTN-750

I was established on the localizer, in APP mode,  level at 3,200 feet, waiting to intercept the glideslope at the IAF, (ALP NDB). The autopilot mode indicators were showing localizer captured, and glideslope armed.

The glideslope flag on the ADI was out of view, and the needle was deflected fully up as would be expected.

As I approached ALP, I would normally expect to see the glideslope needle begin moving down toward center, but that did not happen. It remained deflected fully up. However, just as I crossed ALP, the autopilot captured the glideslope, and began descending, just as it should.

The glideslope needle remained fully up, even though the autopilot flew the glideslope perfectly, and I was able to make a normal landing. I.e. the glideslope is working (as far as the autopilot is concerned), but the ADI (and the HSI) vertical deviation indicators are stuck fully up.

I restarted the sim, and re-spawned the aircraft on the threshold of runway 24 at KELM, and tuned the ILS I-ELM (109.1) on both Nav 1 on RXP GTN, and the stand-alone #2 NAV radio coupled to the copilot ADI and HSI. I put the aircraft in slew mode, and began slewing up. The glideslope needles on both pilot and copilot sides remained deflected fully up, until the glideslope flag finally deployed at about 460 feet AGL.

I repeated this test at the same location using the default Baron, and the glideslope needle in that aircraft worked correctly, coming off of the upper limit when I was at about 60 feet AGL, centering, and finally going full down as I continued slewing higher.

I know the Falcon glideslope indicator was working previously (I last flew an ILS in Rev 3.9), so something has changed recently.

 

Jim Barrett 

Hi Jim,

Yes, I am seeing the same thing. Mark was working on the co-pilot GS the other day so it looks like something got messed up either with the code or what ended up in the installer.  Will be fixed tonight I suspect.

Thx,

Al

Share this post


Link to post
17 hours ago, JRBarrett said:

The glideslope needle remained fully up, even though the autopilot flew the glideslope perfectly

yes just done a ILS landing at KCLM ( 108.9) , got the same result with the FSW GPS.  F50 ver 4.2,  no gtn 750 installed at the moment.

bob

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this