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

737 Lifts Off Before V1

  • Filter
  • Time
  • Show
Clear All
new posts

    737 Lifts Off Before V1

    I'm not sure if related but it doesn't seem likely to be a coincidence. I purchased FSUIPC7 so I could map a custom flap axis which I did successfully. Right about that same time last week almost every takeoff results in the plane lifting off the runway before V1. V speeds are set, takeoff is derated, trim is properly set and I'm using flaps 5. This last flight had full passengers and 8.5T of not light.

    The plane also doesn't want to pitch up over 10-12 degrees where before it was pitching up to almost 20 and sometimes more. I have a button mapped to Toga if that has any relevance. I'm assuming that does the same action as the clickspot on MCP or at least it did prior to the above issues. FMA displays TO/GA as it's supposed to.

    Is there a known issue with FSUIPC7 and the 737 in MSFS that I'm not aware of that could be causing this behavior? Any other thoughts/ideas? It's almost like I'm setting flaps 5 and have 5 indicated but something in the background is setting flap 10 or more.

    Thanks in advance...

    Ryan Jackson

    I guess the first thing is to disable FSUIPC7 to prove this is causing it, but it does sound like you have messed up a setting/settings somewhere doesn't it.
    I've not really used FSUIPC7 myself, apart from it running in the background for some add-ons (FSUIPC7 works fine for me as is), but is there a reset option in it somewhere, or a save/restore option for settings?
    Steve Mel


      It’s a bug with FSUPIC and flap axis. I deleted fsuipc.ini and all is back to normal. My custom flap axis is working ok with out it so no big deal.

      Ryan Jackson


      • Steve M
        Steve M commented
        Editing a comment
        Glad you sorted it.

      PMDG flap axis and FSUIPC don‘t go well together. Been there, done that. P3D, MSFS, same procedure: don‘t assign the flaps to an axis via FSUIPC.

      FSUIPC will extend the flaps to 40 internally while the plane only shows flaps 5. You will be able to rise it completely with F5 but no intermediate setting.
      Ryzen 9 5900X, RX 6900XT, 32GB DDR4 RAM @3600MHz, 4k
      Marc Eland
      GFO Beta