Working Title G1000 NXi Discussion Thread

I find the NXi works all the time for me because I only use the functions that have been activated.

Weird that we can and you can’t. If you are following Kips videos the Bonanza and G1000NXi should work. That’s all I fly so I don’t know anything else.

MSFS: G1000 NXi RNAV Approach - VNAV Descent / LPV Approach / IFR - Microsoft Flight Simulator - YouTube

It may be a bug introduced in version 0.8.0. It is a work in progress, so these things happen. There will likely be a new NXi update with SU7 tomorrow, though I have seen no official announcement.

This has been confirmed over on their discord. :slight_smile:

2 Likes

Since our initial release on July 27th, 113 days ago, we have released 10 different updates, for an average time of only 11.3 days between updates. We estimate we have well over 6K hours into the NXi.

Aside from holds (complete with proper vectorized entry patterns based on entry angle), the full suite of all possible ARINC leg types (including ones previously unavailable like RF, AF, the many permutations of CF, HF, VM, etc), fully coupled VNAV with path calculation vectorized along even curved flight paths with TOD and BOD indications, a full simulation of proper RNAV types including fully accurate CDI sensitivity transitions and annunciations, correct LPV angular guidance, a fully NXi specific autopilot simulation that captures all the strange G1000 situations you can get into, including combo armed modes like GP/V, or in fact any armed modes at all (which are not available stock), correct direct-to turn and path vectorization, SUSP functionality, missed approaches, the HSI moving map, saved suite of MFD/PFD map options individually broken out between screens, correct declutter modes, accurate map system label collision auto-declutter, the ability to add or remove legs arbitrarily from departure, approach, and arrival procedures, correct direct/enter/enter flows on multiple pages, SVT flight path marker, and many, many other things, it doesn’t really offer much more than the current stock G1000. :wink:

This was a bug introduced in early access 0.8.0 and should be addressed in the next release, which should be tomorrow some time.

The next release will include 8 of the MFD pages: nearest airports, intersections, NDBs, and VORs; and information pages: airport, intersection, NDB, and VOR.

You might try and speak with us on our Discord: there we can get better direct feedback and perhaps solve your issue. We haven’t really had reports of those functions working with that little frequency, so it would be interesting and informative for us to see how you’re using them, and if it’s a case of needing to change your procedures (the NXi is not always intuitive, and we match the real world behavior) or if it is a bug on our end.

You will not see SUSP light up (and it will replace the OBS softkey) until you are actually in the hold pattern. So, if you are looking prior to that, you might not see anything. The plane model should not be relevant here, as there is no plane specific code in the NXi (aside from EIS templates).

This is definitely the first report I’ve seen of FPL sync problems between the PFD and MFD. Do you have some steps we can follow to try and reproduce your issue?

Presently there is an issue where using the NXi will cause erratic GPS/AP behavior on subsequent flights with different planes without a sim restart. This will be resolved with a sim-side update tomorrow with SU7.

Anything we change in the Marketplace description has to go through internationalization and translation services, which can cause release delays. For now, we are opting not to include version changes or the changelog in the Marketplace description itself. We do understand that’s an inconvenience, but for now you can check Working Title NXI - Releases to see what version is presently released, as well as the relevant changelog.

-Matt | Working Title

16 Likes

Keep up the good work, Matt. You and your teams contributions enhance everyone’s enjoyment.

4 Likes

This (the altitude select arc) and the horizontal map path vector will be coming with the next NXi update tomorrow or thereabouts.

-Matt | Working Title

10 Likes

That’s awesome!

1 Like

Working Title Garmin G1000 NXi v0.9.0

New Features

Added MFD Pages

  • Nearest
    • Airports
    • Intersections
    • VORs
    • NDBs
  • WPT Information
    • Airport
    • Intersection
    • VOR
    • NDB

VNAV

  • Added the ability to perform a vertical direct-to using the D-> MFD FPL page softkey
  • Added the VNV Cancel/Enable softkey to the PFD FPL softkey menu

Map System

  • Added aircraft track vector (selectable in MFD MENU)
  • Added selected altitude arc (selectable in MFD MENU)
  • Added MFD MENU settings for airspace display options
  • Aligned display and data update frequencies to real-life unit
  • More accurate styling of TOD/BOD labels
  • Overhaul and optimization of the airspace display system:
    • New airspace renderer offering true circular and vector based boundary display
    • Advanced boundary LOD generation from source boundary vectors for much lighter display load
    • Advanced vector culling outside the map area to avoid drawing to very-low-performance far offscreen areas
    • Improves intermittent high-latency frame times due to huge multi-thousand vector airspaces (such as the China Class B RVSM, which covers the entire country)

Flight Plan

  • Added ability to engage vectors-to-final from the procedures menu
  • Added the ability to create a hold directly from the direct-to page
  • Added setting of inbound course for a direct-to
  • Added MFD FPL-page-specific soft key menu
  • Added shortcut to WPT Information page by pressing ENT on non-relative legs that terminate at a navaid

