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

"CHECK ALT TGT" in FMC after update

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

    "CHECK ALT TGT" in FMC after update

    Greetings,

    Recently after the latest updates I have a problem regarding with the FMC especially during descent. Im descending on VNAV with a VNAV PTH on. Everytime I put down the next lower altitude in the MCP it will shows CHECK ALT TGT. It mostly happens when im approaching the approach altitude before intercepting ILS. This problem also happened when Im doing RNP approach while on VNAV PTH. All of sudden it stops descending and again shows CHECK ALT TGT. All of this doesn't happened as I did in real life flying. Appreciate if this problem can be fix. Thanks.

    Joel Robert




    #2
    Same problem here. I have this issue especially during an arrival, and it doesn't matter if the target altitude in MCP is higher or lower than the VNAV altitude in the CDU, it will almost always tell CHECK ALT TGT when approaching that altitude.

    Giovanni Tarar
    Giovanni D. Tarar

    Comment


      #3
      Do you fly with panel states older than the latest updates? If so, it might be a corrupted panel state. This happens because there are variables that get changed to fix bugs but those variables have been saved with the panel state. Now they are used and the plane can‘t handle them correctly. Solution: load your plane with the default state (engines running) and save new panel states.
      i7-6700k, GTX 1080TI, 32GB DDR4 RAM @1600MHz, 4k

      Comment


        #4
        +1

        I had this on all flights after the updates.
        I delete all my own custom panel states after updating, and build new ones based on the default "Cold & Dark".
        Finn Jacobsen
        PC Spec.: i7 3770 3.4 Ghz, 16GB RAM, Nvidia GTX 960 4 GB, Windows 7 Home Edition

        Comment


          #5
          Originally posted by Wothan View Post
          I delete all my own custom panel states after updating, and build new ones based on the default "Cold & Dark".
          Did you try building new ones starting from the default engines running?
          Captain Kevin

          Kevin Yang

          Comment


            #6
            Nope.
            I can do so, but honestly it shouldn´t be necessary.
            Finn Jacobsen
            PC Spec.: i7 3770 3.4 Ghz, 16GB RAM, Nvidia GTX 960 4 GB, Windows 7 Home Edition

            Comment


              #7
              Originally posted by Wothan View Post
              Nope.
              I can do so, but honestly it shouldn´t be necessary.
              The problem with that line of thinking is that with the updates, they've incorporated fixes and possibly new features that may have changed things in the panel state, so if you're using an old panel state, the values inside them might no longer be invalid, and then you run into issues. Take the Boeing 747-400, for instance. At some point, ACARS was incorporated, which required new entries into the panel states that didn't exist before. Then changes were made to the ACARS that modified some of these entries. So how do you propose these new entries be added into old panel states.
              Captain Kevin

              Kevin Yang

              Comment


                #8
                Originally posted by Wothan View Post
                Nope.
                I can do so, but honestly it shouldn´t be necessary.
                No, it absolutely MUST be necessary. You had saved a situation where 2+3 equaled to 6... Now this was corrected and you need to update your save if you don't want to run 5=6.
                i7-6700k, GTX 1080TI, 32GB DDR4 RAM @1600MHz, 4k

                Comment


                  #9
                  I had this issue a couple of times and submitted it as a ticket and got this response from Chris:

                  I spoke with the VNAV developer. It seems that under certain conditions the NG will enter ALT HOLD instead of continue the VNAV descent. One of them is if the airspeed is above a certain value at 10000 feet which in this case it seems to be why this was done. He is going to refine the process of this for a future update. In mean time in such cases you can continue the descent either in V/S or FL Change
                  (assuming we're talking about the same thing)
                  Alex Pugh

                  Comment


                    #10
                    Pardon me but...

                    Those panel states are part of the PMDG install and those files where updated (file date: 25.12.2019) as part of the update.
                    So if they don´t work, then it´s a bug introduced with the update and not something I have normally would have to fix.
                    It´s Ok if these are bugs, but then it would be great to see som devs from PMDG confirming that.

                    If the solution for now, is to delete those and build new ones myself, then again i´s OK for me - all I want is an official confirmation from the PMDG guys.

                    I´m not talking about panel states I have created myself, but those delivered as part of the product - just to be clear.

                    Default files:
                    NGXu COLD DARK
                    NGXu LONG
                    NGXu SHORT
                    Last edited by Wothan; 01Jan2020, 22:24.
                    Finn Jacobsen
                    PC Spec.: i7 3770 3.4 Ghz, 16GB RAM, Nvidia GTX 960 4 GB, Windows 7 Home Edition

                    Comment


                      #11
                      Yes, I'm aware of that, but I have no idea if there are any issues with even those panel states. That's why I asked if you tried creating one from the default engines running state to eliminate this possibility.
                      Captain Kevin

                      Kevin Yang

                      Comment


                        #12
                        Originally posted by Captain Kevin View Post
                        Yes, I'm aware of that, but I have no idea if there are any issues with even those panel states. That's why I asked if you tried creating one from the default engines running state to eliminate this possibility.
                        Thanks Kevin.
                        I will try that and see if it fixes the problem.
                        Finn Jacobsen
                        PC Spec.: i7 3770 3.4 Ghz, 16GB RAM, Nvidia GTX 960 4 GB, Windows 7 Home Edition

                        Comment


                          #13
                          Hi guys,

                          Unfortunately save new panel state doesn't work for me. At first it works without a problem for my first flight. After restarting my P3D & trying to make a second & third flight, at the end of the approach altitude still indicates CHECK ALT TGT. Any solution?

                          Joel Robert

                          Comment


                            #14
                            This is known and fixed for the next update.
                            Chris Makris (Olympic260)
                            PMDG Technical Support
                            http://www.pmdg.com

                            Comment


                              #15
                              Thanks Chris. U guys are awesome. Looking forward for the fix.

                              Joel Robert

                              Comment


                                #16
                                Originally posted by cmakris View Post
                                This is known and fixed for the next update.
                                I did not see this addressed in the latest update today Changelog. Anyone know if the fix was included in today's update?

                                Thanks
                                Greg Clark

                                Comment


                                  #17
                                  Originally posted by GLC222 View Post

                                  I did not see this addressed in the latest update today Changelog. Anyone know if the fix was included in today's update?

                                  Thanks
                                  It has, is under another fix.
                                  Chris Makris (Olympic260)
                                  PMDG Technical Support
                                  http://www.pmdg.com

                                  Comment


                                    #18
                                    Thanks for rapid response Chris!
                                    Greg Clark

                                    Comment

                                    Working...
                                    X