Is this a behavior you can reproduce on the NXi? Certainly the stock flight plan system based units will do this (currently), but this should definitely not happen on the NXi. After reaching the fix on the approach, sequencing will continue on as normal.
We nor SWS are aware of any incompatibilities at this time.
There are the two outstanding CTD issues identified in a post above, but neither are related to the Kodiak (although some users report hitting them more often in the Kodiak, as they are timing issues in the sim, so are sensitive to what is loaded, even if the NXi nor the Kodiak are the causative problem themselves).
Last time I tried was quite a while ago so it is very possible that it’s a non issue now.
I just had another flight where I needed the Direct To you mentioned earlier. It worked beautifully.
The stock G1000 needs to go away, lol. But I’m sure there will be tons of confusion when it does.
1 Like
One silly bug I noticed … it is now 24:25:00 UTC in the PFD!!
Good spot. I have that also 
I feel like we need a whole primary category for the NXi or navigation systems! This stuff is way harder to learn than basic flight.
Anyway, my next struggle is VNAV on the visual approach. Mostly of the time the AP seems to hold the prior altitude and doesn’t descend after I activate the leg or do a direct to.
My guess is the v navigation profile has been exceeded?
Also straight vs. vector?
1 Like
Make sure you set your target altitude before arming VNAV. If you don’t set your target altitude below your current altitude, it will never start to descend. This was my first (of many) mistakes.
2 Likes
It’s set below. I’ll often set to 300 agl. Everything looks armed and all but sometimes it doesn’t take the path.
I could also be used to making my approaches too shallow? I have to one of these times let it run a little further and see what happens.
Indeed. The forum will flooded by angry posts complaining that the G1000-equipped planes no longer turn to follow the flight plan when the NAV button is pressed. 
1 Like
Yeah I am sure, Nav not intercepting the course was the first thing that caught me out with this version.
2 Likes
I could see a need for “Legacy G1000” mode in the options.
I see confusion in pilot forums with these systems too. It can be hard to tell if you are reading MSFS, X Plane or any pilots’ web site. Although in real life a pilot is not likely to jump in cold and learn the system in flight.
If I had to hazard a guess, I would say a large percentage of the base (now with the console) just wants to start up with engines running and take off.
Of course they’re going to turn to the forums and blast away, but hopefully we can help steer them in the right direction. (Lol, pun unintended!)
Hi all, I have a question for the experts among you 
.
I set the NAV2 radio to the Aalborg VOR in Denmark, and I pressed the CDI button until I could see it on the PFD and I was tracking VOR2 correctly, but the icon still said VOR1.
The VOR needle did change shape, but it always said VOR1.
Am I doing something wrong here?
So VOR2 was selected in CDI?
I’ve strictly done GPS but I can try doing VOR later and see.
This what I think is happening. VOR 1 and 2 on the PFD don’t relate to Nav1 or Nav2 necessarily. You can be tuned to one localiser either on Nav 1 or Nav 2 and VOR 1 will be displayed regardless of which Nav radio you are using. if were tuned into two separate localisers at the same time though, then you would see VOR1 and VOR2 displaying info from the two localisers independently.
That doesn’t really make sense and seems like a bug. I guess we ought to check the real G1000nxi manual to be sure.
Hello, I have tried this on a few visual approaches and as far as I can tell, it does not follow a glideslope down to the runway. It levels off at the FAF altitude for me. In fact often when I click APPR from NAV, it switches from gps to a vor CDI source for the nav, and I have to keep switching back to get to gps, but it still never follows a glide slope. Am I missing something? Thanks!
Ok so according to the manual “Setting a Nav Radio” VOR1 should be used when Nav1 is tuned in as the nav mode and VOR2 should be used when Nav2 is tuned in as the nav mode. So you may be right, it may not be working as it should.
RNAV = GPS; ILS = VLOC. VLOC gets you the Localizer, followed by “APPR” before the FAF to capture the Glideslope (“GS”).
If RNAV, stay with GPS, but activate “APPR” before the FAF. That will capture the Glidepath (“GP”).
(IMHO)