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

PMDG 737 MSFS Completely Unusable

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

    PMDG 737 MSFS Completely Unusable

    My PMDG 737 for MSFS2020 is completely unusable. I've been using since the launch date working really good.

    Three days ago I had an outage that turned off my PC with Windows 10 and I was using MSFS2020 with the PMDG 737 in a flight at that moment.

    After that, any time I try to use the PMDG 737 with any library variant, the plane start on the desired runway, but like if it was in Cold and Dark state, all the screens in black and with all the panel buttons and the control completely unusable.

    Today I uninstalled all the PMDG 737 and reinstalled it but the issue is still there. Needless to say that MSFS2020 is working ok with the rest of the planes not PMDG (B787, piston ones, etc).

    Please give me some advice on what to do cause I'm really frustrated.


    Many Thanks!

    #2
    The shutdown has probably messed up your registration. Please go to support.pmdg.com and submit a support ticket so the team can get you back into the air. This is mainly a user forum and we can‘t do anything in this regard. I suppose you have never before submitted a ticket so you‘ll have to sign up for a support account at the support site.
    Ryzen 9 5900X, RX 6900XT, 32GB DDR4 RAM @3600MHz, 4k
    Marc Eland
    GFO Beta

    Comment


      #3
      First question, do you know how to startup the plane from cold & dark? If so, does nothing happen when you turn on the battery? Second, if you don't know how to turn on the plane from cold & dark you can click AND HOLD the menu button on the FMC (the flight management computer to the front and left of the throttles) until the FMC turns on. From there you can choose PMDG Setup I believe it is and look for Startup State and change it to another state.
      Peter Lucas

      Comment


        #4
        Marc, thanks for your recommendation. I'm oppening a ticket.
        Peter, thanks for your suggestion. It's completely unusable. Clicking and Hold Menu Button on FMS doen's do anything because nothing is working.

        Comment


          #5
          I'm having the same issue after reinstall of MSFS, I also submitted a ticket with this image attached. I was trying to run through the PDX to SFO tutorial but loading in on the runway is not working. Note yolk and throttles position locked although audio would indicate idle.2022-06-17.png
          Kind regards.
          Sam Stratton

          Comment


            #6
            Sam, this was my same issue and I had the Yoke exactly in the same position. I raised a ticket and they asked me to follow a simple procedure that solved completely my issue.

            In my case my MSFS 2020 is Microsoft Store Edition, and the procedure was for that type of installation. I don't know if it is exactly your case, but the procedure for my case was the following:

            1. Remove any installed liveries for the 737 from the Operations Center

            2. Uninstall the 737 from add/remove programs.

            3. Go too {SIM}\Community and make sure there is no pmdg-aircraft-737 folder. If there is delete it. Basically:
            3.a. Go to C:\Users\{username}\AppData\Local\Packages\Microso ft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packag es\Community\ and make sure there is no pmdg-aircraft-737 folder if there is delete it

            3.b. Go to C:\Users\{username}\AppData\Local\Packages\Microso ft.FlightSimulator_8wekyb3d8bbwe\LocalCache\SimObj ects\Airplanes and delete any PMDG 737-XXXXX folders if they exist

            3.c. Go to C:\Users\{username}\AppData\Local\Packages\Microso ft.FlightSimulator_8wekyb3d8bbwe\LocalCache\Packag es\ and make sure there is no pmdg-aircraft-737 folder if there is delete it.

            3.d. Go to C:\Users\{username}\AppData\Local\Packages\Microso ft.FlightSimulator_8wekyb3d8bbwe\LocalState\packag es and delete the PMDG-aircraft-737 directory

            5. Install again making sure you run the installer as administrator. Right click and select run as administrator.

            6. Rebbot the PC after the installation.


            My recommendation is to wait for the PMDG Support's anwers.


            Comment


              #7
              Thank you for this! I will wait for PMDG, Although they will probably give me these instructions, I'd rather not make it worse.
              Kind regards.
              Sam Stratton

              Comment


                #8
                Tech support sent me the same solution, which I performed and I'm back up and running
                Kind regards.
                Sam Stratton

                Comment


                  #9
                  I got the same issue, but no crash no nothing... Just started my Sim and nothing works, pretty annoying tbh. I'll give it a try, but how could this happen ?
                  Jörn Küster

                  Comment


                    #10
                    Originally posted by JK86K View Post
                    I got the same issue, but no crash no nothing... Just started my Sim and nothing works, pretty annoying tbh. I'll give it a try, but how could this happen ?
                    For some reasons the sim constantly destroys something within these files or something that it creates from these files. It‘s the same with the DC6 which leads to constantly popping circuit breakers and oil leaks there. The only thing that helps is a complete reinstall including manually deleting these files.
                    Ryzen 9 5900X, RX 6900XT, 32GB DDR4 RAM @3600MHz, 4k
                    Marc Eland
                    GFO Beta

                    Comment


                      #11
                      I had same problem and followed the steps posted ……..reinstalled and all ok now. Really appreciate this forum and the participants.
                      Joe Gilmore

                      Comment


                        #12
                        Originally posted by Ephedrin View Post

                        For some reasons the sim constantly destroys something within these files or something that it creates from these files.
                        Nonsense, If the SIM would randomly destroy config files a whole lot more people would have issues with a wide variety of planes, not just by PMDG.

                        So that usually leaves 4 culprits:
                        1) Terrible (configured) antivirus software, most 3rd party AV Software is not compatible with gaming, let alone flightsimming at all. I've seen in so many cases where an overzealous AV decides to remove or quarantine a file from a SIM product. This has led to more crashes, broken planes and airports than anything else i'd wager.
                        2) Data corruption during a write action caused by Software crash (Sim Crash/CTD).
                        3) Data corruption during a write action caused by Hardware, Driver or OS instability and/or power loss. This could technically happen to any process or file.
                        4) PMDG products have a flaw where it interfaces in a way with the sim that is not recommended/supported OR are prone to corruption due to point 2 and or 3.
                        Now this seems highly unlikely as i imagine we'd see way more complaints about broken 737's
                        Last edited by MarkusGX; 21Jun2022, 13:38.

                        Comment


                          #13
                          Originally posted by MarkusGX View Post

                          Nonsense, If the SIM would randomly destroy config files a whole lot more people would have issues with a wide variety of planes, not just by PMDG.

                          So that usually leaves 4 culprits:
                          1) Terrible (configured) antivirus software, most 3rd party AV Software is not compatible with gaming, let alone flightsimming at all. I've seen in so many cases where an overzealous AV decides to remove or quarantine a file from a SIM product. This has led to more crashes, broken planes and airports than anything else i'd wager.
                          2) Data corruption during a write action caused by Software crash (Sim Crash/CTD).
                          3) Data corruption during a write action caused by Hardware, Driver or OS instability and/or power loss. This could technically happen to any process or file.
                          4) PMDG products have a flaw where it interfaces in a way with the sim that is not recommended/supported OR are prone to corruption due to point 2 and or 3.
                          Now this seems highly unlikely as i imagine we'd see way more complaints about broken 737's
                          Actually there ARE quite a lot complaints about the 737 and DC6 not working correctly anymore. I personally have had this very problem (the aircraft going crazy and need to be deleted and reinstalled) with the DC6 after every (sim and world) update since SU6's hotfix. I haven't flown in MSFS much since SU9 so I can't say much about the 737. Usually it means that the circuit breakers in the DC6 pop one after each other every few seconds. You are right with that this only happens with the PMDG aircraft on my PC and I have only seen complaints and questions regarding this topic concerning PMDG aircraft but I don't follow other developers' forums or Discords, only the official MSFS forum. At the same time it‘s the only addon of mine that installs that complex way, all other addons I have only go into the community folder as far as I can tell. I don‘t have many aircraft addons though.

                          I also totally agree with the points you mention, they ARE the most common causes for issues. The problem is that except number 4 none of them make sense in my case.

                          1) I use the default Win Defender in default settings, nothing else has ever been installed on this PC. No third party AV, no malwarebytes, no 3rd party Firewall.
                          2) I‘ve had occasional CTD since SU8, not a single one before and I have never had a problem with the DC6 after one of these CTD but everytime I have updated the sim with SU, WU or Hotfix.
                          3) I can't sensibly argue with that but I have absolutely no problems with my PC otherwise.
                          4) To me it leaves the first part of your point 4 as the only probable cause. Either the PMDG has a flaw causing this or the PMDG addons install in a unique way the sim can't handle so that no other addons are affected, in line or not with the official documentation. I personally don't care whose fault it is and who needs to fix it, I grow increasingly tired of the constant developer ping pong, Asobo did this, PMDG missed that. I have payed a lot of money to both MS and to PMDG and I expect the products to be taken care of to work as intended. If I have to repair a lawn mower after every time I used it I return it, although it was the grass that changed, not the mower. Unfortunately this is not possible with registered software.
                          Ryzen 9 5900X, RX 6900XT, 32GB DDR4 RAM @3600MHz, 4k
                          Marc Eland
                          GFO Beta

                          Comment


                            #14
                            I am on Windows 10 and have all the updates for MSFS. Oddly enough I am not seeing any issues with the 737-700. However, I have not taken it on any long flights, maybe an hour or so. I do have everything controlled by SPAD.NEXT and disabled everything in the controls in MSFS. All the switches and knobs are working with SPAD.NEXT and I have very little addons. So maybe this is why I have been doing ok. I do usually create a image disk before a msfs update so I can restore it and try again if something goes wrong. I had to do that once before.
                            Last edited by dsalman1; 22Jun2022, 04:20.
                            Dean Salman

                            Comment

                            Working...
                            X