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

Panel state file overwriting

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

    Panel state file overwriting

    Hi folks,

    old panel state files seem to cause issues, if they are incompatible to a new version of PMDG software releases.
    Got it.

    Please confirm that it is save to start anew with one of the delivered panel state files like NGXu cold & dark,
    and save the situation after the flight by overwriting the old one.


    Each aircraft in my hangar has its own p3d state file after the flight, e.g. "748F LX-VCE CLX".

    Thanks in advance.
    Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G

    #2
    Better to start with the default engines running just to be on the safe side.
    Captain Kevin

    Kevin Yang

    Comment


      #3
      Originally posted by Captain Kevin View Post
      Better to start with the default engines running just to be on the safe side.
      Thanks, Kevin.
      Why is that better than cold & dark?
      Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G

      Comment


        #4
        Originally posted by 19ab67 View Post

        Thanks, Kevin.
        Why is that better than cold & dark?
        no panel state at all, it starts with engines running. Shutdown to the state you want and save that as a new panel state
        Chris Makris (Olympic260)
        PMDG Technical Support
        http://www.pmdg.com

        Comment


          #5
          Originally posted by cmakris View Post

          no panel state at all, it starts with engines running. Shutdown to the state you want and save that as a new panel state
          Hi Chris,

          no, it starts cold & dark since I chose PMDG's cold & dark fxml as initial state.
          Again, why would it be better to have the engines running -- I haven't understood that statement.

          Thanks in advance.
          Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G

          Comment


            #6
            Originally posted by 19ab67 View Post

            Hi Chris,

            no, it starts cold & dark since I chose PMDG's cold & dark fxml as initial state.
            Again, why would it be better to have the engines running -- I haven't understood that statement.

            Thanks in advance.
            In the FMC, at the place where you have put the Cold and dark as a default delete it and leave it empty. Restart sim and load the NGXu, it will load with engines running. From there shut it down in the state you want and save that as a panel state.
            Chris Makris (Olympic260)
            PMDG Technical Support
            http://www.pmdg.com

            Comment


              #7
              ok, but why?
              Andre(as) Berg --- i7 8700K 12MB 3.7G. MSI Z370 Tomahawk. DDR4 16G. SSD 500G M.2. MSI RTX2080 DUKE 8G

              Comment


                #8
                Originally posted by 19ab67 View Post
                ok, but why?
                This will make sure you will not have any panel state corruption.
                Chris Makris (Olympic260)
                PMDG Technical Support
                http://www.pmdg.com

                Comment


                  #9
                  Shouldn´t the generic panel states that comes with the NGXu work ?
                  Hopefully they have been updated to be in sync with the latest updated version.

                  By this I mean the Cold & dark, Short and Long states.
                  Finn Jacobsen
                  PC Spec.: i7 3770 3.4 Ghz, 16GB RAM, Nvidia GTX 960 4 GB, Windows 7 Home Edition

                  Comment


                    #10
                    Originally posted by Wothan View Post
                    Shouldn´t the generic panel states that comes with the NGXu work ?
                    Hopefully they have been updated to be in sync with the latest updated version.

                    By this I mean the Cold & dark, Short and Long states.
                    There's no guarantee that this is the case. The default engines running state wouldn't have this issue since there is no actual panel state for that one.
                    Captain Kevin

                    Kevin Yang

                    Comment


                      #11
                      My apologies for semi-hijacking this thread but I'm having an issue where when I start a new flight (with another type of the 737), it uses the panel state from the previously used aircraft. From my understanding this was not the case in the past (e.g. 747 v3). In the past it would always load the default panel state. Is there a setting for this that I'm missing?
                      Tomas Hoste

                      Comment


                        #12
                        Originally posted by simtom View Post
                        My apologies for semi-hijacking this thread but I'm having an issue where when I start a new flight (with another type of the 737), it uses the panel state from the previously used aircraft. From my understanding this was not the case in the past (e.g. 747 v3). In the past it would always load the default panel state. Is there a setting for this that I'm missing?
                        If you are loading a previously saved scenario, then that scenario loads a panel state saved with that scenario. Also, you can use the PMDG Options to name a panel that will always load regardless of scenario.

                        If neither of above apply, then the aircraft should load from the P3D Select Aircraft screen with no panel state, engines running.
                        Dan Downs KCRP

                        Comment


                          #13
                          Originally posted by DDowns View Post
                          If neither of above apply, then the aircraft should load from the P3D Select Aircraft screen with no panel state, engines running.
                          That's the problem I'm having, even when loading an aircraft from the Select Aircraft screen, it still loads with the panel from a previous scenario.
                          Tomas Hoste

                          Comment


                            #14
                            Originally posted by simtom View Post

                            That's the problem I'm having, even when loading an aircraft from the Select Aircraft screen, it still loads with the panel from a previous scenario.
                            Okay but you didn't say you have not set a default panel or perhaps selected use last flight oil quantity. Still not sure why you are having this problem, and I'm not sure if you are seeing the same airplane configuration or the same panel state. I guess a more complete problem description would help.
                            Dan Downs KCRP

                            Comment


                              #15
                              Originally posted by DDowns View Post

                              Okay but you didn't say you have not set a default panel or perhaps selected use last flight oil quantity. Still not sure why you are having this problem, and I'm not sure if you are seeing the same airplane configuration or the same panel state. I guess a more complete problem description would help.
                              So, in the past whenever I loaded up a new scenario using the 747, it loaded up using the default panel state where the engines are already running. Now since a couple of weeks I've been having this issue. I will do some more digging to find out what's causing this.
                              Tomas Hoste

                              Comment


                              • DDowns
                                DDowns commented
                                Editing a comment
                                Tomas I still don't know what "this" is.... also your first post indicated a problem with the 737 but now you point to the 747. I'm confused. It's extremely hard to help when one doesn't know what the problem is.

                              • simtom
                                simtom commented
                                Editing a comment
                                I understand that you're confused but I'll try to explain it more clearly.

                                I'm referring to the 747 because I had no panel state problems with it in the past (loading it from the Select Aircraft screen resulted in it being spawned with the engines running and using the default panel state).

                                Now, after purchasing the 737 NGXu I started noticing that it loads the panel state from a previous scenario. So what I mean is that I never get the default panel state anymore where the engines are already running (only when I closed the previous session with the engines still running obviously). I noticed this problem because I finished off my session with the aircraft completely shut down. The next day I loaded up a different 737 (new scenario, from the Select Aircraft screen) and it spawned with the panel state from the previous session (shut down state).

                                That's why I referred to the 747 because it isn't loading a panel state from a previous flight (of course, it does when loading the save file of that particular flight).

                              #16
                              With the 737, after securing the aircraft, if you didn't save the scenario then that aircraft state is saved as a previous flight. Somehow you are loading the previous flight by default. This is an option that can be selected from the PMDG Setup menu options for the StartupState .... see Introduction pg 61.
                              Dan Downs KCRP

                              Comment

                              Working...
                              X