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,

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

Autopilot problem

  • Filter
  • Time
  • Show
Clear All
new posts

    Autopilot problem

    I don't know if this is a bug or not
    I tested it several times to test auto landing.
    However, when I was almost approaching the runway, the autopilot turned off on its own.
    This has happened many times.
    I don't know if this is a bug or I'm doing something wrong.
    Kim young ju

    Quick question confirmation? You have both radios tuned to ILS both courses set to ILS appr course on left and right side and both CMD buttons engaged when auto landing?
    Aleks Matrosov


    • redsonssi
      redsonssi commented
      Editing a comment
      Yes, I did.

    Weird indeed. I haven't encountered yet. It's probably not your hardware since if it was spiking it would cause problems in cruise as well. Maybe post a short video of the problem while you waiting for a ticket response and maybe we can spot something in it.
    Aleks Matrosov


    • redsonssi
      redsonssi commented
      Editing a comment
      Thank you for your answer.
      I'll have to check it out again while watching the 737 class

    I'd recommend this. Make sure that in options menu in MSFS you turn on option Set MSFS LOC CRS. Then turn on Fail Operational on as well. For Autoland you need the following things setup in cockpit.
    1) Left and Right Radios tuned to ILS frequency as per chart
    2) Left and Right Course knobs on glareshield tuned to localizer course as per chart.
    3) CMDA CMD B buttons depressed.
    4) You need to make sure that you have captured the glide slop and localizer i.e. you pressed Approach button and the diamonds turned magenta.
    5) Approach speed and flap selection is plugged in into FMS.
    6) I'm not sure if Autoland logic is checking for speed brakes but make sure they are armed and not retracted or extended and flaps are at correct setting, again fuzzy if AL logic checks for those.
    Aleks Matrosov


      I had this too and it was an AI plane on the same approach so TCAS ?... The AP disconnected itself, not sure if it should have done.
      Last edited by chrisnoy; 22May2022, 06:13.
      Chris Noy


      • redsonssi
        redsonssi commented
        Editing a comment
        I see. Thank you for your answer.

      What does the FMA indicate at the A/P disconnect? And before that, one has to assume the PFD is indicating LAND2 or LAND3.

      Watch the GS raw data. Asobo has intentionally introduced a bug in the GS such that about 30-80 ft AAL it rises up abruptly and autopilot responds as if aircraft has exceed below glideslope safe limits. My guess is they did this because they are having problems getting their default airplanes to autoland and this bug forces those replicas of an airplane to start their flare. Sim pilots can complain all they want to Asobo but they don't care, they just want to make their xbox game crowd happy.
      Dan Downs KCRP
      i7-10700K 32GB 3600MHz 3080Ti


      • matrosov
        matrosov commented
        Editing a comment
        But PMDGs bird not using stock asobo behavior at all does it?

      • DDowns
        DDowns commented
        Editing a comment
        I don't know, just guessing since OP never shared complete info.

      • AndreH
        AndreH commented
        Editing a comment
        I'm guessing this is why I'm getting glideslope warnings close to the runway threshold even though I'm right on track on most, of not all landings?

      I have had about 30 autolands in the BBJ and haven't had any issues
      Are you by any chance hitting the trim button or moving the controls? I believe that will kick off the autopilot.