bpcw001

I couldn't care less and would rather love to see the already existing (and promising) Citation Longitude get a flight model and study-level systems depth overhaul. This bird can get you anywhere with its 3.500nm range and ample cruise speed. Or brush up the already existing CJ4 which is also decent as a starting point. Personally, not too interested in flying the low-speed, low-range Citations, no matter how good they're done in the sim. If only MSFS had a Challenger 650 as good as the one for X-Plane ...

Having a long-time sim background and now on MSFS, I ventured into X-Plane for the first time because of an aircraft addon that is available for X-Plane only. Yes, it's less polished than MSFS. Yes, it needs more work. But I found it to be appealing in many regards nevertheless, and it's definitely a keeper. Oddly enough, ever since I got into X-Plane, I find myself firing up MSFS less and less .... It all comes down to personal preferences. Arguing that other sims should be dropped and all development efforts should go to MSFS exclusively instead are just hilarious.

Some things finally come true. Amazing! Thanks for that mod!

Well I hope to see David‘s LLBG for P3D v4 as soon as it is possible. I have been following his work and what can be seen already is awesome. I hope David won‘t get caught up in perfectionism and delay the release over and over again.

ok thanks. It will become interesting for me again once the navigational aspects have been improved.

Hi, Is the NGXu finally capable of handling RF (radius to fix) legs or does it still use the „old“ PMDG navdata format? Thanks

Sorry for the late reply. Been quite busy recently. Definitely interested. Will send email through PM.

Having read a bit around on the RXP GTN forums it appears that LinkVor = true is a requirement for vertical guidance autopilot approach coupling to work. So it appears that the Lear 35 RMI must learn to deal with this and keep both VOR channels open independent of GPS mode or ILS coupling ( the latter only using VOR1 and not blocking VOR2 as well).

Cool. Thanks for considering this.

Hi, using latest GTN 750 in P3D v4.4 I have the GTN configured to use „simulator“ as clock source. That works fine as to the fact that the GTN will start up with the time set in P3D. However, when using time acceleration, this will have no effect on the elapsed time when using the flight timers within the GTN. The clock speed of the GTN will stay at 1x, which of course gives totally wrong results for time accelerated flights. Should the GTN clock speed not adapt to simulator speed when clock source is set to „simulator“ ?

Now, as far as I can see, when LinkVor = false, the glide slope *is* there for LPV approaches. The problem is that the red vertical GS flags across the sides of ADI and HSI do not clear away. Next to the red flags, on the right side, you can see a tiny yellow arrow tip that moves with vertical guidance in case an LPV approach is active. It appears that the flags obstruct the yellow vertical guidance pointers. You can even see more of the yellow vertical guidance if the deviation is big so the yellow arrows go above or below the red flags. See here: https://ibb.co/G7X91FV However, on arming the GS on the autopilot system, GS will not be captured (presumably because the signal is flagged as invalid). Unless there is a setting in the RXP GTN.ini file other than LinkVor=true which kills the VOR indications on the RMI (please share!), I think the Lear ADI/HSI should take away the GS flags and make the autopilot accept the vertical signal as soon as there is any GS input and work properly with LinkVor = false

I‘ll tinker with it some more. Let‘s see what I can come up with.

if it wasn‘t for the LPV vertical guidance it would be perfect. VOR1 and 2 completely separated from GPS.

Yes, that brings back both(!) VOR needles on the RMI independent of GPS or VLOC mode. But you lose RNAV/LPV vertical guidance 😞. That seems to require VOR linking to be set to true, I just tried it with LPV approaches into LFSB. No glide slope on Lear HSI with VOR linking in GTN disabled. Other ideas?

