Working Title G1000 NXi Discussion Thread

Did all the Com 1/2 buttons in the middle stop working in the latest version? Thanks!

Thanks for the tip. I’ve checked out the lock mode and description of dealing with complex controls. I’ll give it another try.

So yes right clicking while holding left makes an arrow cursor appear on the map. Then as I advance the cursor towards edges of the map, it moves nicely. Easy when you know what to do.

Hello, great job, I’ve installed it and love it!
I would have a question regarding ETE/ETA. Is it possible to either have the ETA displayed somewhere or FP ETE instead of leg ETE?
Is there a setting?

2 Likes

So you have to install it to see what version is being offered? Seems bizarre to me.

The current version is always going to be what’s offered in the in-game Marketplace. So no apparent need to know which version will be installed. Today, it’s 0.8.0.

For those who don’t know what version they have: Open the sim, click on Profile, click on Content Manager, check the Installed box, scroll down until you see the G1000NXi. If it’s installed, the version number is plainly stated, if it needs an update, it will tell you. If you don’t see it, well…

From the PC version. I don’t know if it’s different on the XBox.

Yes, the MFD is completely configurable.

How? I have looked through all the MFD settings and see nothing to set destination ETA on the status bar as opposed to ETE of the next waypoint. I may be overlooking something, but I just do not find that option.

Same here. I couldn’t find how to add that field or change the leg ETE to FP ETE. If there is a way and you share it, it would be highly appreciated.

I now see this discussion is about the NXi. I know that the G3000 is configurable this way and perhaps the earlier WT G1000 was too. I don’t know if the NXi is or if this is still something they have to develop.

Afaik, there was a variable in a script file that could be changed, but not anymore.

Don’t know if this is by design in the newest version but I can no longer automatically capture a VNAV descent from the calculated TOD to BOD segment as in the prior versions. In prior version this would happen when in range of the TOD and once you pressed the VNAV button, the VPATH indicator would appear together with the pink arrows on the altitude tape. Once the aircraft reached the TOD it would automatically descend. In the present version when I press VNAV in same circumstances nothing appears to indicate the VPATH is armed and ready for automatic descent. The pink arrows do appear however and indicate an advisory path. So is this change now in keeping with how the real unit functions, i.e. VNAV before an approach is advisory only? Once the aircraft reaches the IAF the VPATH does work as it used to. Any thoughts or advice?

Using the keyboard mode to manually input Enroute waypoints disables all mouse functionality in the
cockpit for me. The mouse still works on the PFD and MFD controls but nothing else and the flight must be restarted to recover. Oddly enough, using the keyboard icon to manually input departure and destination airports works fine. The mouse disruption only seems to occur with Enroute waypoint entries.

Before entering the approach, are you using the ALT knobs to set an altitude lower than any altitude listed in the approach? My understanding is doing this gives permission to the Garmin to automatically descend. If I leave the setting higher than these approach altitudes, the plane will not automatically descend during the approach.

I have also found the NXI to be forgiving if I am already in an activated RNAV approach with vertical guidance but I am not descending because I forget to lower that altitude setting. To get the descent working:

  1. Use the ALT knobs to lower the altitude setting below the lowest approach altitude listed
  2. Use VS to descend just until the plane is at or below the altitude I should be at this point of the approach
  3. Click APR to get back to approach mode
  4. Click the VNV button

I think that is what I did today to get the automatic descent locked on the RNAV glide slope.

When I do remember to drop the altitude setting with the ALT knobs and click APR and VNV just before entering the approach, the only thing I have to do is adjust the throttle until the plane is almost at the runway as the Garmin is doing the horizontal and vertical navigation.

1 Like

It’s pretty obvious why someone would want to know. As it stands, the version available does not meet my needs. So I have to uninstall it to go back to the G1000.
Are you seriously suggesting that I should download and install it each day to see if there’s a new version out?

That’s fair enough if it doesn’t meet your needs at the moment.

Instead of installing, why not periodically view Working Title NXI - Intro and click Changelog to see if the latest version will be a winner for you?

2 Likes

Thanks for your reply AviatorCSnet. I do in fact lower the altitude setting as suggested, just as I have always done in prior versions. Your points 2.-4. do not apply to my situation. The approach VNav works fine, just not the automatic initial descent when it hits the first TOD enroute at cruising altitude. This of course happens well before the IAF and previously did not require manual descent using VS. It may be something in my community folder is interfering with this function, or simply that this functionality is no longer there as that’s not how the real unit works.

When a new version comes out, Matt from Working Title normally posts an announcement right here in this very forum thread.

I am curious as to what way the NXi does not meet your needs? Comparing the two versions, I find the NXi is far more capable in almost every regard than the default G-1000. IOW, what functionality does the original G-1000 have, that is lacking in the NXi?

1 Like

Currently have an issue with G1000nxi affecting the other plane’s avionics (G3X, G3000) after SU6 on Xbox series x. If a start a flight using G1000nxi plane, any subsequent flights I create with different planes have broken avionics. All nearest airports are from the flight I created with the G1000nxi plane, they don’t seem to update to the new area. HSI is broken with GPS or VOR. No distance is displayed if I manually enter a nearby airport or waypoint. It still plots the correct route on GPS and VFR map but not on the plane avionics.
I reinstalled the sim, with no world updates or planes and most importantly without G1000nxi mod, and everything works great. As soon as I install the mod, and start a flight with a g1000nxi plane, all subsequent flights display the same problem. Even tried removing the mod using content manager, the default G1000 had the same bug.
Restarting the sim solves the problem until it is triggered by a G1000nxi aircraft. Never experienced this before SU6 update.

Thank you, I understand now that the TOD is before you reach the start of the approach. I have not seen a TOD before the approach in my flights so if I do I will see what happens when I cross it.

Agree. Always thought knowing countdown to destination will be great but this only a “niice to have” as there are other more important aspects/functions to be fixed. See my new post for detail.