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,

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

Cannot start engines manually, requires AFE - MSFS

  • Filter
  • Time
  • Show
Clear All
new posts

    Cannot start engines manually, requires AFE - MSFS

    Per title, while attempting to setup keys for my controllers, I'm unable to get the engines to turn on my own unless I click on the start and safety switches. I have tried both 059 and 060 lvars and just 060 on it's own, but the blades will not spin.

    Is this really the only way to get it done even if I have all other necessary items mapped out?
    Jacob Buchanan

    I've not tried setting those controls to keys or switches/buttons. I assume you are setting the L: number to either 100 or 0?

    Were I to set up something I'd try the rotor_brake approach first, so for a left click on LVar 060 the RPN script would be 06001 (>K:Rotor_Brake). I'm using AAO, what are you using?
    Dan Downs KCRP
    i7-10700K 32GB 3600MHz 3080Ti


      Originally posted by DDowns View Post
      I've not tried setting those controls to keys or switches/buttons. I assume you are setting the L: number to either 100 or 0?

      Were I to set up something I'd try the rotor_brake approach first, so for a left click on LVar 060 the RPN script would be 06001 (>K:Rotor_Brake). I'm using AAO, what are you using?
      Spad here. The default value (off) is 1, setting the start switch (DC_6_060) to 0 will trigger both the safety (..._059) and start switches as if you were to click them, but the event doesn't actually trigger the start procedure. This was my last approach, I also tried at the same time triggering both switches separately but no luck.

      I may need to create a send command in spad to get it to trigger the click command. Regardless, if a set command moves the switch, in the DC-6 at least, it should command the action, but so far the starter seems to be a bit of a wild one in order to make it easy for everyone.
      Jacob Buchanan


        So this even will act as a left click on the start switch and will successfully trigger an engine start, but the reverse is not true for stopping the starter.

        edit: so interesting bug, with this setup it originally worked. I could crank the engine finally with the afe, but never tried a full on start. Restart the flight, set everything up, and now when I use this button, it counts off 3-6-9-12 about as fast as you can read it, without spinning the prop. So then I attempted to just start it with the mouse but using my keys for the mags, boost and prime... no luck. I go through about 3 start cycles and 2 flight restarts and same result.

        I then notice that after attempts to start X engine, that engine's mags are reset back to off, but my switch was never changed. Looking up during the start, as soon as the engine catches off the prime, the mags are set to off without me moving a key at all.

        Absolutely bizarre.

        edit 2: a send command for simconnect is apparently required in order to prevent the magnetos from swapping back to off when the engines catch. The LVAR only controls the switch but not the action.
        Last edited by Swagger897; 19Sep2023, 05:42.
        Jacob Buchanan


          I don‘t use spad but should be the same there: you need to use the rotor brake event to make mouse actions on the switches. What you do there is only move the switch visually.

          So for object 060 to work you need to "click" the rotor brake event with a mouse event.

          >K:rotor_brake 06001 for left click, 06002 for right click.

          adding 03 is a middle button click, 07 wheel up, 08 wheel down (wheels could be vice versa).

          search the forum for "rotor_brake" and you will get a ton of information about this.
          Ryzen 7 5800X3D, RTX4080, 32GB DDR4 RAM @3600MHz, 4k
          Marc Eland
          GFO Beta