![]() I then manually descended to 1700, hit APR, but again, it did not turn on, BUT this time, the GS annunciator turned green, and the autopilot descended like it should. Then set the altitude to 1700 to “give it permission” to descend to FAF altitude once it hit TOD after ZEBED. 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.Second time, I used VNAV after reaching 2600 feet before ZEBED. An example was my personal area around Vienna (LOWW). What I have understood is, that the NXi doesn´t found some data. Thats only because I have just read Bishop´s answer - again, thanks for that … 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. We offer the data the sim the API to access these data. 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.įirst of all THANK YOU very much to … because he explained exactly the background. ![]() The NXi cannot go back to the older API as it doesn’t contain all the information that is required by the avionics. But the appropriate avenue of reporting in this case is Zendesk. So it is unclear where the problem lies, exactly. 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.Īdditionally, it doesn’t seem that everyone has this issue, and those APIs having been used by the NXi since the very first version. 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 APIs are in the sim, and are used by avionics to request navdata from the sim. This is problem with no have all complete navaids available now with NXi and Navigraph. Everyone can do tests and see what navaids he/she miss around, I’ve discovered my and other can find other. 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. 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. Everyone can say to yourself what can be better. I don’t want to that job do Bishop but now is clear where problem lies. ![]() 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. But when this problem will be sorted, I don’t know heh This is democracy…Īs i said before, Navigraph can implement or not that optional API probably. ![]() Ok, what can I do? hmmm now I think that I have some backup with old NXi version that can solve some situation, will try find and play with that (I’m afraid that due SU10 that old versions will not work heh) or leave all NXi aircraft in hangar and use other aircarfts, my priority is use Navigraph. haha this is somehow really funny with this sim haha Very apreciated Bishop’s description of situation, no problem but if each other of devs not implemented that APIs, only NXi will have still problems. NXi use new sim API what other products (Navigraph, PMDG,G3000,GTN750,…) looks like not still use so here is the problem Somehow I can say that this is some big chaos now but except NXi, all is working correctly but is not Bishop’s problem. As I said already in my previous posts up there, with NAV Blue looks like all is ok but Bishop described now where is problem but that also means how all devs cooperate between each other.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |