Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
Collapse
Just Flight Community Forum
  1. Home
  2. Just Flight
  3. MSFS Products
  4. 146 Professional
  5. [V2] Issue with VOR/DME tuning

[V2] Issue with VOR/DME tuning

Scheduled Pinned Locked Moved 146 Professional
15 Posts 5 Posters 605 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    knidarkness
    wrote on last edited by
    #4

    Had the same experience from cold&dark, video on YT is now processing, will add here when it's ready

    1 Reply Last reply
    0
    • B benschooy

      Hey guys,
      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.
      Tried with Nuremberg VOR (NUE) and Otterberg VOR (OTT) both have DME capability and I'm pretty sure it worked with 1.1 as I tried only a couple of days ago. I selected both receivers on. And I also switched between RNAV und NAV mode.
      Can someone verify this issue for me. It might be user error as well. So feel free to correct me if I'm wrong 😉
      Best wishes,
      Bene

      C Offline
      C Offline
      Cpt_Piett
      wrote on last edited by Cpt_Piett
      #5

      @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.

      1 Reply Last reply
      0
      • MartynM Offline
        MartynM Offline
        Martyn
        JF Staff
        wrote on last edited by
        #6

        There were no deliberate changes to the VOR DME logic in v2 and we've not come across this issue but we'll investigate using the examples that you have provided.

        Martyn - Development Manager

        1 Reply Last reply
        0
        • K Offline
          K Offline
          knidarkness
          wrote on last edited by
          #7

          https://www.youtube.com/watch?v=K-1Bf7feu6Y -- it's still "processing", but here's what I've done around DOH vor

          1 Reply Last reply
          0
          • K Offline
            K Offline
            knidarkness
            wrote on last edited by
            #8

            FWIW, I am using the latest navigraph 2403.rev3 + latest JF navigraph database

            1 Reply Last reply
            0
            • MarkM Offline
              MarkM Offline
              Mark
              JF Staff
              wrote on last edited by Mark
              #9

              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

              Just Flight Development Assistant

              1 Reply Last reply
              0
              • K Offline
                K Offline
                knidarkness
                wrote on last edited by
                #10

                Thank you! Indeed, checking the VFR map -- it is void of any VORs...

                1 Reply Last reply
                0
                • MarkM Offline
                  MarkM Offline
                  Mark
                  JF Staff
                  wrote on last edited by
                  #11

                  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

                  Just Flight Development Assistant

                  K B 2 Replies Last reply
                  1
                  • MarkM Mark

                    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

                    K Offline
                    K Offline
                    knidarkness
                    wrote on last edited by
                    #12

                    @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?

                    MarkM 1 Reply Last reply
                    0
                    • MarkM Mark

                      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

                      B Offline
                      B Offline
                      benschooy
                      wrote on last edited by
                      #13

                      @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.

                      1 Reply Last reply
                      1
                      • K knidarkness

                        @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?

                        MarkM Offline
                        MarkM Offline
                        Mark
                        JF Staff
                        wrote on last edited by
                        #14

                        @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

                        Just Flight Development Assistant

                        1 Reply Last reply
                        1
                        • C Offline
                          C Offline
                          Cpt_Piett
                          wrote on last edited by
                          #15

                          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

                          1 Reply Last reply
                          1
                          Reply
                          • Reply as topic
                          Log in to reply
                          • Oldest to Newest
                          • Newest to Oldest
                          • Most Votes


                          • Login

                          • Don't have an account? Register

                          • Login or register to search.
                          • First post
                            Last post
                          0
                          • Categories
                          • Recent
                          • Tags
                          • Popular
                          • Users