Lincoln,

I flew the same route as a test and was not able to get the Falcon to accurately track the GS for KTPA ILS for 01L. It started down the GS but gradually lost it and by about 500 ft. AGL the GS was pretty bottom of the scale. Is your experience similar, or did it completely fail to capture GS. I see on my GTN that the GTN has captured, but the AP fails to accurately fly it. I am using the RXP GTN 750.

Kind Regards,

I flew short (about 35NM) test flights from KSRQ to KTPA using both the RXP and F1 GTN750s to shoot the ILS 01L approach at Tampa. I did two or three flights with each GTN750 and the Falcon50 tracked the GS in each case to within 1/2 dot or less with final approach speeds in the 130-140 NM range.  I also tried the ILS to 04 at KSAT with the RXP GTN750 and got the same results. So I really don't know what to say at this point. I will do some more testing at other locations.

Are ILS approaches at other locations working for you with the Falcon50?

Al

 

Edited January 19, 20206 yr by ark

10 hours ago, LBC said:

Please ask as many questions as you want. I will be glad to answer tem.

Lincoln,

I think at this point if it were me, I would uninstall the Falcon50 and make sure nothing was left over in the original install location -- no files or folders.  I would also rename the XMLtools64.dll file in the P3D directory to something like XMLtools64_old.dll to force the installer to replace the file. And I would remove the block of code you added to the dll.xml file (or just rename the new xml.dll file to back it up and replace it with your original dll.xml file). Again the idea is to force the installer to update the dll.xml file as it should. Maybe this will fix something in the Win10 Registry that is preventing XMLtools from working as it should.

I know it is a pain to do all this, but I'm running out of ideas. Maybe someone else has an idea.

Al

Edited January 19, 20206 yr by ark

Just to jump in on this, first attempt with a flight on new version using RXP750 and would not fly GS at FLKK (aka FLLS). (That is the first one I had tried!)...

Tried to capture - since it disconnected ALT HOLD, but GS disconnected straight away.

G

Edited January 20, 20206 yr by Gazzareth

21 hours ago, somiller said:

Lincoln,

I flew the same route as a test and was not able to get the Falcon to accurately track the GS for KTPA ILS for 01L. It started down the GS but gradually lost it and by about 500 ft. AGL the GS was pretty bottom of the scale. Is your experience similar, or did it completely fail to capture GS. I see on my GTN that the GTN has captured, but the AP fails to accurately fly it. I am using the RXP GTN 750.

Kind Regards,

In my flight, the Autopilot did not capture the G/S. Only the LOC.

13 hours ago, ark said:

I think at this point if it were me, I would uninstall the Falcon50 and make sure nothing was left over in the original install location -- no files or folders.  I would also rename the XMLtools64.dll file in the P3D directory to something like XMLtools64_old.dll to force the installer to replace the file. And I would remove the block of code you added to the dll.xml file (or just rename the new xml.dll file to back it up and replace it with your original dll.xml file). Again the idea is to force the installer to update the dll.xml file as it should. Maybe this will fix something in the Win10 Registry that is preventing XMLtools from working as it should.

I know it is a pain to do all this, but I'm running out of ideas. Maybe someone else has an idea.

Hell Al.

I will do that and, after reinstall it Iwill post here.

Thanks again,

Lincoln

Al,

I don't have a clue what is happening. Yesterday morning I flew KTPA ILS 01L 3x in a row and it flew it pretty well...no more than about 1/4 ball deviation, with slight LOC deviation. Last night I tried again and no matter what I did I could not get it to track the GS. I was watching the flight director bar an it appears the AP doesn't follow the flight director. The FD deflected down to follow GS, but the AP didn't command pitch down to follow the FS.

Is it possible it has anything to do with this:

Kind Regards,

Since I have it installed in both p3d3 & p3d4 can confirm it is exactly the same in both sims. Just tested with EGPH, tries to pick up the glideslope but fails to follow it properly .... unfortunately the good people of Livingston got a Falcon landing on them 😉

 

G

1 hour ago, somiller said:

Is it possible it has anything to do with this:

Hi Steven,

I saw your post on the RXP forum and asked Jean-Luc to explain a bit more on what that

6 minutes ago, Gazzareth said:

Since I have it installed in both p3d3 & p3d4 can confirm it is exactly the same in both sims. Just tested with EGPH, tries to pick up the glideslope but fails to follow it properly .... unfortunately the good people of Livingston got a Falcon landing on them 😉

 

G

What GPS are you using?  And can I assume you are using the latest Falcon50 ver 1.9A (and not ver 1.9)?

 

Edited January 20, 20206 yr by ark

1 minute ago, ark said:

