Thank you very much WT for the G1000 nxi. I used it quite a lot in the last time and I love the new Garmin.
I’ve updated the G1000 nxi to version 0.2.0 and I’m experience a FS freeze every time I try to fly an RNAV approach.
I’ve tested on the Cessna 208 and Baron G58.
There is no CTD but the sim freezes. (LPV approach was working fine in v0.1.0)
Is there anyone experiencing the same problem?
Is it a known issue?
Thanks a lot.
Does it freeze if you fly the exact same flight plan with the stock Cessna 172 with the NXi addon?
Hi all,
Thanks to everyone’s help here and on our Discord, we’ve managed to reproduce the freeze and should have a fix coming (for that cause, anyway) in the next release. There was an error in some TOD waypoint placement and bearing normalization code that was causing an infinite loop in certain conditions.
-Matt | Working Title
6 Likes
I’ve just tested it with the Cessna 172 (G1000) with the same result.
I’ve made a test flight with the C172 from EDQC to EDQC with RNAV 30 LONLI transition, if you also want to give it a try.
The deep frozen Sim always happens then. 
Happy that WT has already found the error. 
Any ideas about the issue I posted about?
Unfortunately, no. Because the NXi is a Javascript instrument, it should not be possible for it to crash the simulator, just as Javascript bugs do not crash a web browser. There may be another sim bug here at play, though.
-Matt | Working Title
2 Likes
OK. Am I alone in this or have you seen other reports similar? I couldn’t have a cleaner, fresher install than I do.
We have received other CTD reports but it’s been hard to separate them from random CTDs. Nonetheless, we’re keeping an eye out, even though there might not be much to be done at the moment if a previously unseen sim bug is the cause.
-Matt | Working Title
3 Likes
I got a flight plan in but was confused because usually the default first way point is the airport I am starting from. Then I would just enter the flight plan with the destination the last way point. The text with the underline is what confused me.
Destination
Origin, Enroute, Destination are just headers that will also show the procedure information when selected.
The rows below and in between those headers are your flightplan legs.
“_____” are empty rows you highlight and turn the inner knob to add a leg there.
Can confirm that CTDs only occur on my PC with the NXi installed. Haven’t had a CTD since I removed it. This is not a random CTD, since I don’t get CTDs on my system. The only other CTD I have ever hyad is when I unlugged my mouse receiver, a bug Asobo said they had fixed. While I appreciate that the NXi shouldn’t be able to cause CTDs as it Javascript, I only ever get CTDs with the NXi installed. So if it is not triggering the CTD itself, it is influencing other parts of the MSFS that then result in a CTD. Have other mods like the DA62X and DA40 NGX installed, but CTDs can occur with any G1000 aircraft. As reported by other users it intially works fine after the 1st install, but then CTDs occur on subsequent loads of MSFS.
1 Like
I’ve been flying more glass cockpit flights this past week than I have all year. The NXi is a fabulous addition, and has made some aircraft (the Baron comes to mind) that I had quit flying attractive again.
I am currently flying the 208 - an aircraft I have largely ignored - and it’s really quite fun to fly RNAV approaches with the NXi installed.
I prepped my system for SU5 by removing (uninstalling) everything related to MSFS. I installed SU5 from scratch. I reinstalled add-on aircraft and scenery as updates became available (thanks PMDG!) and still have a number of third-party add-ons “out of service.”
My experience has been very good… a solid B+ I’d say.
Thanks Matt and the team at Working Title. You’ve done yeoman’s work!
Can you load pre-made flight plans into the G1000 NXi say from little Navmap. I seem to be able load them into the world map and then once in the sim it only shows departure airport and destination airport all my waypoints are missing in between.
Same still for me also. I just tried again, after the HF2 install. Same results. It causes the CTDs. I really like it, when it works.
BTW, the only world updates I have installed is the USA update, since I rarely fly in the other WU places. Don’t think that would matter, but I mention it just in case.
If you can, use the Windows Event Viewer to save the crash dumps and send them to ZenDesk so Asobo can try to track down those crashing parts of MSFS.
Can I have the NXI and G3000 from WT Installed without issues? I just have to remove the WT G1000 right?
Do I also have to remove the PMS Mods too?
I have asked this before, but I am confused?
I tried out the new G1000 NXi from the market place. It’s cool and some of the new features are nice and all, but the numbers and lettering are just too small for me to see now compared to the default. I don’t suppose there is way to scale that is there?
Noted your problem with the MFD zoom. I had the same problem and found the solution for me. I had the Tiny Taxi Ribbon installed, I removed the file and the problem went away.
Thanks for the update but I don’t have that mod installed.
Mod edit: Moved from duplicate thread
Working Title has enabled VNAV approaches in the G1000 NXi, but in the process, ILS approaches have somehow been lost. I’ve tried several times to fly ILS approaches in the Beech G36 since the G1000 NXi became the default Garmin in the G36 and numerous other aircraft in MSFS 2020 with Sim Update 5, without success. I’m not doing anything differently than I did with the plain-vanilla G1000. Before takeoff, I enter the destination ILS runway’s LOC frequency into NAV1 and make it the active frequency; I go to the MFD’s PROC screen to set up the ILS approach and load it for activation later. After takeoff, I engage the autopilot (for an IFR flight plan). All works as it should until I get to the ILS approach’s final-fix intersection (the one with the maltese cross and the little lightning bolt).
Then things go haywire with the G1000 NXi. This is when I mouse-click the CDI softkey in the PFD to switch from GPS to the localizer. Pre-Garmin NXi, doing this would replace the magenta arrow with a green localizer arrow that would be oriented straight-up, 6 o’clock to 12 o’clock–just like the magenta GPS it replaced–on the final approach heading to the target runway. Pre-NXi, I would hit the autopilot’s APR button at this point, the AP would capture the glideslope, and the plane would follow it in. But in the new Working Title G1000 NXi, clicking the CDI key brings up a locator arrow pointing 90 degrees to the left of the runway heading – every time. The only way to land the plane after this is to disengage the autopilot and hand-fly it the rest of the way.
Working Title’s G3000 NXi is still apparently a work in progress. I hope WT works this kink out of the NXi soon.