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

Texture problem with PMDG737-700.

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

    Texture problem with PMDG737-700.

    I have a problem with my PMDG 737-700
    After latest update, some parts of cockpit don't work and appear as pink color.
    A more accurate description is by the following screen shot.
    how can I fix it?
    Regards Max
    Attached Files

    #2
    This normally should never happen.
    Do you have any cockpit mods installed or liveries that come with cockpit mods?
    If not....does it happen with the PMDG liveries?
    Regards, Steve Dra
    Click here to download my P3D, FSX, 2004 paints at Avsim
    Get my paints for MSFS planes at flightsim.to here

    Comment


      #3
      Hi Steve Dra,
      yes, I tried another livery, without modifying anything and I have the same problem, but I haven't modified anything in the cockpit files.
      please explain to me where is the file and what I have to do to fix it if is possible
      Thanks
      Regards Max

      Comment


        #4
        Something went wrong during installation. The missing textures are used for every livery so changing it shouldn't fix it. Deinstall the plane and reinstall/update it again with admin rights.
        Liveries for P3D on https://flightsim.hpage.com/
        Liveries for MSFS on https://flightsim.to/profile/alxcpt/uploads

        Comment


          #5
          Hi Steve Dra,
          I'm sorry but I made multiple attempts to uninstall and reinstall the PMDG 737-700 when I install version 3.0.19 also with version 3.0.20 it worked with this latest update 3.0.30 it is not even seen but if I force it I can see it but all the glass parts such as windows and the inside of the cockpit can also be seen as in the photo. I ask you after this new info which file do you think I have to correct and in which voice? Thank you, Regards Max

          Comment


            #6
            Ehm... how did you get 3.0.30? Mine is 3.0.24. Probably there is the problem. All texture files for the cockpit are in within the Community folder in pmdg-aircraft-737\SimObjects\Airplanes\PMDG 737-700\texture.vc
            Liveries for P3D on https://flightsim.hpage.com/
            Liveries for MSFS on https://flightsim.to/profile/alxcpt/uploads

            Comment


              #7
              I'm sorry I misspelled the version lol...........now i try to see if i can solve i will let you know thanks for your help
              Regards Max

              Comment


                #8
                MEVM: Is this error present across all variants (PAX, BBJ,Cargo)? Or is it only to a specific livery you have added? For everyone else, isn't this error associated with an error within a .json file or a missing .json file?
                Rod Stagner

                Comment


                  #9

                  Hi RocketRod
                  Thanks for your help the problem I have only with my livery but I don't think I made any mistakes because from the first version to the second it worked perfectly now with this latest update it is not even recognized I don't know what or where to go to see this error

                  Comment


                    #10
                    Well I will tell you that I too, am working on my own livery and have had this. Here is what I have discovered. Missing or corrupted textures, errors in .json files (as simple a a space where there should not be one), missing lines in .json files. So don't take just because one works, the other should also. Your textures look like they might be some type mod. for the overhead panel.
                    Rod Stagner

                    Comment


                      #11
                      Hi Rod
                      I solved we went crazy as you also discovered it is the fault of the JSON take the JSON the original enter your data again of your livery and it should work I say should because I did this and now it worked perfectly thanks for your help I hope this that I wrote to you helps you to solve
                      Regards Max

                      Comment

                      Working...
                      X