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

747-8 Slaming down on runway at take off

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

    #31
    Hello to all. I had the same problem, trying to solve in many ways and no succes. Later I tried to change the setting of the joystick and problem solved. Change setting of null zone to absolute minimum, the higher setting of null zone, the more dead space for using the yoke.

    Jerry

    Comment


      #32
      Guys, thanks a lot on this topic, I had this issue on 737-900ER and even sometimes on -800 as well, every time I checked on Tacview record (kinda QAR if you may) I was far from tailstrike. And I can't test it reliably because it just doesn't happen when I try to replicate it at some of my test ground like KVPS and KEDW i normally use (everyone use KVPS, right? )

      After reading this and with some of my test, I can reliably turn it on/off with mesh resolution, 1m on that indeed trigger some jumping even before V1 on some scenery and this phenomenon, and at 10m it just gone. anything else I tried like reinstall / FSUIPC control set / Accufeel-LAND / ActiveSky / RealTrub etc etc doesn't matters...

      Now the problem is how can I make it work with some scenery requires less than 5m resolution
      Last edited by AngelofAttack; 22Jun2022, 16:06.
      ZHU Hai
      B737 Ground instructor

      Comment


        #33
        Originally posted by AngelofAttack View Post
        Guys, thanks a lot on this topic, I had this issue on 737-900ER and even sometimes on -800 as well, every time I checked on Tacview record (kinda QAR if you may) I was far from tailstrike. And I can't test it reliably because it just doesn't happen when I try to replicate it at some of my test ground like KVPS and KEDW i normally use (everyone use KVPS, right? )

        After reading this and with some of my test, I can reliably turn it on/off with mesh resolution, 1m on that indeed trigger some jumping even before V1 on some scenery and this phenomenon, and at 10m it just gone. anything else I tried like reinstall / FSUIPC control set / Accufeel-LAND / ActiveSky / RealTrub etc etc doesn't matters...

        Now the problem is how can I make it work with some scenery requires less than 5m resolution
        It seems that the mesh resolution is the cause of this behaviour, same during landing when the aircraft gets slammed onto the runway when there is a shore or similar just in front of the threshold.

        BUT: when I had this happen, all above the takeoff issue with the 747, I noticed that my stab trim would reset (not move by autopilot or a system but simply reset) to the value it is in when you load the default flight, running engines and so on. I‘m not sure about the value anymore but I believe it was 4 units? With the TO trim setting being in the 5.x region. Been a while. Bzt this can hardly only be due to the mesh settings. The interesting thing is that in my case it was resolved by deleting the FSUIPC.ini. I know, totally standard reply and I don‘t mean to point fingers at bad bad FSUIPC all the time, but something‘s always been a bit off with FSUIPC working with PMDG aircraft. And it seems this symptom continues with the MSFS version as well. I have always refused to set my mesh to 10m as a magic solution to be able to fly the 747 (into 5m airports 🙄), that‘s why I reply to you here. I feel it‘s nit (only) the mesh settings but I can‘t really say WHAT it is. I think it was Dan Downs who told me in this forum that LM had confirmed the issue? Or that it was a topic in their beta or something like that, don‘t recall anymore. Anyway, apparently there are ongoing issues with PMDG and FSUIPC in MSFS so maybe someone will eventually have to deal with it. FSUIPC has lost a lot of its popularity and I hope the issues won‘t become worse again. But IF is goes on this direction could be followed as well on search for a final solution. Can‘t be always the customer who has to sacrifice something in this pricey hobby.
        Ryzen 9 5900X, RX 6900XT, 32GB DDR4 RAM @3600MHz, 4k
        Marc Eland
        GFO Beta

        Comment


          #34
          Originally posted by Ephedrin View Post
          I‘m not sure about the value anymore but I believe it was 4 units?
          4 units for the 777 and 737, 6 units for the 747.
          Captain Kevin

          Kevin Yang

          Comment


          • Ephedrin
            Ephedrin commented
            Editing a comment
            Walking encyclopedia thanks ^^

          • Captain Kevin
            Captain Kevin commented
            Editing a comment
            I only know it because I configured my radio panel such that one window displays the trim, and I had to jerry rig it to display it correctly.

          #35
          It has been known for a long time that terrain mesh resolution is the source of this problem in P3D. The best that you can use to avoid the issue is 5m.
          Christopher Low

          Comment


          • AngelofAttack
            AngelofAttack commented
            Editing a comment
            I have never feel it on any other add-ons even the long one like A321, 757\763 or 747 from other developer....

          #36
          I think we all agree terrain mesh resolution is a causal element in this equation

          We also seem to be talking about two issues in this thread, take off and landing:

          Landing:
          - agree with Marc's point above about water boundary and that by Christopher. 5m resolution hasn't taken away the baulked landing issue at KSFO 28L/R or at NZAA (both flight beam, not that I blame them) - I just have to remember to land long or it's a mess. It happens on 744,748, 772 and 77W but not on the CS 767 or QW787

          Take off:
          - I've only seen the issue once, at Aerosoft EGLL 27R with a BA 744 at VR. It was not a tail strike - it happened at around 2 deg of pitch. I've never seen it before or after and I've not chased finding the root cause. The mesh was set at 5m and remained unchanged

          On the latter, I've got no other pattern of failure info to make an accurate statement on cause
          Adrian Howe

          Comment


          • Michael Codd
            Michael Codd commented
            Editing a comment
            Re: landing at KSFO on 28L/R.
            Although the P3D terrain mesh setting does appear to be the primary cause, it is also worth bearing in mind that PMDG have modelled the radio altimeters to behave realistically. Approaching these runways over water where the landing threshold is very close to the water’s edge is known to produce some rapid and very interesting ‘jumps’ in the readings and automatic call-outs in real life.

          • Extra300driver
            Extra300driver commented
            Editing a comment
            Yes I'd heard that (although the six axis BA sims didn't simulate it)

            My issue in P3D is landing on the aiming point or slightly before leads to a prang at some (not all) airports with a water surround. I think Haneda does it as well on 34L from memory
        Working...
        X