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

STD to Baro profile jump

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

    STD to Baro profile jump

    Hi,

    Seems that the DES FORECAST Baro setting is not being taken into account when going from standard pressure to local QNH. The VNAV path jumps above or below, depending on which side of std the local pressure is.

    Does anyone know if a bug report has already been filed on this?

    Tero
    Tero Partanen

    #2
    Tero, if I remember, this was reported back in the P3D days.
    Captain Kevin

    Kevin Yang

    Comment


      #3
      Okay... well, anyway, the DES FORECAST baro setting is obsolete then, if the VNAV path calculation does not take this into account.
      Tero Partanen

      Comment


        #4
        I've seen it discussed before, but not sure if a ticket was raised.
        Itamar Mazor

        Comment


          #5
          It is known, the thing however is a bit more complex than just "it's not taking the altimeter setting on the forecast page into account".

          Comment


            #6
            Originally posted by imatams View Post
            I've seen it discussed before, but not sure if a ticket was raised.
            It's been reported.
            Tom Landry

            Comment


              #7
              Originally posted by Emi View Post
              It is known, the thing however is a bit more complex than just "it's not taking the altimeter setting on the forecast page into account".
              Of course it is more complex, as a function and under the hood. But for an end user, it's exactly like that. You input a BARO setting and it doesn't get reflected in the Path calculation.
              Is there a list of previously recorded items somewhere? Most likely not, but I ask anyway.

              On another note: do the TAI start/stop altitudes get reflected in the path calculation?

              Tero
              Tero Partanen

              Comment


                #8
                Originally posted by teropart View Post
                Of course it is more complex, as a function and under the hood. But for an end user, it's exactly like that. You input a BARO setting and it doesn't get reflected in the Path calculation.
                Is there a list of previously recorded items somewhere? Most likely not, but I ask anyway.
                Not publicly. If somebody submits a support ticket, stuff is getting tracked in their internal tracking system.
                Captain Kevin

                Kevin Yang

                Comment


                  #9
                  Originally posted by Captain Kevin View Post
                  Not publicly. If somebody submits a support ticket, stuff is getting tracked in their internal tracking system.
                  No need, it is in the bug tracking list.
                  René Moelaert EHLE

                  Comment


                    #10
                    Originally posted by Fleng200 View Post
                    No need, it is in the bug tracking list.
                    Sorry, I should have clarified that I was talking about in general, not specifically instructing anyone to do it for this particular case since the original question asked if there was a list of recorded issues somewhere. If an issue gets reported via support ticket, it's added to the bug tracking list, but it isn't public.
                    Captain Kevin

                    Kevin Yang

                    Comment


                      #11
                      Originally posted by teropart View Post

                      Of course it is more complex, as a function and under the hood. But for an end user, it's exactly like that. You input a BARO setting and it doesn't get reflected in the Path calculation.
                      Is there a list of previously recorded items somewhere? Most likely not, but I ask anyway.

                      On another note: do the TAI start/stop altitudes get reflected in the path calculation?

                      Tero
                      Well, just believe me when I say it's just not as simple and no, if that stuff was done 100% correct you'd see quite a bit more from it.

                      Of course the TAI altitudes are reflected in the profile.

                      Comment

                      Working...
                      X