Yes, installing that NXI addon should not cause any conflicts for any planes that use the NXI without needing that NXI addon. The NXI addon just helps planes that do not “know” that the NXI is now the default G1000 to find and use the NXI.
1 Like
I have downloaded and installed the NXI G1000. I am trying to use VNAV for VFR flights for pattern entry. After pressing direct to, I choose airport but cannot scroll over the altitude to input the pattern altitude. Anyone get the VNAV working for VFR traffic patterns? I’ve watched tutorials on YouTube that show it working.
1 Like
Coupled VNAV (AP guides down automatically) only works on selecting Approaches (either instrument or visual).
Thanks, watched a YouTube tutorial and he was able to go “direct to” set the pattern altitude and then distance from the airport. Not working for me, so I don’t what’s up.
It’s a 2 step procedure.
- Enter airport for Direct-To
save (Or if you have already filled in the Departure and Destination it will already know the DEST) - Using the procedures button choose approach
fill in your your runway and transition etc and
Save
1 Like
When I use the physical PC keyboard to enter waypoint names etc, is there a keyboard shortcut to enter that mode?
I find the TINY little symbol I have to hit with the mouse to be almost impossible to hit, especially when wearing a head tracker or in turbulence.
It seems entirely unnecessarily tiny, and indeed the accepted hit area is much smaller than the graphic button shown.
It would be eons quicker if there was a shortcut key on the physical keyboard which entered that mode.
Tip: You can also activate it by clicking on the place where you enter the text. Maybe a little bit easier to grab. 
1 Like
Aha. So you can. I had tried that, but it turns out you have to click on it twice to activate the keyboard, so I had missed it.
Would be nice if they added a key shortcut too.
Thanks.
1 Like
Unfortunately, we cannot make a key shortcut, as there is no event in the sim for entering this mode.
2 Likes
Our direct-to menu does not presently have the altitude or offset fields enabled.
Presently Along-Track Offset is not implemented, but you can assign your destination an altitude by using the MFD FPL page.
1 Like
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
Yes
Brief description of the issue:
I tried entering a flight plan into the G1000 in a 182 and a Cirrus. The course was to be KVLL MIGGY2 via MIGGY then to KMCD (I believe its VLL, JAXII, MIGGY). When entering the departure in the G1000 it seemed to recognize the routing and accepted the plan. Initially the GPS magenta line displays a direct route from VLL to MCD with no routing. At this point anything else I do to change the route including trying to change it to direct MCD results in the magenta line disappearing and the GPS being useless thereafter. The only way to restore GPS functionality is to exit the flight to the main menu and reload. I should note that while the GPS loads the departure procedure waypoints, there are no bearings associated with them in the list.
Provide Screenshot(s)/video(s) of the issue encountered:
Imagine a G1000 screen GPS with a waypoint set and no magenta line.
Detailed steps to reproduce the issue encountered:
Enter G1000 flight plan Departure KVLL runway 28, Destination KMCD. Click the procedure button and choose the MIGGY2 departure via MIGGY then load. The GPS magenta line will display direct to MCD. Try to edit the flight plan or change to direct to MCD and the magenta line disappears. The GPS is useless after that.
PC specs and/or peripheral set up if relevant:
Specs not in front of me, More than adequate. This is a VR gaming rig. If you find a previous report from me, I believe those specs are in it.
Build Version # when you first started experiencing this issue:
Most recent update, I do not have the exact info with me.
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video:
Moved to G1000 master thread. Bug reports only for verifiable and peer reviewed defects. Seek help in #self-service subforums first. Thanks.
Thanks for the info. I realized the YouTuber switched to the Garmin simulator to demonstrate the VFR approach.
Unfortunately, I am unable to reproduce this. This is my result after following your reproduction steps:
Do you have any additional steps you’re performing that you don’t have listed, possibly?
1 Like
Is this something which can be requested from Asobo for the future? Perhaps you have already done this for all bottons etc in your Garmin emulations?
Hello, I’m not sure I am in the correct forum to ask this question but let’s try.
With the WT G1000nxi implementation, in the flight plan for example you can press with the mouse cursor the small keyboard icon next to the dashed fields to enter directly via keystrokes the airports or waypoint codes you want, it is really easier than turning the knob to get to the desired letter. Cool function.
I have a hardware Garmin GCU475 Controller unit managed via serial by a C# small form app, I can send any command to the G1000nxi so far regarding the buttons, except I’m stuck at using the keyboard function to enter the airports code directly. Basically, I use a line code like
FSUIPCConnection.SendKeyToFS(keyStroke);
to send the keystroke to FS. But when I’m in “keyboard input mode” with the keyboard icon highlighted in the WT G1000nxi the keystroke will not be “A” as expected, it will be “&A”, any stroke sent is preceded by “&” in the unit.
So I was wondering how was implemented the direct keyboard input in the WT G1000nxi because there might be something added to keep the keystroke in the G1000 scope and prevent it to spread to MSFS. This trick might cause the “&A”, “&B” I see when sending keystroke programmatically.
Hopefully there is a workaround to get it to work with hardware (by the way, if possible, add a functionality to programmatically switch on “keyboard input mode” instead of relying to a mouse click, for cockpit builders).
If anyone has a clue, thanks in advance.
I might also post this in cockpit builder forum.
There’s not much control on the instrument side. It simply sends a command to the sim that says “this input field is now active” and the sim does everything else. So, I’m not sure where the & would be coming from, but the sim must be interpreting your input in that way to send us those characters.
I apologize if this has been asked before or if this is a newbie question. Is there any way to set an alert when I arrive at x distance to my destination?
I’m still very new to all this (really) and have been calculating my TOD manually, and changing my altitude/vs to follow a proper glide slope during descent.
I’d like to have some audible or on screen warning when I reach a point on my course. Not sure about my methods here but I’ll learn better ways in due time. LOL
Any guidance would be appreciated.
Thank you for taking time to answer my question. So the “trick” part must be from FSUIPC command side
FSUIPCConnection.SendKeyToFS(keyStroke);
I may use a more conventional native windows key send command, will update if I find a solution.
Oh…by the way, do you know if there is a way to trigger the “keyboard input mode” in the WT G1000 by other mean than a mouse click ? Maybe an accessible event like the others buttons ? I did not find it in the mobiflight event list.
Scroll up a couple of posts and I think you will find your answer
1 Like