Can you post a screenshot of the PFD that you see now that it’s installed?
-Matt | Working Title
Settings memory is not yet fully implemented, but we are adding more settings to it as we go in the NXi. Should be some more added with the next release.
-Matt | Working Title
3 Likes
OK, but at some point, didn’t it save it? Or was that just Map North Up, or am I losing my mind 
The NXi is rewritten from scratch, so every feature in the G1000 mod shouldn’t be expected to exist yet. 
1 Like
I was but today I went in again and checked the marketplace to ‘double-check’ as it still says 'installed. However now afte visit it was NOT installed/downloaded? Not sure about any of this but I tried again and it installed. Now to get to working out the way it all works. Quite different for a old timer than either has been flying Jets and or came from VOR/VOR steam gage dayzzz
THX everyone for at least trying to help 
1 Like
As reported by other users it intially works fine after the 1st install, but then CTDs occur on subsequent loads of MSFS.
Same thing here. Hoping the upcoming new version mentioned above (issues with Bing Maps) actually solves this. Really looking forward to having it installed again.
1 Like
I can sure relate to that… I have done more glass cockpit flying the past ten days than I have in the past ten months.
The NXi - even at the early access stage - is a really nice addition to MSFS.
1 Like
yes, that is my experience also.
Good to hear that ADF is coming. Thx!
How do I remove this mod?
Yesterday I added the G100 NXi through the steam marketplace to give it a try as I am currently trying to learn how to use the G1000 properly.
After finding that some of the functionality is not yet implemented I thought I should go back to the default G100 as this is what I have instructions for so I went to content manager and deleted the NXi version. Now whenever I try to fly a G1000 plane, FS goes not responding and I have to terminate it through task manager. is there a proper way to remove this so I can get back to learning the G1000?
That’s exactly how to remove it. Any Marketplace item is managed through Content Manager once purchased and installed.
A quick check is to clear your Community folder and see if there’s something else in there that’s contributing to the freeze.
It downloads into the “official” folder. When downloading, you could probably send it to your community folder, but as another poster here indicated, it could then conflict with the stock G1000, in which case MSFS would likely crash. I have now flown, cumulatively, for a couple of hours without a CTD – and without either of the Working Title Garmin mods. The advantage of the G1000 NXi – when it doesn’t crash the sim – is the addition of VNAV/VPTH capability at some airports. I haven’t done a survey, but just from looking at approach options at airports with which I’m familiar, I’ve found that ones I’d expect to have this capability do not. They only have LNAV, which keeps your plane lined up with the runway centerline. You still have to manage descent altitudes yourself. I prefer to use ILS runways. The “stock” G1000 supports ILS approaches; the G1000 NXi’s doesn’t at present, and aside from the CTD issues, that is a big drawback for me.
This is a curious bit of information. The NXi fully supports ILS approaches.
VNAV works any time a procedure contains altitude restrictions, which for approaches is all of them. Additionally, LPV is provided for all RNAV approaches.
I’m a little confused as to where you’re looking or what behavior you seem to be seeing.
-Matt | Working Title
2 Likes
With respect to ILS approaches, I’m recounting my own experience. I’ve tried to fly an ILS approach with the G1000 NXi. As I’ve noted in another post, when I get to the approach intersection with the LOC signal and switch the PFD from GPS to LOC, the green arrow comes up pointing 90 degrees off the runway heading. Another poster here said I shouldn’t pay attention to this and that the plane would still follow the glideslope. So the next time this happened, I did not intervene, and my plane – a G36 – immediately went off course.
As for VNAV, I know that it does work up (or down) to a certain point. I tried it on an approach to Salinas, after having entered all the waypoint altitudes prior to takeoff. And the plane did commence descending per the FPL. But because the RNAV approach to Salinas doesn’t support VNAV/VPTH, I had to disengage the AP and hand-fly the plane to the runway. This same runway has ILS capability, so I was surprised to see only LVAV noted on the approach plate. My point was that VNAV doesn’t always stand in for ILS at many airports.
Matt, the ILS issue is of minor concern to me compared to the CTDs I’ve encountered, which seem at least circumstantially related to the G1000 NXi. I’ve posted about this at some length already, but to recapitulate:
- I flew with the G1000 NXi several times (I wasn’t counting) without any issue other than the ILS stuff. This included an RNAV flight from Watsonville to Salinas in which the VNAV approach (RNAV Y RWY 31) worked.
- However, at the start of a subsequent flight from Watsonville to San Jose in the G36, the G1000 NXi’s MFD map screen background was black–instead of the usual green and blue. I took off anyway. The sim froze and CTD’d shortly after takeoff – after I engaged the autopilot, using my Logitech multipanel. I think I was trying to adjust the altitude when this happened.
- After closing out my related apps (TrackIR and Steam), I shut down my PC, disconnected the multipanel (in case it was somehow conflicting with the G1000 NXi’s AP), restarted my PC, launched Steam, launched MSFS, went to the World Map, “refiled” my KWVI to KSJC flight plan, and clicked “Fly.” MSFS crashed to desktop.
- Thinking this problem might be particular to the G1000 NXi, I reconnected the multipanel, rebooted my PC, etc., switched planes to the Daher TBM with the stock G3000, and set off for KSJC again. MSFS crashed to desktop once more, over the Santa Cruz Mountains about a third or more into the flight.
- Frustrated, I shut down the PC, restarted, and did a complete uninstall/reinstall of MSFS, without downloading the G1000 NXi from the MSFS marketplace.
- Since then, I’ve flown a couple of hours over two days — with the stock G1000 and G3000 — and with no CTDs.
Perhaps these circumstances are peculiar to my PC, or not. I simply don’t know enough to say with any certainty. But I know others have had problems with this modification.
To give you more context, here are my rig’s specs: HP Omen 25L Desktop, Intel i7-1070 CPU, 32 GB DDR RAM, Nvidia 3070 GPU, 1 TB SSD, Logitech flight yoke, throttle quadrant, rudder pedals, multi-panel, radio panel, TrackIR 5
I’m not sure if I am doing something wrong or if there is something broken with MSFS flight planning and/or autopilot. I am using the NXi in a C172 and C208. The only problem with the flight plans is with user defined waypoints. They show up in the NAVLOG and VFR MAP but are missing from the Garmin FP display. The flight plan has departure → user waypoint → destination. The Garmin shows only departure → destination. When I enable the autopilot NAV function, the aircraft heads for the destination airport ignoring the user waypoint. However, the VFR MAP shows the first leg to the user waypoint in magenta and the second leg to the destination in white.
Also I am confused about the Garmin CDI display. When the source is FMS/GPS, there is a magenta arrow pointing to the destination airport which the autopilot is using. Looking at the EXTERNAL view, the CDI displays a Magenta GPS arrow but it points to something else, possibly the user waypoint. The autopilot is not tracking to this arrow.
I understand WT is using their own flight planning. I hope that MSFS-created flight plans are compatible.
Am I doing something wrong, is this part of the Beta, or is this another MSFS SU5 ■■■■■?
Another lovely flight on the LXGB (Gibraltar) RNP 09 using the WT G1000 NXi. Including a manual 360 at BUGOV Absolute fun!
3 Likes
no, they are not particular to you. I also get CTDs with the G1000NXI. They are random when they occur, but the first flight after install is ok. the subsequent flights I get random CTDs. I have had them at TAXI, takeoff roll, and also when selecting a DIRECT on the MFD. If I uninstall the addon and reload the sim, then the CTDs go away. This is repeatable.
I’d just like to report I had two hard hangs in MSFS with this mod… Both occured at exactly the same place. Doing a GPS approach into Cairns Australia using the UPOLO eight alpha approach and when I get to the SUNNY wp (the first fix on the approach with an altitude) the sim hangs…
I tried in two different aircraft - DA62 and the C172