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

How to handle the Startup states with Hyd bug?

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

    How to handle the Startup states with Hyd bug?

    Hello!
    I am on the latest update and still see the Refill Hyd failure bug.
    I know that this could be connected to an faulty startup state. I never created an own state, I always use the default LONG state.

    I dont know if I get this right:
    It seems that the default startup states will not be updated when a patch comes out? So they are somewhat incompatible?

    As I never created any own startup state in any aircraft I dont know how to do this correctly... can anyone enlighten me?

    Thank you very much and sorry about my confusion!
    Klaus Schmitzer

    #2
    You need to set the cockpit (all switches etc) in your wished state. Then go into the CDU panel state menu and there is an option "save panel state". There you can give a name for the panel state and save it.
    ‚Äč

    Comment


      #3
      Originally posted by Hendrik96 View Post
      You need to set the cockpit (all switches etc) in your wished state. Then go into the CDU panel state menu and there is an option "save panel state". There you can give a name for the panel state and save it.
      Oh its that easy! But one more question - before I create this state, what state should I activate? When I load in with the already set default LONG state or COLD AND DARK I just save this buggy state!?
      Klaus Schmitzer

      Comment


        #4
        Originally posted by Rhinozherous View Post

        Oh its that easy! But one more question - before I create this state, what state should I activate? When I load in with the already set default LONG state or COLD AND DARK I just save this buggy state!?
        In the CDU go to the panel state settings and delete the load up state. Next time you load the airplane it will have its engines running and everything is "default". from there you can do whatever you want. however I believe the PMDG panel states (short, long, cold and dark) have been updated.
        i7-6700k, GTX 1080TI, 32GB DDR4 RAM @1600MHz, 4k

        Comment


          #5
          Originally posted by Rhinozherous View Post

          Oh its that easy! But one more question - before I create this state, what state should I activate? When I load in with the already set default LONG state or COLD AND DARK I just save this buggy state!?
          Load no panel states. This will load the plane ready for flying. Shut it down as you like and set that as panel state
          Chris Makris (Olympic260)
          PMDG Technical Support
          http://www.pmdg.com

          Comment


            #6
            Thank you very much guys!
            Klaus Schmitzer

            Comment


              #7
              Originally posted by cmakris View Post

              Load no panel states. This will load the plane ready for flying. Shut it down as you like and set that as panel state
              This worked for me, thx
              Sergio Naiberg

              Comment


                #8
                Good morning
                I encountered a related problem : impossible to find the aircrafst in flight configuration after the last update and GSX manipulations after a landing.
                The planes (800/900 + 600/700) were all in the starting position, as soon as they were reloaded but all engines stopped.
                Even after trying to reload different panels from the FMC.
                After having uninstalled/reinstalled the two softs (base + expansion), always the same problem.
                What I did :
                - deleted all the panel state files,
                - re-installed the aircraft from the initial files downloaded from the site,
                - launched a flight without installing the latest update 2.91.0122
                - all aircrafts (600/700 et 800/900) in flight configuration : OK,
                - saved the panels in the FMC,
                - installed the update 2.91.0122.
                - restarted P3D v4.5 hf2
                - Now,everything's ok now.
                Have a nice day.
                JP Marrer

                Comment

                Working...
                X