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

New pilot - some questions

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

    New pilot - some questions

    Hello! I am new to MSFS2020 and the DC-6 and am very excited about my new purchases. I'll use this thread to ask questions as I go along and hopefully get feedback and support as I heard these forums were very helpful! Starting off:

    1) I believe I got the DC-6 installed and updated correctly, however I'm not seeing the PMDG DC-6 folder in the C:\Users\...\AppData\Roaming\Microsoft Flight Simulator\Packages\Official\Steam directory. Where is the plane actually installed? Where is the operations center installed? Thanks!
    Daniel Lucas - KLOU
    i9-10900K 32GB RTX3090
    PPL SEL (SR22)

    #2
    Welcome to the PMDG forums, please note that on joining we all agreed to sign our full name on every post.

    The PMDG DC-6 is installed into the Community folder. Each user has the option when installing MSFS to put the Community folder where you want it to go. Mine is simply c:\MSFS, I don't know how you used that option.

    The OC is installed into your appdata\roaming folder. I recommend creating a shortcut on your desktop pointing to the oc executable, and set it to always run with admin rights.
    Dan Downs KCRP
    i7-10700K 32GB 3600MHz 2080Ti

    Comment


      #3
      Originally posted by DDowns View Post
      Welcome to the PMDG forums, please note that on joining we all agreed to sign our full name on every post.

      The PMDG DC-6 is installed into the Community folder. Each user has the option when installing MSFS to put the Community folder where you want it to go. Mine is simply c:\MSFS, I don't know how you used that option.

      The OC is installed into your appdata\roaming folder. I recommend creating a shortcut on your desktop pointing to the oc executable, and set it to always run with admin rights.
      thanks! I was looking in the Official package (as thats where my other payware planes reside). But I have found it, along with the documentation, great. I have also placed the OC shortcut on desktop.

      And didn't think I understood the signing thing, as I used my actual name when I registered I thought it was attached to my posts? Do I need to actually type my name out in each post? I'll copy yours for now as it seems to work!

      Next question: I'm following Tutorial 1 and have successfully taken off. Working on the AP now and wanting to bind the AP pitch and AP roll commands to my HOTAS. Can someone point me in the right direction on which keybindings to use for Autopilot functions? There are a ton and it's super confusing. Thanks!

      EDIT: i tried to map "INCREASE AP PITCH HOLD REFERENCE" but that didn't seem to do anything...
      Last edited by dresoccer4; 12Sep2021, 20:47.
      Daniel Lucas - KLOU
      i9-10900K 32GB RTX3090
      PPL SEL (SR22)

      Comment


        #4
        Originally posted by dresoccer4 View Post

        Next question: I'm following Tutorial 1 and have successfully taken off. Working on the AP now and wanting to bind the AP pitch and AP roll commands to my HOTAS. Can someone point me in the right direction on which keybindings to use for Autopilot functions? Thanks!


        ________________________
        Daniel Lucas KLOU
        i9-10900K 32GB RTX3090
        PPL SEL (SR22)
        Hi Daniel (nice name): I recommend Lorby's Axes and Ohs (AAO), it's inexpensive and is very versatile and I'm using it in MSFS with the DC-6 with custom assignments to both keyboard and my Warthog HOTAS. Be prepared to learn RPN scripting, for you can directly assign some things but others like the Sperry A-12 controls need to be scripted using the Rotor_Brake function.

        Search this forum for how others have accomplished this. Some are using FSUIPC7 but I've come to prefer AAO.

        Tip: Many custom controls (the Sperry A-12 is basically a custom job) will not work by simply manipulating the control's LVar. You actually have to use the Rotor_Brake function to simulate left and right mouse clicks. Be sure to set your mouse actions to the PMDG settings. After setting up the PMDG mouse actions, take a look at the PMDG_DC-6x_VC.xml file in the <community>\PMDG-AIRCRAFT-DC6\SimObjects\Airplanes\PMDG DC-6x\model folder. Browsing this file will reveal the LVars used by PMDG, and AAO will actually import those into itself for your use. As for the A-12 A/P, you'll find gyropilot switch is 434 and you use it with Rotor_Brake function where you multiply the LVar by 100 (or add two trailing zeros) to get 43400. You then add a digit to 43400 depending on which mouse function you want:

        1 Left Click
        2 Right Click
        etc.

        So to click (or toggle) the gyropilot switch your RPN script would be this: 43401 (>K:ROTOR_BRAKE) and this mimics a left mouse click on that switch control. Then it is assigned to a button or switch on your HOTAS (I'm using Button 01 on the Joystick). I got fancy and expanded the script to include first clicking on the hot spot to center the turn wheel and forcing the mode switch to Gyro mode, then flipping the mechanical clutch lever up and finally clicking on the gyropilot switch. Nice thing about scripting is you can get as fancy as you wish.
        Last edited by DDowns; 12Sep2021, 20:51.
        Dan Downs KCRP
        i7-10700K 32GB 3600MHz 2080Ti

        Comment


          #5
          Originally posted by DDowns View Post

          Hi Daniel (nice name): I recommend Lorby's Axes and Ohs (AAO), it's inexpensive and is very versatile and I'm using it in MSFS with the DC-6 with custom assignments to both keyboard and my Warthog HOTAS. Be prepared to learn RPN scripting, for you can directly assign some things but others like the Sperry A-12 controls need to be scripted using the Rotor_Brake function.

          Search this forum for how others have accomplished this. Some are using FSUIPC7 but I've come to prefer AAO.

          Tip: Many custom controls (the Sperry A-12 is basically a custom job) will not work by simply manipulating the control's LVar. You actually have to use the Rotor_Brake function to simulate left and right mouse clicks. Be sure to set your mouse actions to the PMDG settings. After setting up the PMDG mouse actions, take a look at the PMDG_DC-6x_VC.xml file in the <community>\PMDG-AIRCRAFT-DC6\SimObjects\Airplanes\PMDG DC-6x\model folder. Browsing this file will reveal the LVars used by PMDG, and AAO will actually import those into itself for your use. As for the A-12 A/P, you'll find gyropilot switch is 434 and you use it with Rotor_Brake function where you multiply the LVar by 100 (or add two trailing zeros) to get 43400. You then add a digit to 43400 depending on which mouse function you want:

          1 Left Click
          2 Right Click
          etc.

          So to click (or toggle) the gyropilot switch your RPN script would be this: 43401 (>K:ROTOR_BRAKE) and this mimics a left mouse click on that switch control. Then it is assigned to a button or switch on your HOTAS (I'm using Button 01 on the Joystick). I got fancy and expanded the script to include first clicking on the hot spot to center the turn wheel and forcing the mode switch to Gyro mode, then flipping the mechanical clutch lever up and finally clicking on the gyropilot switch. Nice thing about scripting is you can get as fancy as you wish.
          Nice name indeed, isn't it.

          Whoosh, didn't realize you couldn't simply map stuff to some keys. This sounds complex. I will have to deal with clicking the controls with my mouse for now and come back to this another day. Tutorial 1 is already holding all of my attention at the moment. Thanks for your help.
          Daniel Lucas - KLOU
          i9-10900K 32GB RTX3090
          PPL SEL (SR22)

          Comment


            #6
            Originally posted by DDowns View Post

            ..

            So to click (or toggle) the gyropilot switch your RPN script would be this: 43401 (>K:ROTOR_BRAKE) and this mimics a left mouse click on that switch control. Then it is assigned to a button or switch on your HOTAS (I'm using Button 01 on the Joystick). I got fancy and expanded the script to include first clicking on the hot spot to center the turn wheel and forcing the mode switch to Gyro mode, then flipping the mechanical clutch lever up and finally clicking on the gyropilot switch. Nice thing about scripting is you can get as fancy as you wish.
            quick q: does the "altitude hold" ap function key work as normal?
            Daniel Lucas - KLOU
            i9-10900K 32GB RTX3090
            PPL SEL (SR22)

            Comment


              #7
              Originally posted by dresoccer4 View Post

              quick q: does the "altitude hold" ap function key work as normal?

              Nope sorry, pretty much all Gyropilot functions, including Altitude Hold, need to be triggered via LVARs and/or ROTOR_BRAKE events
              Dirk Flachbart

              Comment


                #8
                Originally posted by woodstock327 View Post


                Nope sorry, pretty much all Gyropilot functions, including Altitude Hold, need to be triggered via LVARs and/or ROTOR_BRAKE events
                hmm ok. well what i did find was normal autopilot still works just fine, albeit by magic. pressing the normal VS, altitude, approach AP keys fires it up (and conflicts which is very confusing)
                Daniel Lucas - KLOU
                i9-10900K 32GB RTX3090
                PPL SEL (SR22)

                Comment


                  #9
                  Another questions: do the prop animations currently reflect the angle of the blades? Or situations such as feathering?

                  I know some of the planes in XPlane do this really well and it's fun to watch the engines from the side and see the blade blur thickening and thinning as you test the prop.
                  Daniel Lucas - KLOU
                  i9-10900K 32GB RTX3090
                  PPL SEL (SR22)

                  Comment

                  Working...
                  X