[V2] Issue with VOR/DME tuning
-
Had the same experience from cold&dark, video on YT is now processing, will add here when it's ready
-
@benschooy said in [V2] Issue with VOR/DME tuning:
Since the V2 update I have an issue when tuning in a normal VOR station. Trying to tune in the station does not lead to any needle deflection. Furthermore, I don't get a DME indication. This applies to both VOR receivers.
However, for an ILS it seems to work correctly.Exactly the same issue here. On approach to EGLL ILS 27R and the ILS DME gets a DME indication, whereas the BNN and LON VORs don't.
Range is not the issue as I'm currently circling around the BNN VOR.
-
https://www.youtube.com/watch?v=K-1Bf7feu6Y -- it's still "processing", but here's what I've done around DOH vor
-
FWIW, I am using the latest navigraph 2403.rev3 + latest JF navigraph database
-
This looks to be quite a strange one. We've confirmed within the development team that we have tracked VORs and flown VOR approaches as recently as last night so we are confident that Navaids can be tuned with V2 of the 146 Professional, so it looks like there may be an external factor at play here.
We have been able to replicate this issue of VORDMEs not being detected in the 146 as well as several other aircraft. Something one of our development team has noticed is that when this issue occurs, the MSFS VFR map does not show any navaids, as if no Navaids exist in the simulator.
We are actively investigating this, but at the moment this looks like it may either be an issue with the MSFS servers or maybe an issue with the latest Navigraph ARINC Cycle 2403 revision 3 that was released earlier today.
We'll keep you all updated if we find anything.
Mark - Just Flight
-
Thank you! Indeed, checking the VFR map -- it is void of any VORs...
-
Just to confirm, we are confident this is an issue with the latest Navigraph Navdata that was released earlier today (4th April) "Navigraph ARINC Cycle 2403 revision 3".
Hopefully, Navigraph will be able to update the Navdata soon to fix the issue, but in the meantime, the solution will be to uninstall the "Navigraph ARINC Cycle 2403 revision 3" from the Navigraph Hub if you would like to see VORDMEs in the sim.
Mark - Just Flight
-
@Mark , to clarify, if i uninstall the Navigraphs 2403.3, but not JF's version -> VORs will be there + UNS-1 will still use waypoints from 2403?
-
@Mark said in [V2] Issue with VOR/DME tuning:
Just to confirm, we are confident this is an issue with the latest Navigraph Navdata that was released earlier today (4th April) "Navigraph ARINC Cycle 2403 revision 3".
Hopefully, Navigraph will be able to update the Navdata soon to fix the issue, but in the meantime, the solution will be to uninstall the "Navigraph ARINC Cycle 2403 revision 3" from the Navigraph Hub if you would like to see VORDMEs in the sim.
Mark - Just Flight
Works perfectly fine for me! Thank you very much vor your quick support! :) Now it's time for the first real flight! :) Awesome Job done here and I guess Navigraph will fix their issue soon, too.
-
@knidarkness Correct. The 146s Navdata is completely separate to the MSFS Navdata. So if you delete "Navigraph ARINC Cycle 2403 revision 3" from the Navigraph Hub, that will revert the MSFS Navdata back to it's default, but as the UNS-1s Navdata is completely separate, it will still use the latest 2403 cycle.
Mark - Just Flight
-
Looks like Navigraph has released AIRAC 2403 Revision 4 which should fix the issues.
https://forum.navigraph.com/t/release-notes-msfs-airac-cycle/1755