Hi, I am using the latest Lear 35 together with a single RXP GTN unit (version 2.5.16.0) The GTN, as a single unit, is configured to COM1/NAV1, so my expectation is that it would only occupy the VOR1 channel via GPS. I have put the frequency of a nearby VOR in both NAV1 and NAV2 and set both RMI needles to VOR. Now, look at this: In VLOC mode, both RMI needles indicate the selected VOR, as expected: https://ibb.co/W0z9jMV Now, the GTN is switched to GPS. Upon doing so, I lose the VOR1 indication on the RMI, since it is now coupled to the GPS. This works as expected: https://ibb.co/187jKrp Now, I add a waypoint to the flight plan in the GTN. Upon entering the waypoint, VOR2 indication on the RMI is lost: https://ibb.co/XLSm0h8 However, the VOR2 channel should not be affected by the GTN at all, since it is configured to take COM1/NAV1. What is wrong here? GTN config: [GTN_750_1] ; comma separated list of read only settings. locked = LinkOto,LinkCrs,LinkObs,LinkVor,AutoNavGps,AutoSelect,UseFailures,UseSimGpsCmds,LinkSimGps,AutoSavePln,UseAltMouse,UseLegacyVars ; is the master device if true. MasterDevice = true ReduceRate = true LinkCrs = true LinkObs = true LinkVor = true UseSimGpsCmds = true LinkSimGps = true UseAltMouse = true VFRcode = #7000 OwnshipIcon = BUSINESS_JET ; aviation db: 0: nav_db2_grm, 1: nav_db2, 2: nav_heli_db2_grmn, 3: nav_heli_db2 NavDbType = 1 VFRmode = VFR_EUR AFMS.rf_procedure_legs = 1 FuelType = JETA PowerSource = BUS_AVIONICS TawsSurface = HARD Rheostat.Display = 67 AutoNavSource = 1 Rheostat.Buttons = 67 UseFailures = true MasterVolume = 50 [GTN_750_1.DEFAULT] ; show screen only gauge if true. nobezel = false ; screen only border size (pixels). border.size = 0 ; screen only border color (#RGB or #RGBA). border.rgba = #000000 ; display mouse tooltips if true. tooltips = false ; enable mouse clickspots if true, disable if false. usemouse = true ; enable alternate click-spots (left CCW, right CW, middle Push) if true. usealtmouse = false ; enable touch beyond screen bounds if true (2D only), clip if false (GTN native). extendtouch = true ; auto-resize dimension (width,height) refsize = ; left mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225) (requires SHIFT+left mouse button). popleft = ; right mouse button on the screen toggles popup window by ident (ex: GPS_PANEL or 225). popright = ; adjust brightness (0 to 100) brightness.bezel = 100 ; offset brightness (-100 to +100) brightness.screen = 0 Thanks for looking into this.

I might add that while using IAS hold is the preferred mode in climb, V/S for climbing can be mandated in strong gusty and changing winds. In such conditions, IAS hold mode can lead to huge pitch oscillations resulting in bobbing motions as the aircraft chases IAS. Pretty uncomfortable for pax and pilots alike.

+1 vote for fixing the landing and taxi lights. Really difficult to see taxi lanes and markings on the ground at night, on some payware airports even with only the taxi lights on. I tried to tinker around with the lighting based on what I found in the aircraft.cfg, but found that it has no effect. The lighting seems to be compiled into the model.

I should have mentioned that I am using the RXP GTN. Sorry. No F1 here. Been flying a lot lately, but first time I run into this.

Hi, Please have a look at the following: https://ibb.co/d4dXqwV The Lear is tracking the flightplan correctly, but with constant lateral offset. This happened on the second leg. First leg from freshly started P3D was without issues, for approach GPS was switched to VLOC to shoot an ILS. On turnaround, without restarting P3D, after new flight plan inserted in GTN, GPS guidance was again selected, and flight plan was flown with the observed lateral offset. GTN is configued to automatically adjust the HSI course. Sim is P3D v4.4 on Win 10. Any ideas?

As I was suspecting, none of the GPS approaches you mentioned has vertical guidance by design. The RNAV part only gives lateral guidance. An RNAV approach with vertical guidance requires RNAV/LNAV or RNAV/LPV designations and minima. Compare to e. g. the RNAV approach charts for Teterboro (KTEB) which should come up with vertical guidance.

Lear 35's with GTN are not that uncommon. But interesting to see it was built into a Falcon 50. Nice find! If only we had GTN crossfill available, it would be the icing on the cake 🙂

What was the actual approach you were flying? Not all RNAV approaches have vertical guidance.

Thanks for the information. At least the issue has been identified now. Looking forward to the next update!

Toying a bit more around with this, I realized the same and can confirm your observations. Hopefully RXP will look into this.

Exactly my obervations!