I’m always so gunshy posting here, thinking I’m the problem, not the G1000…
Anyhow, I just took off from KHWD with no flight plan. I selected the NRST page and then Nearest Intersections.
I notice there are a number of duplicate intersection entries. Is this expected behavior?
Examples:
ROGGE 2x
YEGGU 2x
SEPDY 2x
(Man, this G1000 is seriously fun to “play” with. Such cool functionality. Again, thank you MS & WT!)
The developers know what is going on. They don’t need a screenshot from me. I am simply asking for the devs to please add a way to disable that thick white border on displays when pointing the camera at them with a Xbox controller on PC. A workaround has been provided in this topic already but it is nowhere close to ideal. It involves remapping two gamepad buttons but it doesn’t really solve the issue. Thank you for your interest.
Yes, I did too.
On the stock G1000 I usually do not get the speed into the yellow bar (when cruising), but with the NXI I have to watch that.
Hi there. I am having problems with the key binding in MSFS 2020 in the G1000 Nxi. When I press Autopilot On (Alt + Z) through the keyboard, I get no response from the status display in the G1000. If I press the button on the G1000 for Autopilot ,it comes on in teh status display. When I press Autopilot off (Shift +Alt + Z) through the keyboard, the Autopilot on the display in the G1000 does turn off in the display. Is there a problem with the key bindings to the Autopilot in MSFS 2020 or in the G1000Nxi? Thanks 
Do you have both the stock G1000 and the G1000NXi installed? As reported lots of times in this thread, this causes conflict and problems. WT specifically say that you should delete the stock and just continue with the NXi. Remove the stock G1000 which will probably solve your problem.
The stock G1000 needs to be deleted?
That’s interesting. I downloaded the NXi using the in-game content manager and I didn’t read anything about deleting the stock G1000. However in my case the stock G1000 doesn’t have the thick white border issue I’m trying to solve with this mod. I’ll look into this further.
I think instead of stock G1000 people mean if you have the G1000 from the WT from git hub, which is obsolete.
Agreed, that’s the info I found as well. Thanks. (I didn’t have the github version installed, just the one from the content manager.)
The G1000 NXi acts as a touchscreen in MSFS in order to take input focus, allowing you to use keyboard input.
This is specific to X-Box, from what I’ve read over the last several months in this thread.
This is not an issue we can solve. All touchscreen panels will show this (such as the G3000 and the G3X Touch) as this is part of the sim display. Since we require mouse control in order to have the keyboard focus feature (where you can click on the keyboard icon or waypoint input area to allow the keyboard to fill the field), we will not be removing the touchscreen capability from the NXi.
If you feel the white border is distracting, your best bet would be a forum feature request to get votes on, or a request to Zendesk to let the MSFS team know.
Because the NXi is just a Javascript instrument, it cannot change the flight model of individual planes. It would therefore be impossible for plane performance to change due to the NXI being installed.
Thanks for your reply. As noted by others below, I don’t understand how you get rid of the “stock” G1000. Just so you know, I have run this with the G1000 NXi as well as with it removed from the sim (i.e., stock g1000 in place only) and I get the same problem. I am totally baffled by this. Does anyone else have this problem using the keyboard commands?
Thank you kindly for your reply and information. I thought you might have better access to the official game developers. If you do, please let them know that several PC users want the white borders to go away (or at least make it an option to disable). All other methods to get this issue resolved have failed for us. Thank you and have a great day.
You don’t. All you need to do is “buy” and install the NXi. Simple as that.
The one you may need to remove, if applicable, is the “old” WT G1000 mod which you would download externally and place in your Community folder. The marketplace G1000 NXi replaces that mod and they’re incompatible.
HethrMasn,
This may or may not help you, but I faced the same problem when trying to use the D-pad on my Xbox controller to view Instrument 1, Instrument 2, etc. (NOT the analog joystick). Btw, I’m running on a PC - I added the controller for cockpit views as well as drone/external views.
I downloaded a utility named JoyToKey, which allows mapping of functions to multiple joysticks/controllers. For cockpit Instrument 1 ( the PFD in the Cessna, for example), I programmed it so that UP on the D-pad sends CTRL + 1 to view Instrument 1, RIGHT on the D-Pad sends CTRL + 2 to view Instrument panel 2 (the passenger MFC), etc.) This works very well.
When I tried to assign these keystrokes directly to the Xbox controller via MSFS, I got the white border. This utility fixed my problem.
Hope this helps as a workaround.
Best,
Bill
Thanks Bill. I did see your workaround. I seem to have quite a different play-style than you. I use free-look to look around inside the cockpit (also zoom in/out and translate my position inside the cockpit), so I rarely use the dedicated instrument camera views. Thanks a lot though!
In case it hasn’t already been mentioned, in my testing of SU8 it appears that the update 8 breaks NXI.
Yes, it was still installed in content manager and up to date, but it just doesn’t seem to take effect.
What I see is the main issue that the stock G1000/3000 code has , which NXI fixes: on approach, when you are assigned an approach and you select and activate it, the aircraft will try to go the wrong way than the correct course. It seems to be that “magic/invisible” waypoint insertion which the stock code does and which NXI fixes.
I know they changed a lot of stuff from an SDK perspective, so perhaps that is impacting NXI.
It is working (like it always has) here?
Same here - have not noticed any changed NXI behaviour between SU7+ & SU8 Beta