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

Why does my 777 want to keep going back to FL400?

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

    Why does my 777 want to keep going back to FL400?

    Hi all,

    Here is an interesting case.

    I am in cruise while flying from CDG to YVR in the 777 and maintaining FL370. I encounter severe turbulence so I decide to climb to FL400 and later to FL420. VNAV was programmed to have the next step altitude be FL400.

    I deleted 400 from the LEGS and VNAV page and set the step size from RVSM to 0.

    Now my problem is that the plane, while in VNAV, wants to keep going back to FL400.

    I am using P3D V5.2.

    Any ideas what I am doing wrong here?

    Thank you.
    Yori Smulders

    #2
    What do you mean it wants to keep going back to 400. What altitude were you at when it was doing this. Any time I change altitudes, I just set the altitude in the MCP, then push the altitude knob to change altitudes. Not sure what exactly you were trying to do here, but it sounds like you made it more complex than it needed to be.
    Captain Kevin

    Kevin Yang

    Comment


      #3
      I was at 380 and did what you said but once I reached 400 and later 420 the plane would automatically reset the altitude to 400 and the plane started to climb or descent. All because the next altitude to climb to in the VNAV page was 400.

      Is there anyway to cancel the step climb in the VNAVpage?
      Yori Smulders

      Comment


        #4
        Yori,

        this sounds like the auto step climb feature is active in your Simulation settings in the CDU/PMDG options. I‘m not entirely sure why it happens although you set the step size to 0 but everything else points towards that setting. As Kevin said if you just dial in the new altitude in the MCP window and press the altitude rotary knob it should reset the VNAV/Cruise page with the new crz alt. There is no need to to that manually and as long as you don‘t allow the airplane to climb or descend by dialing in new altitudes it shouldn‘t change the flight level. What you dialed in the MCP is the cleared limit, it can‘t change it on its own. (Except by the sim setting „auto step climb“)

        another possibility: you don‘t have any virtual copilots active have you? FS2Crew, 3rd party ATC programs with assistant options, etc?
        i7-6700k, GTX 1080TI, 32GB DDR4 RAM @2666MHz, 4k
        Marc Ehnle

        Comment


          #5
          Originally posted by Yosm View Post
          Hi all,

          Here is an interesting case.

          I am in cruise while flying from CDG to YVR in the 777 and maintaining FL370. I encounter severe turbulence so I decide to climb to FL400 and later to FL420. VNAV was programmed to have the next step altitude be FL400.

          I deleted 400 from the LEGS and VNAV page and set the step size from RVSM to 0.

          Now my problem is that the plane, while in VNAV, wants to keep going back to FL400.

          I am using P3D V5.2.

          Any ideas what I am doing wrong here?

          Thank you.
          This problem has been reported a couple of times, and there could be something amiss. Not sure why the step was 3000 ft, non-RVSM? The VNAV is simply advising you that a step climb is expected, this does not mean you have to execute the step. Ignore it.

          If you desire, you can list all the steps taken to recreate the problem and submit a support ticket to make sure it is in the bug tracking system, but it probably will be not acted upon pending release of new FMS LNAV/VNAV code.
          Dan Downs KCRP
          i7-10700K 32GB 3600MHz 2080Ti

          Comment


            #6
            Originally posted by Ephedrin View Post
            Yori,

            this sounds like the auto step climb feature is active in your Simulation settings in the CDU/PMDG options. I‘m not entirely sure why it happens although you set the step size to 0 but everything else points towards that setting. As Kevin said if you just dial in the new altitude in the MCP window and press the altitude rotary knob it should reset the VNAV/Cruise page with the new crz alt. There is no need to to that manually and as long as you don‘t allow the airplane to climb or descend by dialing in new altitudes it shouldn‘t change the flight level. What you dialed in the MCP is the cleared limit, it can‘t change it on its own. (Except by the sim setting „auto step climb“)

            another possibility: you don‘t have any virtual copilots active have you? FS2Crew, 3rd party ATC programs with assistant options, etc?
            Hi Marc,

            Thank you for your thoughts.

            I just did both because only the MCP wasn't working.

            I do not have any virtual copilots active.

            Thanks

            Rgds,
            Yori Smulders

            Comment


              #7
              What's the box cruised at on the VNAV page?
              William Holland

              Comment


                #8
                Originally posted by Yosm View Post
                only the MCP wasn't working
                can you give more details ..... confusing to me
                cheers
                john martin

                Comment


                  #9
                  Just for your further information FL420 is not an assignable altitude. You can fly there but that requires a block altitude from ATC. The MCP was not allowing you to change the altitude or something?
                  Tim Barker
                  FAA Air Traffic Control Specialist

                  Comment


                    #10
                    Originally posted by vadriver View Post

                    can you give more details ..... confusing to me
                    What I mean is that setting the altitute in the MCP alone is not enough to keep the FMC from overwriting that command and keep climbing to a higher altitude. The only thing I can do is to set the FMC VNAV auto step climb setting to 0 instead of RVSM.
                    Yori Smulders

                    Comment


                      #11
                      Switch your RSVM to zero
                      Alex Kulak
                      PMDG Studier and flyer

                      Comment

                      Working...
                      X