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

8.33khz on Radios

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

    8.33khz on Radios

    Hello!
    maybe a stupid question!
    i fly my Ngxu only online with IVAO altitude!
    sometimes I cannot communicate by text with a controller! He did not read me! This happened with freq. for example 121.705 (on the Ngxu radio Panel 121.700 is set)! Could it be that the Ngxu doesn’t support 8.33khz on radios!

    thx

    Essl Alexander

    #2
    Originally posted by EsslAlex View Post
    Hello!
    maybe a stupid question!
    i fly my Ngxu only online with IVAO altitude!
    sometimes I cannot communicate by text with a controller! He did not read me! This happened with freq. for example 121.705 (on the Ngxu radio Panel 121.700 is set)! Could it be that the Ngxu doesn’t support 8.33khz on radios!

    thx

    Essl Alexander
    None of the sims supported 8.33 spacing. This has changed with P3Dv5. We are going to implement 8.33 spacing for P3Dv5 but this will not be part of the first version of NGXu for v5
    Chris Makris (Olympic260)
    PMDG Technical Support
    http://www.pmdg.com

    Comment


      #3
      Ok thanks! So it must be a problem with altitude!
      tjx very much

      Comment


        #4
        Originally posted by cmakris View Post

        None of the sims supported 8.33 spacing. This has changed with P3Dv5. We are going to implement 8.33 spacing for P3Dv5 but this will not be part of the first version of NGXu for v5
        Hello,

        Just wondering, is this going to be applied sometime? Or is it already there?
        The new Voxatc version for P3D v5 also works with 8.33, that's why I ask!

        Gr.

        Robert Koolstr.
        Robert Kools

        Comment


          #5
          It's not implemented yet, but Chris' statement still stands unless anything contrary has been said over an official channel.

          Comment


            #6
            Would be great of it could be added soon, now it is impossible to enter frequencies on a lot of airports on the Comm's.

            Gr.

            Robert Koolstr.
            Robert Kools

            Comment


              #7
              For those who fly online with VATSIM, certainly in the UK we've taken the decision NOT to move to 8.33 spacing with our frequencies until the overwhelming majority of add-on aircraft support it. Frequencies either remain on their previous entry or to something very close to it that is selectable in almost all aircraft.
              Trevor Hannant

              CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
              GPU: Nvidia RTX4070Ti
              RAM: 32Gb

              Comment


                #8
                I don't know for IVAO, but on VATSIM all pilots and controller clients don't consider the last decimal number.
                So for example if you need to contact 119.705, the clients will read just 119.70, so you can easily talk to a 8.33KHz spaced frequency, just by setting the closest decimals in your com panel.
                Just to make an example: if the frequency you have to contact is 125.330, tuning the com on 125.325 will work fine since .325 is the closest decimal to .330

                I'm pretty confident MSFS will have 8.33KHz spacing as well, but as said above, it will probably not be implemented until the vast majority of aircrafts will support it. And the vast majority of aircrafts will probably not support it, until the vast majority of users will run on a sim that supports it.
                It's just a matter of time, but it'll eventually become a standard.
                Giovanni D. Tarar
                FAA CPL+IR Single & Multiengine Land
                I love flying when I'm in a bad mood

                Comment


                  #9
                  Any news on this topic?

                  Is it going to be implemented soon?

                  Gr.

                  Robert Koolstr.
                  Robert Kools

                  Comment


                    #10
                    Originally posted by Roberto0203 View Post
                    Any news on this topic?

                    Is it going to be implemented soon?

                    Gr.

                    Robert Koolstr.
                    I doubt they will visit this item on the to-do list until after both 777 and DC-6 have installed on P3Dv5, and then it will depend on how many alligators they find when draining that swamp.
                    Dan Downs KCRP
                    i7-10700K 32GB 3600MHz 3080Ti

                    Comment


                      #11
                      I’m happy without it. I suspect my Logitech radio panel would lose vatsim functionality
                      Dave Gray

                      Comment


                        #12
                        Originally posted by cmakris View Post

                        None of the sims supported 8.33 spacing. This has changed with P3Dv5. We are going to implement 8.33 spacing for P3Dv5 but this will not be part of the first version of NGXu for v5
                        It's been 3 years


                        Last edited by PreciselyTuned; 12Sep2023, 15:47. Reason: nvm it did
                        Denzel de Reuver

                        Comment


                          #13
                          Originally posted by micstatic View Post
                          I’m happy without it. I suspect my Logitech radio panel would lose vatsim functionality
                          Mine works perfectly fine - other than the display being a digit short.. You can counter this however by dropping the '1' at the start using whatever software you use to drive it. If your tuning steps are setup as increment/decrement by 0.25, just change these to do so by 0.005 instead.
                          Trevor Hannant

                          CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz
                          GPU: Nvidia RTX4070Ti
                          RAM: 32Gb

                          Comment

                          Working...
                          X
                          😀
                          🥰
                          🤢
                          😎
                          😡
                          👍
                          👎