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

VNAV custom altitude crossings

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

    VNAV custom altitude crossings

    I encountered a problem with the 91.0041 build. I have submitted a ticket. So I will explain what happened. I was flying from KSFO to KEWR. The Williamsport 3 arrival has a few crossings at waypoints that are ATC assigned and not descend via into the STAR. I went to input crossing RACKI at 13K feet and my VNAV disconnected. The other waypoints speeds and altitudes went blank. I then inputted the crossing of SWEET at 7000. Everything was still blank. I deleted them and everything seemed to come back to order. I then tried to enter it a second time and that is when everything in the plane quit working basically. This picture shows you a lot of things weren't aligning up. The AP does not match the ND. Now I can go into detail what is wrong here but you can piece it together if you look at it enough. Basically the only thing that worked on the PFD was the speed below the tape in mach and the altitude. I am not sure about the compass at the bottom.Annotation 2019-12-25 150039.png
    Tim Barker
    FAA Air Traffic Control Specialist

    #2
    Strange indeed. Looks like a MCP failure of some sort. The FMA on the PFD should be always correct and trusted even though it is showing false data in your screenshot. In any case, revert to ANC, downgade one or two automation levels and continue flying.
    Bogdan Misko

    Comment


      #3
      You miss the point the whole plane does not function correct. Landing gear doesnt go down. Flaps do not go out. It is a bug not a failure.
      Tim Barker
      FAA Air Traffic Control Specialist

      Comment


        #4
        Let's see... The airspeed bug is on .77 mach and it looks like you're matching it but actual reads .71. VNAV is disengaged. You're 5.4 nm to the right of RNP "required" path. The magenta line is in draft mode. Both CDUs are in a precarious state, left one is toast. Your left ND arcs look to be set on 160, but arcs do not indicate any range on them. N2s and EGTs are out of sync. Both VORs are turned off.

        On a bright side, both engines are turning and you have plenty of gas I don't see any issues. Life is good!

        Comment


          #5
          This issue happens when an arrival runway is not selected yet. If you have an arrival runway selected you should not have an issue.
          Tim Barker
          FAA Air Traffic Control Specialist

          Comment


            #6
            Something similar happened to me on a flight right after updating. Took off from ESGG towards ESSA, switching AP on after passing 5000 ft, 2200 ft/min V/S, after 10000 ft switching to FL CHG mode, and passing FL240 plane starts to nosedive, instead of climbing, although vs shoved +2100 ft/min of vs, PFD froze, MCP also, I was just able to disconnect the AP. No movement of the yokes in the cockpit also. Yeah, I say it’s a bug.
            Ivan Majetic

            Comment


              #7
              I had a similar problem yesterday. Climbing from LDDU, I was expecting to level off at FL360. V/S decreased to about 400fpm as I was at about 358 but the plane passed the mark and continued to climb. My speed had also increased to about .83M from .78 and was continuing to rise. I quickly checked to make sure I didn't make some bone head mistake with the figures in the FMC, MCP, etc.... That's when I noticed that I was missing several displays on the FMC. There was no distance or Mach/FL listed in the LEGS page. Only the waypoints were displayed. The menu page didn't show the "<FMC" option but the LSK got me there anyway. Each FMC page I was switching to was showing less data each time I switched to it. I couldn't switch to a different MCP mode except that VNAV disconnected after the first button I pushed and wouldn't reengage. I completely missed a waypoint turn and watched as I continued to drift ever farther away from the magenta line without being able to switch into HDG SEL. I attempted to disengage/reengage AP without success so I restarted the sim and started over. Same thing. Everything was fine until I was approaching my target FL. Only the second time, I didn't overshoot FL360, I never got there. At about FL342, I got the bobing up and down thing (anyone remember those days? ) About a +/-1300 ft deviation from my selected FL. The FMC was doing the same thing as before and the MCP was pretty much useless.

              I restarted the sim again and this time I reset with another new panel state. So far, I've completed 3 problem free flights since.
              Erik Olson
              KPHX/KDVT

              Comment

              Working...
              X