What GPS are you using?

 

RXP GTN750 .. .. .. if you want can test with P3D3 with the F1GTN, doesn't work for me with P3D4 though......

 

G

12 minutes ago, Gazzareth said:

RXP GTN750 .. .. .. if you want can test with P3D3 with the F1GTN, doesn't work for me with P3D4 though......

 

G

Thanks for the feedback. Please check that the GTN750 setting Connect GPS to HSI is ON in the RXP GTN popup settings window as shown below:

Also, RXP just released an update to the GTN750 that fixed some things. As we try to track down what is happening here please update when you can. Also make sure you have ver 1.9A of the Falcon 50.

Al

Edited January 20, 20206 yr by ark

5 hours ago, ark said:

Thanks for the feedback. Please check that the GTN750 setting Connect GPS to HSI is ON in the RXP GTN popup settings window as shown below:

Also, RXP just released an update to the GTN750 that fixed some things. As we try to track down what is happening here please update when you can. Also make sure you have ver 1.9A of the Falcon 50.

Al

Ok so tested as follows.

Uninstalled Falcon, uninstalled RXP, reinstalled Falcon (latest version), reinstalled RXP (latest version),  checked settings as per your post.

Using P3D3 did the following:

Takeoff from EGPF loaded ILS 06 EGPH, Intercepted, Turned on approach mode, results as follows:

 

Falcon 50 RXP - Intercepted LOC - plane switched from ALT to GS mode then ignored the Glideslope

Learjet 35 RXP - Intercepted LOC - plane switched from ALT to GS mode then followed Glideslope down to minimums

Falcon 50 Flight1 - Intercepted LOC - plane switched from ALT to GS mode then ignored the Glideslope

 

As a final test I did the same flight with RXP using 1.8c and it captured glideslope and followed down to minimums no problem!

G

Edited January 20, 20206 yr by Gazzareth
Added last test !

3 hours ago, Gazzareth said:

Ok so tested as follows.

Uninstalled Falcon, uninstalled RXP, reinstalled Falcon (latest version), reinstalled RXP (latest version),  checked settings as per your post.

Using P3D3 did the following:

Takeoff from EGPF loaded ILS 06 EGPH, Intercepted, Turned on approach mode, results as follows:

 

Falcon 50 RXP - Intercepted LOC - plane switched from ALT to GS mode then ignored the Glideslope

Learjet 35 RXP - Intercepted LOC - plane switched from ALT to GS mode then followed Glideslope down to minimums

Falcon 50 Flight1 - Intercepted LOC - plane switched from ALT to GS mode then ignored the Glideslope

 

As a final test I did the same flight with RXP using 1.8c and it captured glideslope and followed down to minimums no problem!

G

Good feedback.

I don't have P3Dv3 so can only test in P3Dv4.5.  I tried 6 ILS approaches today in the Falcon50 and they all worked OK. I will keep looking into it and also talk with Flysimware (Mark) to see if he has seen this, and will also try to check with another beta tester.

Al

33 minutes ago, ark said:

Good feedback.

I don't have P3Dv3 so can only test in P3Dv4.5.  I tried 6 ILS approaches today in the Falcon50 and they all worked OK. I will keep looking into it and also talk with Flysimware (Mark) to see if he has seen this, and will also try to check with another beta tester.

Al

Should say the only significance of using v3 was that I can't use the F1 GTN in v4. Can test in that if you need, but since that is where I originally saw the issue I can pretty much guarantee the same outcome.

 

Cheers

 

G

"Falcon 50 RXP - Intercepted LOC - plane switched from ALT to GS mode then ignored the Glideslope"

"Learjet 35 RXP - Intercepted LOC - plane switched from ALT to GS mode then followed Glideslope down to minimums"

P3Dv4.5HF2 - Above is exactly what I experience with RXP GTN750 in latest versions of both Falcon and Lear.

What I find troubling is that I've gotten the Falcon to fly the ILS GS, but I can't get it to do it reliably. Based on my tests, it almost seems to be a sim session-based difference, in that if it works once during a sim session it keeps working, but if it doesn't work the first try, it never works. As I mentioned above, Sunday morning I loaded P3D, Falcon 50, and flew 3 approaches to ILS 01L at FT KTPA - all successfully. Sunday night I did the same and the Falcon wouldn't fly the GS. As far as I know I changed NOTHING between those sessions, other than flying other aircraft on other routes during the day. Each time I flew the Falcon it was the first and only aircraft loaded into P3D after a fresh P3D launch, and loaded directly at KTPA.

The Lear flies an ILS like it's on rails, and is a thing of beauty to watch on approach.

Kind Regards,