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

Problem after the update SU11

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

    Problem after the update SU11

    I noticed some issues after updating with the 737. The plane no longer follows its flight path (LNAV/VNAV on), when i tried to press Heading to follow the heading manually nothing works and the AP CMD A doesn't work either. After taking off, i engage the AP but the plane nose dives for no valid reason or a significant climb at 20°.
    Kimi Häkkinen

    #2
    I can not confirm this, the AP works fine, LNAV and VNAV is flown correctly.
    Roland Arndt

    Comment


      #3
      Originally posted by Iceman7 View Post
      I noticed some issues after updating with the 737. The plane no longer follows its flight path (LNAV/VNAV on), when i tried to press Heading to follow the heading manually nothing works and the AP CMD A doesn't work either. After taking off, i engage the AP but the plane nose dives for no valid reason or a significant climb at 20°.
      This is usually due to not turning off ALL MSFS Pilot Assist options.
      Dan Downs KCRP
      i7-10700K 32GB 3600MHz 3080Ti

      Comment


        #4
        Nothing is enabled. I set everything to hard, i hate assists.
        Kimi Häkkinen

        Comment


          #5
          I had this issue earlier. I deleted the "Startup State" and reloaded into the sim. Issue was solved. Not sure if that was the root cause, but a quick reload fixed it.

          Comment


            #6
            ok i'll try.
            Kimi Häkkinen

            Comment


              #7
              It works! thx!
              Kimi Häkkinen

              Comment


                #8
                Corrupt panel state, I am guessing.
                Captain Kevin

                Kevin Yang

                Comment


                • Iceman7
                  Iceman7 commented
                  Editing a comment
                  I think. The SU11 kill my sim.

                #9
                Originally posted by Captain Kevin View Post
                Corrupt panel state, I am guessing.
                One thing I got into the habit of doing with P3D was loading the plane in default state and then loading my desired panel rather than using my desired panel as the startup state.

                Is this the recommended approach again in MSFS? If so, why is a startup option even offered?
                Andrew Hill
                i9-9900KS 64GB Dual RTX 2080 Super
                P3D V5 & MSFS 2020

                Comment


                  #10
                  Originally posted by jmarauder04 View Post
                  I had this issue earlier. I deleted the "Startup State" and reloaded into the sim. Issue was solved. Not sure if that was the root cause, but a quick reload fixed it.
                  Where can i find this

                  Comment


                  • Pieterqe
                    Pieterqe commented
                    Editing a comment
                    Cant find it

                  • Iceman7
                    Iceman7 commented
                    Editing a comment
                    strange it's for in the content manager that i deleted it. but i thought that the problem was fixed but i still have the same problem. When i engage the AP the plane either climbs 20° too high or falls at 25°. I have to fly manually.

                  • Pieterqe
                    Pieterqe commented
                    Editing a comment
                    I think its a pmdg problem, cuz it started after su11. I guess we need to wait until they fix it

                  #11
                  Yeah, same for after the SU11. I don't see any other solution at the moment. Wait next update.
                  Kimi Häkkinen

                  Comment


                    #12
                    The problem indeed comes from the panel state. When i start on the runway everything is good but when i start in cold and dark (panel customized) the same problem happens again and again.
                    Kimi Häkkinen

                    Comment


                      #13
                      for me plane nose dives down and a/t is broken whether its approach state or runway it always does this

                      Comment


                      • Iceman7
                        Iceman7 commented
                        Editing a comment
                        Was the issue resolved after the last update?

                      #14
                      Originally posted by Pieterqe View Post
                      for me plane nose dives down and a/t is broken whether its approach state or runway it always does this
                      Hard to assist without more information. Which model, what’s your controller setup, route, etc. screenshots are helpful.
                      George Morris

                      Comment


                        #15
                        I too seem to have this exact problem when attempting to engage the autopilot from cold and dark. Checklist has been followed every time.
                        Engaging the autopilot works, but the plane climbs or descends unreliably, doesn't follow your altitude input and doesn't follow either VNAV or Heading (tried both).
                        I'm yet to try from another startup state.
                        Carl Johnson

                        Comment


                          #16
                          Carl can you give us your flight plan screenshots of the panel? Hard to diagnose with so little information.
                          George Morris

                          Comment


                            #17
                            Similar problem here, after the SU11. If I load a panel state, the 737 would not follow the VNAV properly, mostly descending too slow, and subsequently missing the approach.
                            All other AP modes were OK, including LNAV.
                            NOT loading any panel state and configuring everything manually, solves the problem, the 737 follows the VNAV perfectly, as it did before the SU11!
                            Deleting all the "old" panel states and saving a new one does not solve the problem, as soon as I load the new saved panel,
                            the 737 does not follow the VNAV properly. PMDG, please advise.



                            Alfredo Croci

                            Comment


                              #18
                              Originally posted by ac5 View Post
                              Similar problem here, after the SU11. If I load a panel state, the 737 would not follow the VNAV properly, mostly descending too slow, and subsequently missing the approach.
                              All other AP modes were OK, including LNAV.
                              NOT loading any panel state and configuring everything manually, solves the problem, the 737 follows the VNAV perfectly, as it did before the SU11!
                              Deleting all the "old" panel states and saving a new one does not solve the problem, as soon as I load the new saved panel,
                              the 737 does not follow the VNAV properly. PMDG, please advise.


                              We have not seen this in testing. I suggest opening a ticket with PMDG support.
                              George Morris

                              Comment


                                #19
                                Well, you have not seen this in testing... Did you do exactly what I did?
                                Alfredo Croci

                                Comment


                                  #20
                                  Originally posted by ac5 View Post
                                  Well, you have not seen this in testing... Did you do exactly what I did?
                                  Not possible with the lack of detail in your problem description.
                                  Dan Downs KCRP
                                  i7-10700K 32GB 3600MHz 3080Ti

                                  Comment


                                    #21
                                    Originally posted by DDowns View Post

                                    Not possible with the lack of detail in your problem description.
                                    Lack of description? It's quite simple.
                                    One loads a panel state, the VNAV does not work properly.
                                    One DOES NOT load a panel state, the VNAV does not works properly.
                                    Alfredo Croci

                                    Comment


                                      #22
                                      Originally posted by ac5 View Post
                                      Lack of description? It's quite simple.
                                      One loads a panel state, the VNAV does not work properly.
                                      One DOES NOT load a panel state, the VNAV does not works properly.
                                      So in other words, VNAV doesn't work at all for you. But in that case, if VNAV never worked, presumably they would have seen it and it wouldn't have been released.
                                      Captain Kevin

                                      Kevin Yang

                                      Comment


                                        #23
                                        Originally posted by ac5 View Post

                                        Lack of description? It's quite simple.
                                        One loads a panel state, the VNAV does not work properly.
                                        One DOES NOT load a panel state, the VNAV does not works properly.
                                        Please open a ticket with PMDG support. They will assist sorting this out for you.

                                        As mentioned if VNAV didn’t work, you would see other global remediations from PMDG. VNAV is working so this must be something with your specific install. PMDG will assist helping you correct the problem.
                                        George Morris

                                        Comment


                                          #24
                                          Did you guys even read what I write? VNAV does work perfectly.... It just does not work properly IF ONE LOADS A PANEL STATE....
                                          No matter if an "old" panel state, saved before SU 11 or a new one, saved after SU 11.
                                          This did not happen before SU 11.
                                          Alfredo Croci

                                          Comment


                                            #25
                                            Originally posted by ac5 View Post
                                            Did you guys even read what I write? VNAV does work perfectly.... It just does not work properly IF ONE LOADS A PANEL STATE....
                                            No matter if an "old" panel state, saved before SU 11 or a new one, saved after SU 11.
                                            This did not happen before SU 11.
                                            With all do respect and kindness… Did you read what you wrote??

                                            Originally posted by ac5 View Post

                                            Lack of description? It's quite simple.
                                            One loads a panel state, the VNAV does not work properly.
                                            One DOES NOT load a panel state, the VNAV does not works properly.


                                            The two “does not work” is what I was responding to.

                                            Regardless I highly recommend opening a ticket. Panel Saves are working as well.
                                            Last edited by Falcon99; 01Dec2022, 19:05.
                                            George Morris

                                            Comment


                                              #26
                                              Originally posted by ac5 View Post
                                              Did you guys even read what I write? VNAV does work perfectly.... It just does not work properly IF ONE LOADS A PANEL STATE....
                                              No matter if an "old" panel state, saved before SU 11 or a new one, saved after SU 11.
                                              This did not happen before SU 11.
                                              Yes, I read what you wrote, this was what you said.
                                              Originally posted by ac5 View Post
                                              Lack of description? It's quite simple.
                                              One loads a panel state, the VNAV does not work properly.
                                              One DOES NOT load a panel state, the VNAV does not works properly.
                                              Notice that you said in both cases, it doesn't work properly, hence my befuddlement. In any event, have you tried to create a new panel state and see if the new panel state works. A lot of the time, if an update for the aircraft is released, the panel states get corrupt since more parameters may have been added in that the older panel states don't have.
                                              Captain Kevin

                                              Kevin Yang

                                              Comment


                                                #27
                                                Ok, i found where the problem came from since the release of the SU11. That's when i press the key on pause. When i press pause during takeoff or landing when i take shots, and i press the "pause" key again to resume my flight that the problems arise. the plane no longer followed its flight plan, impossible to start the APU, i tried but nothing worked, when i stopped the engines, the engines continued to operate and remained at 20% N1, when i enable the GPU, it's not displayed on the overhead so it's impossible to connect it...no pressurization, Flt Alt/Land Alt becomes dotted lines, the plane climbs/descends without reason, nose dive...until PMDG restores this problem, don't use the pause button during your flight.
                                                Kimi Häkkinen

                                                Comment


                                                  #28
                                                  I have the same problem. I did a flight using the Pause at TOD option and afterwards the autopilot would not do anything I entered.
                                                  I then did a flight without ever using any pause option and there where no issues at all.

                                                  Thorsten Weiss

                                                  Comment


                                                    #29
                                                    Originally posted by Iceman7 View Post
                                                    Ok, i found where the problem came from since the release of the SU11. That's when i press the key on pause. When i press pause during takeoff or landing when i take shots, and i press the "pause" key again to resume my flight that the problems arise. the plane no longer followed its flight plan, impossible to start the APU, i tried but nothing worked, when i stopped the engines, the engines continued to operate and remained at 20% N1, when i enable the GPU, it's not displayed on the overhead so it's impossible to connect it...no pressurization, Flt Alt/Land Alt becomes dotted lines, the plane climbs/descends without reason, nose dive...until PMDG restores this problem, don't use the pause button during your flight.
                                                    In MSFS, Pause and Un-pause are two different things. See the Introduction pg 28 "Other Important Settings."
                                                    Dan Downs KCRP
                                                    i7-10700K 32GB 3600MHz 3080Ti

                                                    Comment


                                                      #30
                                                      Originally posted by DDowns View Post

                                                      In MSFS, Pause and Un-pause are two different things. See the Introduction pg 28 "Other Important Settings."
                                                      I'm talking about putting on "pause" on the MSFS toolbar.
                                                      Kimi Häkkinen

                                                      Comment


                                                      • DDowns
                                                        DDowns commented
                                                        Editing a comment
                                                        I've got no idea what you are talking about... I don't think I've ever found anything on the toolbar to be useful.... LOL didn't know it had a pause. If you following the "important" recommendation in the Introduction you won't have a problem.

                                                      • LH201
                                                        LH201 commented
                                                        Editing a comment
                                                        I tried another flight today, following the pause options as per "Other Important Settings" and still got the autopilot misbehaviour after pause at T/D.
                                                        I will open a support ticket.
                                                    Working...
                                                    X