Hmm. I’ve been successful in the Caravan with both ILS and RNAV approach. I’ll try again later as maybe mine was before the latest hotfix.
1 Like
Causes all sorts of CTDs with the FBW A 320 dev
You need to manually set the CDI to the published ILS localizer course shown on the approach chart - it won’t automatically do it for you. The Garmin G1000s and G3000s in the default aircraft all do set the localizer course automatically based on the course stored in the nav database, This may be an option on the real Garmin units, and may simply be a missing feature in the current NXi version, but you need to be prepared to set the course manually.
Even if the CDI is rotated 90 degrees, the autopilot will still capture and fly the localizer. Setting the CDI to the published localizer course will give you the correct “sight picture” of the localizer’s position in relation to your current heading, but the autopilot does not depend on that when flying an ILS.
3 Likes
Minimums callout doesn’t work on NXi only 1000ft to go alert.
I’m having problems flying multiple legs. Basically I set it up (usually with the world map planner), fly that leg, delete flight plan. However at this point (whether I’ve deleted the plan or kept the old one) I can’t change the origin or destination airports; I move over those fields with the large/outer knob, but turning the inner does nothing.
I can usually change the “enroute” field however, which makes for one hacky extra leg using “direct to”.
After having done that, it seems the enroute field also cannot be changed again.
I’m guessing this is a bug and not how it actually works? Is this a known issue, and if not, should I report it somewhere other than here?
Exiting to main menu and setting up a new flight is far less immersive than staying in the plane. 
EDIT: I updated to 0.2.0 – I wish the sim would tell you there are updates every time, not sometimes.
Haven’t tested the above again since updating, but I did run in to this:
Not sure exactly how that happened, but it seems it was triggered when I pressed numpad 0, which is mapped to the default view (“RESET COCKPIT VIEW”) while mucking around with the MFD/right display.
I can’t seem to get it to change from that view now; FPL button does nothing, CLR does nothing, holding CLR does nothing.
It hasn’t frozen though, I can hit direct to for example.
EDIT 2: Hm, I seem to be having many issues with 0.2.0. The autopilot did a right 360 instead of a left turn into an ILS approach; prior to that it did a constant 360 until I went “direct to” the next waypoint. It also showed 0.0 nm instead of the ~40 nm that actually remained.
In the next flight, I set the altitude to 4000 ft and V/S 600 fpm, but it eventually crossed 4000 and kept climbing. I raised the altitude to 5000, but it kept climbing through that as well. Had to hit the ALT key to make it actually stay at the current altitude.
Thanks for your reply.
Does manually “setting the CDI to the published ILS localizer course” involve setting the PFD heading bug to the ILS LOC heading? And even if I don’t do this, you’re saying it still doesn’t matter if the CDI needle – having been switched from GPS to LOC – looks like it’s pointing 90 degrees off course? The AP will follow the LOC’s glideslope to the runway anyway? I’ll test it today on an approach to KSJC and see where my plane ends up, but even if it continues to the runway, I think the mis-orientation of the CDI LOC needle is a bug that needs fixing.
I think lots of folks have been flying only glass cockpits where this is normally a thing, which is understandible.
A localizer antenna carries with it no course information at all. Before the glass cockpit days, steam gauge CDIs did not automatically slew to the correct ILS course, because there was no radio information that gave them that course. However, just like the old manual CDI days, it does not matter at all which direction the needle is pointed: that’s for pilot information. You can point the CDI 180 degrees completely backwards from the course and it will still be flown by the autopilot all the way down, because it flies the antenna signal. A localizer is not like a VOR in this way.
At the moment, we do not have auto-slew of the CDI implemented. In the Garmins, when you tune a LOC or ILS, it will look up the course in its nav database and initially slew the CDI needle to the database course. This is not required to fly the ILS properly, but does give the right picture to the pilot. We will be implementing CDI auto-slewing, but just haven’t yet.
-Matt | Working Title
4 Likes
Matt, thanks for your response. My experience with the “old” stock G1000 was that when I switched the PFD from the GPS “needle” to the green LOC needle, the LOC needle always lined up with the runway heading, and that – having made the runway LOC frequency the active NAV1 frequency – when I activated “APR” on my autopilot (through my Logitech multipanel), the plane would capture the glideslope and commence descending per the same. It worked every time.
Today, I flew a short hop from Watsonville (KWVI) to Monterey (KMRY) with an ILS approach to RWY 10R. I’d entered and activated the LOC frequency (110.7) into NAV1 and loaded the approach into the MFD prior to takeoff. I took off and activated the autopilot. When I reached the approach intersection with the LOC fix (MINCK), I switched the PFD needle from GPS to LOC. The LOC needle came up pointing at a heading 90 degrees off the runway heading. Acting on advice that this didn’t matter, I did not intervene. The G36 I was “flying” banked sharply to the right. The autopilot was clearly NOT going to make the runway on this heading. So I switched the PDF back to the GPS needle, canceled the AP, got back on course manually and hand-flew the rest of the way in. IMHO, and based on my experience with the stock G1000 vs. the G1000 NXi, the latter is not working the way it should.
2 Likes
The few times I could use the NXi without a CTD, my experience was the same with an ILS approach. I am using Navigraph data, if that makes a difference.
Agreed. I haven’t been able to successfully get the C208 or 172 to correctly fly any localizer frequency. In fact, when I leave the AP alone, the planes eventually fly 180 degrees in the OPPOSITE direction.
1 Like
To be clear, I’m not suggesting ILS doesn’t have bugs. However, the CDI pointing in the wrong direction is not related to the way the plane flies an ILS. So, just want to keep those two issues separated, because they are.
-Matt | Working Title
The control is the CRS knob, which is on the right side of the PFD. It is a dual knob. The outer ring sets the CDI needle, and the inner sets the altimeter pressure.
Thanks. I can use the heading selector knob on my Logitech multipanel, which does the same thing as the CRS knob in the sim, minus the baro pressure. I haven’t used it much to date, but I did today to dial in the heading setting for RWY 10R (98 degrees) at Monterey. Of course, that went out the window when the G36’s autopilot started following the LOC needle off course on final.
I’ve had one CTD that I think I can fairly blame on the NXi. At the start of a flight in the G36 yesterday, the NXi MFD map screen’s background was black instead of green and blue the way it should’ve been. I took off with it like that, and activated the autopilot. MSFS CTD’d when I tried to change an autopilot setting (on my Logitech multipanel). I assume some kind of conflict between the multipanel and NXi crashed the sim (as opposed to the plane). What it was, I don’t have a clue, of course. But the NXi returned to normal (green/blue MFD map screen) after I restarted my PC and launched MSFS again, and I didn’t have another CTD after that.
Read my post above and you will see my experience. They say it is javascript controlled. I wonder if I need a file or files to get JS to play nicely on my PC. I dunno. I do not think I am the only one seeing this though. It may be sorted out in future releases…I dunno.
Does the G1000 GTX get updated via Market Place. just wondering. One issue when I load an approach and just want to load it only, it activates it and changes the planes flight path.
I haven’t quite got the hang of it yet but when I switch from GPS to Nav1 (where the ILS is tuned) with the CDI button, it also seems to flip the AP from the current NAV to ROL/PIT mode. I have to press NAV to get it to switch back.
This is correct behavior. The real unit will also revert to ROL mode when the CDI is changed, so you don’t immediately start navigating towards the source if you still needed to set up the course (for VORs for example). You must re-arm NAV mode to resume.
-Matt | Working Title
3 Likes
I am convinced that the G1000 NXi crashed my sim this afternoon. I was trying to replicate a YouTube tutorial on how to fly an RNAV course with a VNAV final approach – in a Cessna Caravan flying from Albany, NY to Manchester NH. I set up the flight plan in the World Map and proceeded to the cockpit, where I saw that the MFD map screen had a black background–instead of the blue/green background it should have had. I’d previously experienced a CTD after taking off with the G1000 NXi MFD map screen in the same state. So instead of taking off, I exited MSFS, restarted my PC and tried again, going back to the World Map, “filing” the flight plan, etc. This time, I could not get to Cessna’s cockpit ; I could not even get to “ready to fly.” The sim CTD’d on “Fly.” This happened again after another PC restart, return to the World Map, and flight plan filing. The third time I restarted my PC, I filed the same flight plan again, and chose a different plane, the Daher TBM 930 with the stock G3000 instead of the Cessna Caravan with the G1000 NXi. This time, I was able to get into the TBM’s cockpit and take off. By process of elimination–the elimination of the G1000 NXi as a factor in this flight, I have to conclude that the G1000 NXi was the culprit in the CTDs I experienced today.
Why the stock G3000 in my Daher? I recently removed the Working Title G3000 mod from my community folder because I suspected it was causing CTDs on “Fly” after I installed Sim Update 5. (I had no problems with it prior to Sim Update 5.) Removing the G3000 mod seemed to resolve those CTDs. Ironically (or not), MSFS still mysteriously crashed to desktop this afternoon about two thirds of the way from Albany to an ILS landing at Manchester. I was really put out by this because I’d been flying in some very dynamic live weather. I have now resorted to a frustrated simmer’s ultimate solution: a complete uninstall and reinstall of MSFS 2020 — I think this my third reinstall since Sim Update 5, but who’s counting?
The NXI causes CTD for me as well when you leave the world map too. It flies fine for the first flight after install, but subsequent attempts CTD.
Many other people do not seem to have this problem.
I am afraid that reinstalling MSFS will not help you, because I am on a complete fresh Win 10 install and a complete fresh MSFS install.