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

too tight lnav path

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

  • Maxxxii
    replied
    Yeah, thanks guys! Now I know more

    Leave a comment:


  • Max Rate
    replied
    By the way, I can confirm that without some kind of speed intervention (either entered into the FMC or by using the MCP), the aircraft flies that initial turn about 3 nm too wide, and completely botches the turn at LUX as well. The departure (RAPOR 7T at ELLX) doesn't have a speed restriction listed in the procedure, though, so the FMC doesn't know any better than to go to climb speed above 10000 feet. I-am-not-a-pilotâ„¢, but I'd say it's incumbent upon the crew to monitor the departure and to intervene if the aircraft in unable to maintain the published flight path.

    EDIT: yes, what Aeromar said.
    Last edited by Max Rate; 23Jun2022, 15:00.

    Leave a comment:


  • Aeromar
    replied
    Not exactly like this but in real life LNAV also has issues connecting points when the speed is too high. The real FMC would, in this case, create a discontinuity requiring the pilot to modify the speeds on the different points in the legs page. When this happens, we would enter a lower speed restriction and LNAV would connect again.

    On other types of procedures where you would see a INTC in the legs page, the airplane would simply turn to a certain heading or track (all while in LNAV) until intercepting a certain track inbound or outbound some other pseudo or a fix. This is not fully modelled in the PMDG but probably will once we get the LNAV update. Right now, all the PMDG does is try its best to fly from one point to some other point and then the next drawing somewhat of a bezier curve between the points taking expected groundspeed into account.

    Now, having said that, why the hell are you flying so fast? In a procedure like this one, where you'll spend some time flying not towards your destination, what you're interested in is climbing. You can type 210B/ at LUX and fly VNAV SPD, or you can fly VNAV SPD with SPD INTV 210kts of you can just fly LVL CHG 210kts. After LUX you can consider accelerating. We almost always fly slow during the initial turns on a departure not pointing to our destination. Usually, the faster you climb the sooner you'll get a direct (provided you've been granted unrestricted climb)
    Last edited by Aeromar; 23Jun2022, 14:59.

    Leave a comment:


  • Max Rate
    replied
    I'm flying that departure right now just to see what happened, because it seems rather improbable that you'd be up at 14000 feet already halfway through the initial turn. What ZFW and fuel load did you configure, and which climb thrust setting?

    Edit: never mind. A lightly laden 737 could make that climb easily.

    Last edited by Max Rate; 23Jun2022, 14:45.

    Leave a comment:


  • Maxxxii
    replied
    Thanks! But why PMDG don't set it in the FMC? Or it is impossible and all what we can do is use "spd intv"?

    Leave a comment:


  • Max Rate
    replied
    lux1.png

    lux2.png

    You're welcome.

    Leave a comment:


  • Maxxxii
    started a topic too tight lnav path

    too tight lnav path

    It is a bug or exist also in real aviation? image 1 - lnav path is too tight and aircraft can't carry it out. image 2 - aircraft wants to back to the correct path (by taking too hard turn) and can't do next turn
    Attached Files
Working...
X