1.04 is the core NXi that used to be on Marketplace, but is now embedded in the sim.
0.14.0 allows Third Party Planes to use the new 1.04 NXi until their authors update their cfgs to point to the new version. Only delete it if you don’t want NXi to appear in your Third Party Planes.
Thanks. I was having trouble looking for that. Now I am not sure which planes even need that. Most of them have the pms50 750 built in or used with JayDee’s 750 mod
Every stock plane what used G1000 before has now NXi as default avionics.
Yes, I love that PMS GTN750, very good product, have it as primary on my Seneca and working perfectly. Looks like that discovered problem going to strange direction, isn’t it? 
Hope more users will report here same problem and also will report to Zendesk as Bishop sugested. Simply now only one solution, use default sim NAVBlue data if you want fly NXi, same as me. Really I can now bypass C172 but many other aircraft have also now NXi as primary avionics. My preference is B737-700, TBM930 and Seneca what are now functional with Navigraph without problems.
Hello Richard,
thank you for infos and confirmations. Really, we are all stuck now and hope something will be sorted soon. Very appreciated as also to Bishop and other users do reports and confirmations here and to Zendesk.
That´s exactly the “problem” now and it looks for longer time, when I read the answer from Matt (WorkingTitle) correctly, because he wrote yesterday (from the WT discord channel):
The dependency between the core-sim and the navdata APIs is a huge risk as we see now for all, not only for user also for 3rd party aircraft developer and of course us too. And as I wrote in my postings before, it´s not only the NXi which is effective from this bug - we have also identified an issue on the VFR map. Some navigational data can be found, some not …
As @OMICO4146 wrote - currently you can´t use 3rd party addons which uses the in-game database via the navdata API (at least with our data) because the results are unsure and it seems that a fix is far away (earliest with the next sim-update mid of November - when this sim-update comes out on time).
Cheers,
Richard
Yes,
I can remember clearly still existing bug from day one - some NAVs are sometimes missing from MFD or VFR map, with stock NAV Blue data of course. Therefore I’ve selected your product Richard, no doubts! As I can’t fly IRL now, my play with MSFS is really pure serious to have same feeling as before IRL. I\m satisfied with MSFS absolutelly although some bugs are there. No other way
That’s all correct. I have run it with no mods at all and still the same behaviour. I have installed the marketplace version, and I have no MODS using it normally.
Matt pls,
can you confirm my initial post but other bug, with keyboard hook to not have background set of sim features during insert fields in NXi FPL or ‘Direct to’ with that perfect Keyboard feature (Icon)? With my post there is this problem described by me. If I correctly remember, some versions before this was ok.
Very sry,
new bugs discovered.
with NAV1/ILS set as Bearing1 indicator, no DME is show with this indicator 1. To right DME indicator to Bearing 2 is ok with JAN VOR.
with set of Bearing 1 indicator as ADF, strangely DME is displayed but with ADF? I don’t expect DME with ADF source. On other side, this DME indication with ADF doesn’t change with flight, only after change of field to another source and back to ADF change distance again but statically.
I expect here some bugs probably. One next question, are the colors of distance purple everytime? Although if color of source is different? Hope I’m not wrong but purple indication looks to me everytime as FMC source. Just only question, really due so much changes what I test now I can have some problem with correct things.
There were two ways to load a flight plan into the G1000 NXi before SU10:
a) Load it via the MSFS user interface
b) load it via FSUIPC
While both of these methods still work on the G3000 and G3X, loading the flight plan via FSUIPC does no longer work on the G1000 since SU10.
Any ideas why?
Hi guys, I’m quite enjoying the visual approaches ever since I found out about them.
One thing though: sometimes it sets the TOD before some waypoints I want to go through before lining up the approach. When that happens, whenever I activate the approach I end up a bit below the vertical path. Any tips to prevent this?
I thought that after SU10 the marketplace NXi would disappear but it still sits there. On my XBox I installed the final update but on my PC its completely uninstalled.
Do we just ignore it? Will it get removed now that its the default G1000? Does it matter if it gets installed from the marketplace even though its already in the sim? Should it be uninstalled via the marketplace?
sorry for all the questions but I really expected it to disappear completely.
Check Content Manager and filter for NXi. It should show Installed even though it’s part of the core code now.
If you have addon planes that use the NXi, I think you still need the marketplace version until the respective developers release their updates. I still have it for the Kodiak, for example.
Yep. 0.14.0 is required for 3rdp aircraft not pointing directly at the core code NXi.
@WT:
Please implement TAWS-B within the first group and enable us to press “Inhibit TAWS”. These callouts are making me insane and they come even on final at some ICAO registered airports. Some aircraft make it possible to mute these warnings via turning off DME on the audio panel and I think there is a mute function in some suites which I am not aware off. Best would be the first option. Thanks for consideing.
Yes if you have third party aircraft that still use v0.14.0
TAWS-B is not presently implemented nor on the roadmap as the necessary terrain data is not accessible to us. The warnings you hear are not from the NXi; they are defined by the individual aircraft code in panel.xml and are not inhibitable from our end.
Thanks for the insights. So the developers including Asobo should take care of it. The Kodiak actually does have an inhibit button yet there is no keybind which is very annoying and unrealistic with a home cockpit (kills immersion when a mouse needs to be used)