EIS

  • Add EIS support for ColorLine and ReferenceBug
  • Add EIS support for ValuePos in horizontal gauges

PFD

  • Added option to display metric altitudes on the altimeter

Issues Fixed

  • ETE should now be displayed properly in MM:SS and H+MM instead of HH:MM
  • Fixed an issue where XPDR display would become corrupt when inputting same frequency as currently set
  • Fixed an issue where pressing ENT would not advance past minimums on the PROC approach page
  • Fixed FPL header names sometimes overflowing
  • Dep/Arr confirmation dialog now displays full procedure name
  • Fixed conditions causing MENU press to not open FPL page menu
  • Disabled Activate Leg on leg types which should not be able to be manually activated
  • Added proper message when the flight plan system rejects a duplicate leg input
  • Fixed various incorrect ICAO region names
  • Fixed an issue where visual approach waypoints would continue to display on the map even when the approach was changed
  • Fixed logic around hold-at-waypoint commands.
  • Fixed issue where heading bug would not be properly synced to current heading on flight restart
  • Fixed issue where circling approaches would offer vertical guidance
  • Fixed accuracy errors in horizontal EIS gauges
  • Fixed incorrect active leg arrow style for some leg types
  • Fixed NEXRAD remaning visible at low map ranges
  • Fixed an issue where discrepancies in airport runway number and ILS frequency associated runway number would cause an inability to auto-tune or auto-switch for an ILS approach
  • Fixed overflow of MFD FPL METAR text
  • Fixed non-functional lean assist on the SR22 and Baron
  • Fixed issue where the cancel button on FPL Waypoint Remove did not close the dialog
  • Fixed DTO menu not automatically advancing to activate button in certain situations
  • Fixed a bug where the direct-to page would not accept waypoints input from other pages, such as the nearest airports page
  • Fixed bug where the direct-to waypoint did not have the proper altitude constraint assigned
  • Fixed an issue where both the TOD and BOD markers were drawn on the map simultaneously
  • Fixed bug where deleting a hold origin fix does not delete the hold for that fix
  • Fixed bug where MAPR sensitivity is missing when direct-to a leg in the missed sequence
  • Fixed bug where the GPS To/From flag could be erroneously set in OBS or SUSP mode
  • Improved a number of course-to-fix leg calculations for better flight path vectorization
  • Improved hold calculations, including erroneously chosen entry paths and display
  • Fixed issue where direct-to page would not offer duplicate waypoint resolution

Known Issues

  • Vectors To Final auto-switching the CDI will only work if you have not chosen VECTORS as the transition and you select ‘ACTIVATE VECTORS TO FINAL’ from the PFD; this will be fixed in the next release. For now, if you don’t follow this flow, you will need to manually switch the CDI source for LOC/ILS approaches when VTF is activated.
  • Activating VTF when you are past the FAF (as measured along the final approach course) will cause LNAV to sequence the active leg beyond the FAF. To avoid this, do not activate VTF until you are in a position to intercept the inbound course to the FAF.
  • World Map imports from Navigraph and Simbrief do not include airways, so airways will not be added to the G1000 NXi flight plan when the plan was imported to the World Map from one of these sources.

Heads Up!

  • VNAV now deactivates upon reaching the last constraint (cyan altitude in FPL) prior to a VNAV ineligible leg, such as a MANSEQ, Procedure Turn or Hold. Be aware that if you have a MANSEQ leg at the end of your arrival procedure, without manual intervention, you can (and likely will) end up too high to reasonable descend for the approach. You have three options to navigate this: (1) Manually descend as is reasonable at your discretion; (2) delete the MANSEQ leg to allow VNAV to recalculate by directly connecting the end of the arrival with the beginning of the approach or (3) activate the approach (or proceed direct to the IAF) and VNAV will attempt to calculate a path up to 6 degrees from your current position to the next constraint.
  • GPS, LOC, and VOR modes now ARM! Be aware that you will need to be on an intercept course and within capture distance of the desired flight path before those modes will become active.
  • The GPS flight plan sequencing will enter SUSP under the following conditions: when reaching a manual termination leg (holds, manual sequence) and when reaching the final leg of the plan. This is actually correct behavior. To exit out of SUSP (for example, if you got to the end of a plan and then loaded more waypoints), hit the SUSP softkey in the middle of the PFD.
  • Changing the CDI source drops the autopilot into ROL mode. This is the correct behavior, intended to keep the airplane held in the same attitude until the pilot reselects appropriate guidance.
  • The NXi’s traffic advisory system (TAS) will now start in STANDBY mode by default. While in this mode it will not issue any advisories nor will traffic be displayed on any maps. The system will automatically switch from STANDBY to OPERATING mode after takeoff (and back to STANDBY after landing). You can also manually switch TAS to OPERATING mode through the MFD Traffic Map page (use the MFD FMS knobs to change the open MFD page).
  • The fuel quantity information on the MFD’s sytem page simulates an authentic totalizer. This means it does not actually track the fuel in your tanks, it simply counts how much has been burned and relies on you to tell it what the original quantity was. This means if you add or remove fuel in flight you’ll need to manually adjust the starting quantity in the tanks with the buttons on the GAL REM submenu.
  • The displayed METAR information on the MFD FPL page reflects real-world weather from the sim live weather METARs, so they may not always match in-game conditions, especially if using a weather preset or custom weather.
