Why does map zoom in/out with mouse scroll wheel work in opposite sense in the vfr map and the Nxi?
This is slack and irritates my cat 
1 Like
One important thing to keep in mind is that VNAV works on barometric altimeter (which is not generally perfect, and may have errors due to non-ISA pressures or just due to not being perfectly calibrated) whereas approach modes are working on GPS altitude. It is oftentimes the case that these two altitudes may not be exactly coincident with each other, and that’s perfectly normal.
The other reason to end up below the path, if this is further down along the glidepath, is that you don’t have enough power in for the autopilot to keep you on the path at a reasonable angle of attack. Adding a bit of power back will keep your speed the same but will allow the AP to correct.
2 Likes
Thanks for the tips guys. I think I found that if I set the AP altitude just above the FAF (instead of just below), the plane stays on the vertical path. This is all with the Kodiak, I will try other planes some other time.
Just downloaded the latest nvidia driver, hoping to clear up the nxi with DLSS on. As I accelerated down the runway, the ones digit on the ASI was very blurry, not a clear scroll that you get with TAA.
1 Like
Since SU10 I’m no longer able to load a flight plan from AivlaSoft EFB V2 to G1000 equipped aircraft. I believe AivlaSoft EFB V2 also uses FSUIPC.
There is a huge confirmed bug in the new navdata API from WorkingTitle in combination with the new loading system from Asobo.
It looks like we must wait till SU11 to get a fix (or possible later). There is currenly no official statement about the fix, only the confirmation that it’s a bug.
Cheers
Richard
3 Likes
Can you explain how the bug manifests itself to the player?
In other words, what can we expect to encounter because of the bug?
Thanks.
1 Like
I’d have to re-rest in the 1000, but in the 750 if I load any flightplan into the map screen which has a custom waypoint, the custom ones are removed, and a single waypoint at the North Pole is added.
If I load the plan directly into the 750 while spawned, then it loads correctly.
I found I was unable to load a NAV plan from CYVR to CYBD low IRF.
KPDX to KFHR ok
KFHR to CYVR ok
CYVR to CYBD nope
CYBD to CYLW ok
I have a fully updated system.
My guess is there is an issue someplace in the Canada update. just a guess since I don’t have any inside info.
dw
Any chance you could get this information bannered or otherwise highlighted?
Regards
Hi guys,
When you scroll up, you also find your answer in this posting (a few days before). Also I guess, that the WT-guys can be explain this much more better than I, and honestly they should inform about it than I … so please, excuse when I can only explain the result of this bug and not the why that happens … but here a short summary to this issue:
First of all, this issue are only with our (Navigraph) data and ONLY with the new NXi, which uses new navdata APIs since SU10. Also, all 3rd party addons which possible use the NXi or this new navdata APIs from WT are effected.
Now the problem:
The search result in the new NXi, or in the VFR map search is not complete. According WT (from their discord-channel), is this an issue that surfaced with overlapping navdata and facility searches.
Here the reference from the WT discord channel to this:
As an example, when you want to fly a “Direct-To” in the NXi and you´re looking for a waypoint, the result is not complete and the NXi returns possible “no waypoint”. The same, when you´re trying to search waypoints and/or navaids in the VFR map … included, you see it on the map but the result is empty (sometimes).
In this link here, I have explained in very detail the issue (incl. screenshots):
As you see, the data are included, but the new navdata APIs returns not always the correct results due this bug. Again, this is effected only in the NXi and all 3rd party addons which uses the NXi and/or this new navdata APIs from WT. The normal sim, all other 3rd party addons are working as expected …
Sadly, we have no information when this will be fixed. There is no timeline therefore and we (Navigraph) can´t do nothing till this is solved by WT and/or Asobo.
WT announced this fix earliest with SU11, but haven´t confirmed it … so it can be later too, what is very bad for every Navigraph user because we can´t recommend to use the new NXi and also for every 3rd party developer, not to implement the new navdata APIs till this fix is out without loosing the usage of the Navigraph data.
Cheers,
Richard
6 Likes
Thanks so much for the information and links.
Regards
1 Like
I love seeing other players on TCAS, not just AI aircraft. Thanks WT!
Just again, for clarity, the NXi has used this same navdata API since SU4.
The issue is arising due to some facility data index code that predates MSFS 2020, which previously did not surface as an issue prior to SU10 as it was possible to prevent the fs-base-navdata package from being loaded completely, which prevented its data from entering the facility ident index. It turns out that the facility ident index is not aware of any of the facility deletion BGL types, thus all facility idents in any package will enter this index if not prevented from loading completely. This will cause the updated SU4+ API facility ident search lookups to fail as they will not find the actual facilities, which are actually being deleted with the facility deletion BGL types.
We (the MSFS team) have a bead on the issue, but the solution is potentially complex and in legacy code areas. We obviously would like to have this fix in the next sim update, however, if possible.
2 Likes
So, until this is solved, using NG data may result in errors in our flight planning or prevent us from planning correctly, but the stock MSFS data will not?
Is this correct?
Thanks.
No, thats not correct. Only the new NXi and the search feature in the VFR map (what we have currently figured out), which uses the new navdata APIs, are effected of this bug.
The Navigraph data are correct and working as expected, ie when you use the previous NXi (0.14.0), which doesn’t include the newer navdata APIs you will see it works. Also the flightplanner in the WorldMap, the search there, … no issue. It’s only effected on this parts, where the newer navdata APIs (release with SU10) are implemented (NXi and VFR map - again, what we have found out till now).
Cheers
Richard
PS: @Bishop398 I have only used your own terminology about the “new navdata APIs”. So that I understood you correctly - the navdata API was updated/extended with SU10, which results in this bug.
This is not correct. The NXi has been using the same navdata APIs since its initial release. Additionally, 0.14.0 is actually the current Marketplace bridge package, will users should have installed in order to use the SU10 NXi with third party planes.
As mentioned a few times in this thread in response to this issue, these APIs are the same that the NXi has always been using. They have not been updated for SU10. They are only “new” relative to the old FS9GPS simvar based API, which was previously used in other instruments/panels.
This issue is a result of a legacy pre-MSFS code issue that surfaced as a result of the package load system changes.
5 Likes
Only with the NXi, the VFR map, and the PMS GTN 750 in WTT mode. As a workaround, if you’re using those units and fly mostly in the US, you can uninstall Navigraph data temporarily, as the sim uses the exact FAA data already. For other regions you may have to weigh the pros and cons.
The issue will only surface when attempting to input waypoints directly in the units in question; if you load the flight plan from the world map or load a PLN file into the world map, your waypoints will be transferred to the NXi.
3 Likes
A very “professional workaround” to remove proven, working 3rd party data only that a confirmed bug in the sim (whereever it is and what name you give it him) can be “solved”, without any specific timeline when it’s fixed.
And I see this as much more critical, when you wrote that this is a hidden bug since SU4, what can be happen, of course but than, you should try to fix it immediately and not in 6 weeks plus because some 3rd party companies had trust the system since SU4.
Sorry, but thats not acceptable and we will discuss and escalte this internally now. To remove our working data, is not an acceptable “solution” without to know how long. You exclude deliberate, Navigraph user to use stock sim feature.
Cheers
Richard
2 Likes