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

Engine 1 issues from C&D only.

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Engine 1 issues from C&D only.

    Recently I switched the engine operations to realistic damage and start but having some issues that I can't quite explain but I'll try to explain the phenomenon:

    If I start from C&D, start all engines successfully and all is in the green prior to taking off under engine visualiser, once I call the AFE to run the takeoff checklist I notice that those red feather buttons eventually lit up, the blue governor on engine 1 is lit up as well and engine one has higher RPM's than then others yet under stress visualiser it has CHT to cold for engine 1only. Eventually the maintenance page will show the engine as yellow/stress to eventually fail.

    This happens consisently but it does not happen when I start the same flight/same conditions from the runway instead with engines running already, I still run the TO checklist with the AFE prior to taking off but the feather lights are not illuminated this time around nor is the blue governor nor do I have any of the engine woes that follow.

    I don't see what both situations are different as I follow all procedures, hard not to follow given the AFE does all the work so I just don't understand what is causing this, am I still doing something wrong here prior to the point of TO now that it's set to realistic but looking at all the gauges etc during the pre flight processes there is nothing to indicate that I am.

    Thanks.

    Stefaan de Keersmaeker
    YBCS
    Tags: None
    #2
    Just to make sure: Please check that there are no assistants active in the MSFS assistance options.

    The typical reason for the engine(s) to feather around takeoff is that the AFE activated the autofeather system and an impatient pilot 😉 throttled up to more than 26“ MP to line up. Reducing the throttles again will feather the first engine that will drop below 26“. If you use one hardware axis for all 4 engines it will be engine 1.

    be patient with the old lady.
    Ryzen 7 5800X3D, RTX4080, 32GB DDR4 RAM @3600MHz, 4k
    Marc Eland
    GFO Beta

    Comment

      #3
      I thought about assists interfering as well and I checked for them, nothing is on, if anything it's all set to hard/real whatever the settings are called. I don't even touch the throttles either, not at all actually until the 'before landing' checklist which is when I'll take control of those. I did see the auto feather lights come on during the checklist though, is that meant to happen? Not sure if it does that from C&D only, will have to double check that one.

      But as mentioned the problem only occurs from C&D, very odd.
      Stefaan de Keersmaeker
      YBCS

      Comment

        #4
        Sorry, I can‘t follow. You have an issue that only occurs when you start from C&D (which is the automatic condition when starting from a parking position) but you say you don‘t touch the throttles until approach. How do you get to the runway?

        I might miss something, misunderstand you or whatever, but I‘m confused.

        Autofeather is a takeoff system in the DC6, it should certainly not come on during approach. But has it actually been turned off after departure? If it remains on it will feather the first prop whose engine drops below 26“ MP. This is the critical value. Not sure atm if there is a way it could feather all engines though. Normally it‘s supposed to disarm after one engine failed afaik.

        It COULD be a corrupted panel state file of course.
        Ryzen 7 5800X3D, RTX4080, 32GB DDR4 RAM @3600MHz, 4k
        Marc Eland
        GFO Beta

        Comment

          #5
          Yes sorry, I do taxi to the runway, I was basically referring to me not touching the throttles at takeoff and beyond. I have not been able to reproduce the issue anymore since, I did do all the maintenance on the engine though, maybe that did it but everything was even green prior. We'll see how it goes, appreciate your feedback nevertheless.
          Stefaan de Keersmaeker
          YBCS

          Comment

          Previous template Next
          Working...
          X