Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

LatestGTN GS capture problems. Xp and FS

Featured Replies

Default aircraft. B350 P3DV3 and C90 in Xplane 11. Been having problems capturing the GS /LPV both XP and FS with 2.5.12. Either with GUI set to Auto or Manual. When LPV is activated and at correct initial waypoint altutude, the aircraft first climbs then descends violently and never does capture the GS. HSI is displaying correct GS path. Have tried various setups in the configuration with same results. FYI, Loaded the "other guys" latest GTN in FS and shot the same approach using the same settings and worked fine. Could I be omitting something in the setup. Tried everything I can think of. Thank you.

Just flew my standard LPV test approach w V2.5.12.

KTPA, R01L, via PIE at 2600 ft

RealAir Legacy P3DV4.4.

APP mode after glideslope indicators became visible, autopilot flew the approach correctly.

Bert

  • Author
2 hours ago, Bert Pieke said:

Just flew my standard LPV test approach w V2.5.12.

KTPA, R01L, via PIE at 2600 ft

RealAir Legacy P3DV4.4.

APP mode after glideslope indicators became visible, autopilot flew the approach correctly.

Well, im sure its something ive done wrong.; I;ll keep trying different settings. Flown 1000's of approaches so its not a pilot thing....could be. 🙂

 

Btw Bert, did you try it in P3DV3 or 4 because v4 works fine. I only see the issue in V3 with different default aircraft!

 

Edited by Adrian123

38 minutes ago, Adrian123 said:

Btw Bert, did you try it in P3DV3 or 4 because v4 works fine. I only see the issue in V3 with different default aircraft!

 

V4.4. only... maybe it is a Carenado thing.. they supplied default aircraft models for V3.  :cool:

There are HSI GSI, and NAV GSI needles in the P3D coding list... maybe one or the other was screwed up..

Edited by Bert Pieke

Bert

  • Author

Ya Bert. Its just V3 but it's the same with the default aircraft also! . No problem w/V4. No biggy as I rarely use V3 and can use the F1 GTN there.  anyway just kinda wierd.

4 minutes ago, Adrian123 said:

Ya Bert. Its just V3 but it's the same with the default aircraft also! . No problem w/V4. No biggy as I rarely use V3 and can use the F1 GTN there.  anyway just kinda wierd.

As they say:  "Never look back... they may be gaining on you.."  :cool:

V4 it is!

Bert

15 hours ago, Adrian123 said:

Its just V3 but it's the same with the default aircraft also!

Hi,

have you check the RXP log files? I'm wondering whether you're using a P3D3 version for which there is no autopilot support implemented (this is the sole custom hack needed per prepar3D version).

Just let me know if there is any 'oto' mention in the rxpGTN.gau.log file and which version gets reported in this case.

  • Author

Jean-Luc, No mention of "oto" in the log files in. All the aircraft are complete default aircraft, no mods. P3DV3: 3.4.22.19868

19/02/14 14:33:32.495 04424 -    ] # rxpGTN.dll version 2.5.12.0
19/02/14 14:33:32.495 04424 INFO ]

-I want to retract the original XP statement. It was just the known "Certain" aircraft. All else is fine.

 

This P3D3 version is supported. What I'm wondering is the 'behavior' you're describing (nose up then down and dive violently)?!?!?

  • Author
35 minutes ago, RXP said:

This P3D3 version is supported. What I'm wondering is the 'behavior' you're describing (nose up then down and dive violently)?!?!?

Simply put. RXP GTN see's the gs/LPV and activates the APPR mode but  the AP just wont capture it. That certainly acts like the AP of the aircraft and not RXP? But all aircraft?... Could it be a Simconnect issue? BUT, if it were that , why does the F1 GTN work as expected?

-Always been aware if I'm the only one seeing this, its my setup and I'll resolve it. Please Don't waste too much time on this Jean-LUC.  thank you

 

Edited by Adrian123

  • Author

- New observation. V3, The moment the GTN activated the APPR mode, the AP "ALT" disengages. Can that work and why would it? That's seem to be the issue?

-V4 , same aircraft and approach doesn't deactivate the ALT.

Edited by Adrian123

the APPR mode is just 'triggered' using the standard FltSim key event 'KEY_APPR_HOLD_ON'. It might be this aircraft is not pleased with another gauge changing its modes underneath.

This is one of the reasons latest update has this 'command' sent only when you select the corresponding AFMS option, otherwise, it won't do it and you can then manually ARM any autopilot mode you prefer.

Can you confirm you have set "AFMS Engage Autopilot APPR" enabled? What about disable it?

  • Author
12 minutes ago, RXP said:

Can you confirm you have set "AFMS Engage Autopilot APPR" enabled? What about disable it? 

Yes and it still disconnects the ALT. Both enabled and disabled.

Edited by Adrian123

  • 3 weeks later...
On ‎2‎/‎14‎/‎2019 at 10:33 AM, Adrian123 said:

- New observation. V3, The moment the GTN activated the APPR mode, the AP "ALT" disengages. Can that work and why would it? That's seem to be the issue?

-V4 , same aircraft and approach doesn't deactivate the ALT.

I'm having the exact same problem with GNS530 V2. Doesn't matter if "AFMS Engage Autopilot APPR" is enabled or not.

@Adrian123 is this also happening with v2.5.13?

@Spug Do you use the latest GNS v2.4.8? You might want to cross check the RXP log files (see User's Manual for file/path). Each file header (1st line) prints the version number.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.