Announcement

Collapse

PMDG Forum Rules

1) SIGN YOUR POSTS. Since 1997, we have asked users to sign their real name, first and last, to all posts in the PMDG forum. We do this in order to keep conversations personal and familiar. You took the time to be here, we want to get to know you. This is one of the few rigid rules that we enforce regularly. We do so because we feel that forums in which users must engage one another personally are generally warmer, more collegial and friendly. Posts that are unsigned will be quietly removed without comment by the moderators, so to make your life easy- we recommend enabling your forum signature so that you never need to remember. Do this by clicking the username pull-down at the top right, then selecting "User Settings." You will find the signature editor on the ACCOUNT tab, about half way down the page. Look for "Edit Post Signature." Be sure to click the "Show Signatures" box.

2) BE NICE. We are all simmers here and no matter our differences of opinion, we share a common love of aviation, computing and simulation. Treat everyone else in the forum with respect even when you disagree. If someone frustrates you, walk away from the conversation or ask for a moderator to get involved. Speaking of Moderators, they prefer not to be treated as "The Thought Police" but if any behavior infringes on the enjoyment of another user or is otherwise considered to be unacceptable in the moderator's judgment, it will be addressed in keeping with our view of ensuring that this forum remains a healthy environment for all simmers.

3) BE LAWFUL: Any behavior that infringes upon the law, such as discussion or solicitation of piracy, threats, intimidation or abuse will be handled unsympathetically by the moderators. Threats and intimidation may, at the moderator's discretion, be provided to law enforcement for handling.

4) BE FACTUAL: When you post, always be factual. Moderators will remove posts that are determined not to be factually accurate.

5) RESPECT COPYRIGHTS: Posting of copyrighted material such as flight manuals owned by Boeing or various airlines is not allowed in this forum. If you have questions related to copyrighted material, please contact a forum moderator for clarification.

6) RESPECT PMDG: We love to hear what you like about our products. We also like to hear what you think can be improved, or what isn't working. Please do tell us and we will always treat your feedback with value. Just be sure to treat the team respectfully, as they do put a significant amount of effort into building and maintaining these great simulation products for you.

7) RESPECT PMDG DEVELOPERS: All of the developers will spend some time here. Given the ratio of developers-to-users, it simply isn't possible for us to answer every post and private message individually. Please know that we do try to read everything, but developer workload is simply too high to manage personal contact with tens-of-thousands of users simultaneously. In most cases, members of the development team will stick to conversations in the forum and will not answer private messages.

8) RESPECT OTHER DEVELOPERS: PMDG has always advocated for a strong development community and we have many friends within this community. Every developer offers something unique that helps to make the simming community larger and more vibrant. We insist that you treat our friends respectfully.

9) RESPECT MODERATORS: Moderators have a tough job, and none of them enjoy having to stomp out negativity. If a moderator has to weigh in to keep a thread peaceful, please respect that effort and refrain from giving the moderator any grief.

10) If you require official support for any of our products please open a support ticket through the support portal, https://support.precisionmanuals.com

11) This forum is designed primarily as a vehicle for the PMDG development team to interact with our customers, and for customers to interact with one another in a manner that is positive, supportive and assists in the general advancement of understanding the simulation and helping to make this and future simulations better. Any other use of this forum is not permitted, including but not limited to discussion of pricing policies, business practices, forum moderating policies, advertising of non-PMDG products, promotion of events, services or products that are not approved in advance by PMDG or any other topic deemed unacceptable by any forum administrator

12) HAVE FUN: This is the whole point of it all.
See more
See less