12 Likes

Many thanks for your response which definitely shows genuine concern and a want to help attitude. This is greatly appreciated as sometimes we feel we’re groping in the dark with no help. Thank you for the offer of speaking on Discord if you would show me how/where to long in. If you have any specific questions for me kindly let me know in advance so as to prep my answers without fumbling and wasting your valuable time. We know you guy’s do a great job in a difficult situation.

Thanks Matt for you and your teams work. Something we can count on.

Can’t operate the FMS outer knob to shift cursor position to the right when entering letters of IDs in the Airport, VOR…MFD pages.

If you want to get these items fixed, it is recommended to use the WT discord. This is not the bug reporting thread.

1 Like

We had another report of that and have it logged. For now using keyboard focus mode will enable you to enter idents on those pages.

There was another report in Discord about activate acting like load the first time. We’ll take a look at it.

The NXi reads whatever navdata is installed in your sim (stock or Navigraph). LAX doesn’t have a 29R. If you’re referring to 25R, I see approaches for ILS 25R, RNAV Y 25R LPV, and RNAV Z 25R. Looking right now in the NXi with stock navdata I see all the correct approaches for KLAX that should appear in the unit.

-Matt | Working Title

2 Likes

can you import a flight plan that is create in littlenavmap?

thanks very much for the reply Matt

1 Like

Thank you for the reply, Matt. After the latest version got released, I was still having the same issues. Seeing others were fine, I committed to finding out why ILS and RNAV was working with stock G1000 and not with NXI. I’m happy, and a little embarrassed, to say I figured it out after hours of videos. It came down to 2 very small, though crucial details. I’m hoping my experience may help others who recently transitioned from stock to NXI. It all had to do with sequencing of ap commands. What we were able to do in the stock does not work in NXI:

RNAV LPV:
Stock G1000 allowed you to engage VNAV at any time, regardless of your altitude select value. In the NXI, you MUST lower your altitude select (ideally to below the altitude of your last step-down) BEFORE engaging VNAV. You will not engage vertical navigation at TOD if you don’t follow this.

ILS:
Stock G1000 has you switching CDI to nav1 or nav2 at any point in which you can capture the localiser frequency. You were also able to activate approach mode any time before or after this action, so long as you were on approach mode prior to gs intercept. The NXI switches to the localiser frequency for you automatically when you’ve loaded an ILS approach into you flight plan; only then I’ve found can you engage approach mode. I was trying to manually switch to the localiser frequency using the cdi button, and also trying to engage approach mode before this as I did in the stock g1000. Apparently this is a no no.

As for the NXI altering other aircraft APs. Matt was kind enough to acknowledge that this was a bug, and I indeed was not going crazy. I haven’t tested, but apparently this was fixed in the last update.

So thank you Matt for your response, and my apologies for doubting the NXI. It was in-fact me all along :slightly_smiling_face:

2 Likes

So, I’ve tried to reproduce this in a bunch of different ways, but I am unable to after some significant testing (with an empty plan, with an already active direct-to, with choosing VECTORS, with a full plan). I always get a proper activation in 0.9.0.

Can you give some additional details on how you’re encountering this? Is this with an empty plan, what steps are you taking to activate the approach, what is the approach you’re activating, are you doing this from the PFD or MFD, Navigraph or stock navdata, etc. That would really help if we could get a reproduceable case to debug.

-Matt | Working Title

I have found an issue with the IFR / VOR training activity while using the G1000 NXi (actions triggered too early, no mode change at the beginning of the lesson). It is described here: SU7 | New lessons : VOR lesson issues with WorkingTitle G1000NXi, "Watch out!" landing, IFR test 110 kt endless leg

Hello. I’m currently flying a bush trip in the Grand Caravan and the navigation map range selection is broken. When zooming, the waypoints, airports, etc… all adjust accordingly, but the land/water on the map do not adjust. Here are two screenshots, one at 25nm range, the other at 5nm range. The waypoints move, but the topo map is stuck.

The range selection does work correctly with the inset map in the primary flight display, so I can correctly zoom in/out on that small version.

I upgraded to latest NXi yesterday after the sim update, so all things should be current.

1 Like