Maybe you can post a screenshot of your flight plan way-points as shown in the NXi.
If memory serves, you need to have a way-point with an altitude target/restriction for the VNAV to create a path to it, and to have that altitude show up on the PFD above the altitude tape.
I did that already too.
OK details of your flight plan, and screenshots as @BigCow74 suggested.
Okā¦
Looking back, the NXi was updated prior to AAU1, and wasnāt included in the AAU1 update (or AAU2 for that matter).
It appears they didnāt remove the RNAV/RNP approaches in the NXi like they did for the G3000. So the approaches are still listed (and apparently usable in the sim) in the NXi, although the NXi is not certified for RNAV/RNP approaches (just like the G3000 isnāt certified for RNAV/RNP approaches). Iām hoping thatās one of the things that gets updated in a SU or AAU3. But in any case, I guess as long as theyāre listed in the sim, apparently we can use them. The fact that RNAV/RNP approaches were missing in the G3000 was one of the first things people started noticing after AAU1 was released, and thatās when it was clarified the it wasnāt certified to fly those approaches, hence they werenāt available in the G3000, even though the airport charts may have shown them. So people were picking an RNAV/RNP approach in the WM when setting up a flight, and then realizing the approach wasnāt listed in the G3000 once they were in flight. Ooops. I suspect if they remove the RNAV/RNP approaches in the NXi at some future point, people will start noticing theyāre missing, just like they did with the G3000.
So I guess we can keep flying them in the NXi until thatās fixed. I never noticed them still in the sim because in my mission planning, I never selected an RNAV/RNP approach because theyāre not legal approaches for that system, even though they were listed as available on the airport charts.
Live and Learn!
Regards
I would be surprised if anyone can see the magenta VNAV target altitude on the PFD after AAU2 and am happy to see this issue mentioned in this, the main G1000 NXI topic. I have been flying without the VNAV target altitude on the PFD for many weeks now. All the Visual and RNAV approaches I use still work perfectly, but I have to refer to the flight plan to see the altitude I need to set ALT to instead of seeing that altitude displayed on the PFD like it used to do before AAU2:
No need to kill RNP approaches, if someone wants to be authentic then they can just choose not to select them.
Thank you for posting in response to my post. Iām waiting for a future update too. Now I know Iām not the only one.
Hi, I just want to correct my earlier statement. I do get VNV target altitudes on the MFD, but as you correctly stated the next altitude restriction no longer appears on the PFD altitude tape. I know the devs try to model the Garmins realistically and I am no expert but maybe the real system does not have that info on the PFD so they removed it. Perhaps they will read this and clarify the situation.
C172/G1000nxi. I create a flight plan in the world map section of MSFS. I set the altitudes also. Get in the aircraft and the G1000 flight plan doesnāt have any altitudes for the way points. I seem to remember that they used to show up in the fltpln along with the vnav profile. Did something change or am I mistaken. I use the class Echo with spad.next connection. Even if I restart without spad or class Echo enabled it does the same thing. Thank you in advance for any assistance.
So far I canāt get any vnav profile at all. I have watched numerous helpful videos but my G1000 just doesnāt perform the same as theirs. The only way I get any altitudes in my fltpln is to enter them with the cursor, even then nothing shows up in vnav profile. the only thing I can do in the vnav profile box is set the angle of descent. I am at the end of my troubleshooting ideas and my patience with the sim.
Any screenshots of your flight plan and PFD? Could be helpful.
Iām sorry, I do not know how to do a screenshot and post it here. 
Iāll go there, thanks
Also if you are on a PC you can take snapshots of specific areas of your screen, e.g. the MFD, instead of the whole display with Windows logo key+Shift+S
How to Take Screenshots on Windows 11 | Windows Learning Center (microsoft.com)
Thank you again. I will try that tomorrow.
Made progress this morning. Manually entered a fltpln from Salem to Portland with the arrival and approach/ILS. The fltpln now shows the altitudes for each point in the arrival and approach. All that looks normal. But, still nothing in the active VNAV profile. The only VNAV field it allows me to enter anything in is FPA which I entered -3.0
With the help of AviatorDown8227 I do have a screenshot of the MFD. It is saved in OneNote. How do I get it here? Sorry to be so inept, but Iām learning.
Can you show the PFD as well?
What do you have your target altitude set at? Weāll be able to see these details in the PFD screenshot.
First thing that pops into my mind is that you havenāt lowered your target altitude, which is needed in order to engage VNAV. If you donāt lower your target altitude, the avionics will prevent you from descending.
I understand about setting the altitude in the autopilot (PFD) lower than the next VNAV altitude. I flew the plane today and the VNAV did work once. then for some reason the plane didnāt follow the changes in heading at each waypoint so the GPS disconnected somehow. I did have a PFD screenshot but I canāt find it now. Iāll recreate the flight plan and take another screenshot of the PFD. Donāt know where it went.
I have discovered that using the world map create a fltpln is not at all what works right for me. Iām getting closer to resolution, Iāll manually enter another fltpln and fly it to see how it goes.