DME distance not correct

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    DME distance not correct

    According to Navigraph, ZSPD, the DME distance at height 1970ft should be 6.2, FBW320 is more accurate, but pmdg737 shows 8.1?QQ图片20220511163144.pngQQ图片20220511163151.png
    QQ图片20220511163203.png
    Jiekeng Luo

    #2
    Originally posted by ljk811 View Post
    According to Navigraph, ZSPD, the DME distance at height 1970ft should be 6.2, FBW320 is more accurate, but pmdg737 shows 8.1?QQ图片20220511163144.pngQQ图片20220511163151.png
    QQ图片20220511163203.png
    Hello I report to Same Problem for Approach ILS X Rwy 28 a BGY the BRM DME not correct.

    Comment


      #3
      I had the same on EKCH 22L and EFHK 15, seems to be happening everywhere. Latest NG navdata installed and the DME is about 2nm off like pics above.

      Comment


        #4
        Originally posted by Henksu View Post
        I had the same on EKCH 22L and EFHK 15, seems to be happening everywhere. Latest NG navdata installed and the DME is about 2nm off like pics above.
        I guess this is the case for all airports because the PMDG uses the wrong way to get the DME distance
        Jiekeng Luo

        Comment


          #5
          Originally posted by ljk811 View Post

          I guess this is the case for all airports because the PMDG uses the wrong way to get the DME distance
          And you know that how? We read what the sim sent to us. Nothing fancy or custom.
          Chris Makris (Olympic260)
          PMDG Technical Support
          http://www.pmdg.com

          Comment


          • ljk811
            ljk811 commented
            Editing a comment
            So why can FBW320 get the correct DME distance but PMDG737 can't? Isn't this worth investigating?

          #6
          I can confirm I have the same issue. I flew into 4 different airports and every airport had the DME exactly 2nm off. at 1000 feet I usually expect the DME to be around 3nm but instead, it reads 5nm. not too sure what's causing the issue but it works fine in other aircraft.
          Yuvarajan Saravanamoorthy

          Comment


            #7
            Guys - check if these airports do not have their DME equipment at the END of the runway and not the threshold....
            P. De Swardt

            Comment


              #8
              Guys, submit a support ticket for this kind of stuff. Best way to get it in their system and officially investigated.
              Matt Smith

              Comment


                #9
                Originally posted by pdeswardt View Post
                Guys - check if these airports do not have their DME equipment at the END of the runway and not the threshold....
                I checked and the DME isn't offset by any means. I fly into these airports regularly so I am pretty sure it's a bug. On a clear day, I use the shoreline for VOMM ILS 25 as a reference point to put my gear down and it's around 5 DME. pmdg only shows 5 DME well inland at 1000 feet which is quite late. will submit an official ticket.
                Microsoft Flight Simulator Screenshot 2022.05.10 - 16.48.06.56.png

                Capture.png
                Last edited by Mindbugs_; 11May2022, 15:53. Reason: Multiple uploads
                Yuvarajan Saravanamoorthy

                Comment


                  #10
                  I'm also seeing this problem with wrong distance to runway when tuning the ILS on NAV1. I happens on a lot of airports. I have tried both with and without Navigraph Navdata and it is the same result. Since so few people report this, I wonder if it has a solution, or only happens in certain situations/OS-languages?

                  On the FBW A320 I do not have this problem with the same base Navdata.
                  Vidar Haaland
                  System: Win11, Intel i9-9900K, Gigabyte Z390, RAM 32GB, M.2 SSD, ASUS RTX 3080 ROG Strix OC

                  Comment


                    #11
                    So, this must be om the scenery creators side (Asobo/external company) and not PMDG.
                    Christoph Linden

                    Comment


                    • ljk811
                      ljk811 commented
                      Editing a comment
                      I have submitted a support ticket to pmdg and they are aware of this bug and it will be fixed in the next update.

                    • NegativeApproach
                      NegativeApproach commented
                      Editing a comment
                      Good to hear that it will be solved in the end PMDG truly rocks

                    #12
                    Originally posted by NegativeApproach View Post
                    So, this must be om the scenery creators side (Asobo/external company) and not PMDG.
                    I am not too sure about that. I don't have DME issues on other airplanes. I have now flown over 20 different airports (some default/some freeware scenery), and all of them have DME indications exactly 2nm offset. anyways I have submitted an official ticket so I am hoping this gets fixed.
                    Yuvarajan Saravanamoorthy

                    Comment


                      #13
                      Originally posted by Mindbugs_ View Post

                      I am not too sure about that. I don't have DME issues on other airplanes. I have now flown over 20 different airports (some default/some freeware scenery), and all of them have DME indications exactly 2nm offset. anyways I have submitted an official ticket so I am hoping this gets fixed.
                      I found the cause of this bug. The DEM coordinates obtained by PMDG are not from airports, including default airports and third-party airports, but from their own navigation data pmdg-aircraft-737\Config\NavData\wpNavAID. And they get the ILS coordinates, not the ILSDME coordinates, so there is always a 2nm error (the length of the runway).

                      For example, Shanghai Pudong Airport, the coordinates of 16L ILS are 31.124872, 121.829478, corresponding to Google Maps as shown in the figure
                      QQ截图20220515111641.jpgQQ截图20220515111942.jpg

                      The ILS DME coordinates of 16L should be 31.157136, 121.815983, corresponding to the Google map as shown in the figureQQ截图20220515111911.jpg

                      So, it's the problem of pmdg, they got the wrong data, so the distance of DME is wrong
                      Jiekeng Luo

                      Comment


                        #14
                        Watched a video of 737NG Driver and he mentioned there is a MSFS bug where the DME is not located on the threshold of the runway for many airports in MSFS, so if that is the case you can't blame PMDG. He showed it on one of his videos where the DME was way of from the real distance to the runway.
                        Martijn Coenen
                        The Netherlands
                        Flying the virtual sky since FS 5.0

                        Comment


                        • ljk811
                          ljk811 commented
                          Editing a comment
                          I have submitted a support ticket to pmdg and they are aware of this bug and it will be fixed in the next update.
                      Working...
                      X