Absolutelly appreciated your effort CasualClick.
I understand to this situation… Therefore I use Navigraph for their products and support. But pls if I can say something. Due that Bishop’s news it looks like that all of devs then need implement changes because Navigraph is mostly used as mandatory nav product. really, I can’t imagine this now, also really love Bishop’s work with NXi from beginning and now it can be used only with NAVBlue sim nav data what is really shame.
What you’re seeing is expected events in a simulation landscape. Developers, whether first party like Asobo or Working Title, or third party like Navigraph, will find they need to adjust to make sure their products all work together as best possible. There are limits obviously, based on design, cost and business goals.
To that end, the fastest way to get an answer is to go to Navigraph and say “Hey, this is happening on NXi, but doesn’t happen using Navblue.” That tells them right away, there might be something Navigraph needs to investigate. Hopefully that makes sense.
Yes,
as i said before, Navigraph can implement or not that optional API probably. Again, to me is solution from inverted side of view 
If Bishop change his NXi to not use that optional API, then all other devs don’t need do nothing, hope I good understand heh hehe Ok, seriously. I don’t want to that job do Bishop but now is clear where problem lies. Everyone can say to yourself what can be better. Again, this my discovered thing affect all of us, not only me, also I expect that TermedGuitar749 probably somehow misundertanded situation because from Bishop’s info is clear that mentioned navaids are availble only from NAVBlue, not from Navigraph, with NXi only of course. Situation simply shows that some Navaids are missing from option to set them in FPL or set them in Direct TO actions although they are vissible at MFD map. Everyone can do tests and see what navaids he/she miss around, I’ve discovered my and other can find other. This is problem with no have all complete navaids available now with NXi and Navigraph.
My problem is the same as you. Here’s what I did:
Navigraph Installed:
Use C172 with WT G1000 NXi, cannot.
Use Cessna Longitude with WT G3000, can.
Use GotGravel Vertigo with WT G3X, can.
Navigraph Uninstalled:
All above, can.
So I think it might be some problems between the NXi’s newer API and the Navigraph.
Thank you for confirm that,
hope I did something helpful to Community and maybe more problems to devs now 
I have some real life aviation experience so better can swim in problematic. Hope some solutions can be prepared soon.
Just to be super clear again here:
The APIs are in the sim, and are used by avionics to request navdata from the sim. These APIs are part of the programming surface exposed by the simulator for avionics only, and there is nothing for Navigraph to “implement”, as Navigraph’s offering is data only, not programming and not avionics. The API is not the NXi’s specifically, either, it just happens to be one of the available navdata request APIs that exist in the sim.
Additionally, it doesn’t seem that everyone has this issue, and those APIs having been used by the NXi since the very first version. So it is unclear where the problem lies, exactly. But the appropriate avenue of reporting in this case is Zendesk. The NXi cannot go back to the older API as it doesn’t contain all the information that is required by the avionics.
We can then certainly, when the tickets are appropriately routed, take a look at the core simulator and, if an issue is indeed found, try to fix the problem for the next sim update.
Hi guys,
first of all - sorry, when I have something missed here and/or I haven´t understood the fully issue …
First of all THANK YOU very much to @Bishop398 … because he explained exactly the background. We offer the data the sim the API to access these data. So an API is the connector to the data behind, which can be used (could be simpler) or not, when you prefer a direct access to the data. It´s up to the dev.
Thats only because I have just read Bishop´s answer - again, thanks for that …
To the topic:
What I have understood is, that the NXi doesn´t found some data. An example was my personal area around Vienna (LOWW). An example was the WGM (Wagram) VOR … I have tried to reproduce it, and I can insert the WGM ident and get the correct VOR information back.
C172 with the G1000:
… the same with the JAN (Janovce) VOR - the G1000 NXi returns the correct values back:
… but the result is different, when I do the same in “Direct to” - no WGM (Wagram VOR):
… the same JAN example from above - no JAN VOR found:
So in my eyes the data are correct so far but the “Direct to” function (+ possible the FP function) doesn´t find the existing waypoints. I have also compared both VORs (WGM and JAN) now between our data and the stock NavBlue data. There is absolutely no significant difference - both (that what I see with my tools) are equal. Again, this is a pure view of the data - nothing more.
Further, when you look on the VFR map and you try to find WGM - nothing:
… but do you look for FMD (Fischamend) what is only a few miles away from WGM, it will be found
The silly situation here is, that both VORs are in the same BGL (stock and our data) file and has exactly the same parameter (excl. coordinates and frequency) … so, why do the sim find the FMD VOR but not the WGM VOR?
Something goes wrong here … you see, on the VFR view, the data are available (also with the Navigraph package) but can´t be searched it? Possible the new navdata API uses a special sort file or similar else, which is only generated from the stock data … that could explain, why the stock data are working but not any other 3rd party data.
Cheers,
Richard
hello all
I too seem to have the same problem, initially thought that the problem was with the 2 “two” letter identifier but apperantly reading above it is not.
if you seach on the “near VOR/NDB…” of the unit the database is actually there and correct but shows nothing on the FLP creation page as you can see from below.
I too live in the aviation world so feel free to inquire me in troubleshooting but I must admit that I am a zero on the IT tech side
regards, CS
** I think I was writing at the same time as Richard
YEP 
… but the outcome is absolutely the same … the data are there and can also be shown on different views (nearest nav list, when you enter it as single ident for information, …) but can´t be selected.
Therefore, my assumption that there is anything else happened, what we don´t know with SU10 …
… and last, the data/cycle wasn´t changed since the previous version and the current version and I know that all these examples above were working with 1.26 (without the new navdata API)
Cheers,
Richard
Well, just to stress again that it’s not really very “new” in an absolute time sense: we’ve used this API since the release of the NXi back last June. I think we added it in the sim in SU4 or SU5.
So, not really sure what is happening here.
No, no you´re right @Bishop398 … I correct it to “newer set of navdata APIs”
Which G1000 NXi manual should I use? There are so many different ones all covering different types of aircraft.
This one has been in circulation a long time even when WT started their Mod pre 1st Party days.
Edit: my memory is going. Link update to NXi, previous link was G1000 only.
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 have noticed sinds the latest G1000 update that traffic is not showing on the screens. I have enabled it, tried different planes but I see nothing. On the VFR map (from the tool bar) you do see the traffic. I am flying in VR mode.
Provide Screenshot(s)/video(s) of the issue encountered:
I’m in VR so I have no idea to make a screenshot, but it pretty self explinatory
Detailed steps to reproduce the issue encountered:
Look at your screen. Enable Traffic.
PC specs and/or peripheral set up if relevant:
Build Version # when you first started experiencing this issue:
SU10
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:
Are you at or below 50 mile radius for the G1000?
The VFR map now shows traffic out to 200 miles, whereas before su10, it was only 50 also.
I was, zoomed all the way in on the airport where there was traffic (they told me to stop, and that’s how I found out). But thanks for the help
Just to be clear-
1 You see other traffic on the ground or air.
2 Traffic shows on the VFR map.
3 Traffic does not show on the Garmin G1000 only.
Any mods installed?
Everything in content manager updated?
MSFS has been restarted since any/all updates?
Make sure you have the G1000 from the Market Place installed for use on any 3rd party a/c that use it.
( see release notes)
Got it, thank you!
Traffic that is on the ground will never be displayed, no matter the settings, and if you’re on the ground then you will not see any traffic unless you manually turn traffic off STANDBY. Once out of STANDBY, then you’ll see traffic based on the traffic setting (default is +/-2400ft of your altitude).
Oi. I am searching on here but having trouble finding an answer. I have two Nxi’s installed in my content manager…I can only delete the version 0.14.0…So I assume that I should but keep the 1.0.4 version?
