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

Some questions regarding PMDG liveries

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Some questions regarding PMDG liveries

    Hello,

    I'm fairly new to livery making, but I've been practicing with the FBW A320 and Fenix A320. This has allowed to give me a better understanding of livery painting and how things work.

    However, today I started painting the MSFS 737-700BBJ SSW and I've noticed some differences.

    First of all, why do I need to include files that I haven't touched? For example F1_COMP, F1_ALBD and WINFR_ALBD & COMP. Not including those gives the infamous pink textures. The reason I'm asking is because the texture.cfg file is there just for that, to have fallbacks in case a certain file isn't included (thus saving on complexity and livery size). This has worked fine for the FBW and Fenix (and all other aircraft), but here things are different. This made it quite difficult to troubleshoot at first. Is there a particular reason for this?

    Second, I'm somewhat confused by all the PMDG_NG3_DECAL1_ALBD.PNG variations out there. It looks like every livery has its own variation of decals, which makes it hard for me to decide what would be a "normal/default" decals layout. I'm currently using the one that's included in the default livery (minus the references to PMDG). Is there even such a thing as the "correct" decals layout?

    Thirdly, it looks like an overwing exit frame is missing in the paintkit:
    Screenshot 2022-06-19 021035.png ​

    I've added it myself by copying the lower one, but maybe this can be fixed by PMDG?

    Lastly, it might be worth mentioning in the paintkit manual that you also need to have an .ini file in LocalState\packages\pmdg-aircraft-737\work for the OC2 Livery Export to work.​
    Tomas Hoste
    Tags: None
    #2
    You don't need to include the comp textures. Those along with the corresponding json files can be removed.
    Cheers,

    John Tavendale

    Comment

      #3
      Originally posted by John Tavendale View Post
      You don't need to include the comp textures. Those along with the corresponding json files can be removed.
      That’s what I was thinking as well but it still gave me the pink textures. I’ll try again tomorrow. You can apparently use also have to include the WINFR (window frames) or else you get a pink outline.
      Tomas Hoste

      Comment

        #4
        you get pink textures if you don't update the .json files after modifying the textures.
        Cheers,

        John Tavendale

        Comment

          #5
          Originally posted by John Tavendale View Post
          you get pink textures if you don't update the .json files after modifying the textures.
          I finally found what was causing it, it's simply 1 line missing in the default texture.cfg file. It's basically missing a fallback, and adding this does lead to having smaller file size liveries.
          Steve Dra apologies for tagging, but maybe worth mentioning to the higher ups?

          Take the BBJ SSW for example, this is the texture.cfg:
          fltsim
          fallback.1=..\..\PMDG 737-700\texture.vc
          fallback.2=..\..\PMDG 737-700BBJ\texture.BBJ
          fallback.3=..\..\PMDG 737-700\texture.common
          fallback.4=..\..\PMDG 737-700\texture.700
          But by adding ..\..\PMDG 737-700BBJ\texture.PMDGSSW as fallback.5 you don't have to add any of the fuselage COMP files if you didn't make any changes to them, same for the tail and WINFR files.
          Last edited by simtom; 22Jun2022, 16:25.
          Tomas Hoste

          Comment

            #6
            I've tried it. Actually works at least on the fuselage. But you have to use the BBJ COMPs even for the standard -700.
            fallback.5= ..\..\PMDG 737-700BBJ\texture.PMDGSSW or
            fallback.5= ..\..\PMDG 737-700BBJ\texture.PMDGBW
            depending on your version. That's because the default PMDG liveries (which COMP files should be used) have a metallic 737 on the fuselage. The tail COMPs aren't included in the liveries from the OC per default. The BBJ tail however has a PMDG logo on it, so you will see it, if no custom tail comp file is included.
            Last edited by Alx5; 23Jun2022, 18:34. Reason: Reviewed Textures: procedure works for the fuselage but not for the tail
            Liveries for P3D on https://flightsim.hpage.com/
            Liveries for MSFS on https://flightsim.to/profile/alxcpt/uploads
            • Likes 1

            Comment

              #7
              Originally posted by simtom View Post
              Thirdly, it looks like an overwing exit frame is missing in the paintkit:
              Screenshot 2022-06-19 021035.png ​
              This has been reported to PMDG by me.

              Tom Landry

              • Likes 1

              Comment

              • simtom
                #7.1
                simtom commented
                23Jun2022, 14:51
                Editing a comment
                Thanks Ralgh!
              #8
              Originally posted by simtom View Post

              I finally found what was causing it, it's simply 1 line missing in the default texture.cfg file. It's basically missing a fallback, and adding this does lead to having smaller file size liveries.
              Steve Dra apologies for tagging, but maybe worth mentioning to the higher ups?

              Take the BBJ SSW for example, this is the texture.cfg:


              But by adding ..\..\PMDG 737-700BBJ\texture.PMDGSSW as fallback.5 you don't have to add any of the fuselage COMP files if you didn't make any changes to them, same for the tail and WINFR files.
              I'm all for file size reduction and standardization...but we have to be very cautious...to the point of not touching the texture.cfg file....for the main reason: If there is an update from PMDG where they modify default "Common" folders and the like and change them slightly...it will flat-out break your liveries.

              With the advent of the internet speed being what it is compared to years ago when file size was a serious matter, in addition to the size itself taking up drive space now that we most have very large ones (by comparison of years back)....trying to save file size is not that big of a deal IMO....esp when you risk the potential of breaking your liveries.

              With that said....folks who attempt to make 8k liveries by upscaling the perfectly fine 4k textures...as is the current fad, are doing a disservice to everyone IMO because you do not see the impactful resolution gain when increasing the pixels16x from 4K to 8K (not doubled like some think). Unless you repaint all 67+ MILLION pixels on an 8k map, you're only making them bigger...not cleaner. Sure, you can now paint on it and see the detail, but MSFS is likely going to downscale anyway it if you don't have your settings maxed out.
              Anyway, off my 4k to 8k soapbox, LOL.

              Bottom line, I would highly recommend not altering the texture.cfg and pull any textures you want to edit into your main livery folder...the size increase will not be that great (relatively speaking) and it will ensure updates don't break your paints. Yes you have to grab the associated json's...but they are tiny 1-2k text files.
              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

              • simtom
                #8.1
                simtom commented
                23Jun2022, 15:40
                Editing a comment
                Fair enough.
              • Alx5
                #8.2
                Alx5 commented
                23Jun2022, 18:42
                Editing a comment
                In fact liveries for the 737 aren't that large. For me the file size differs between 50 and 70MB, when adding a custom cabin I get up to 100MB. That's for most of us no big deal with regard to download size/time and disc space. If PMDG would consider adding a default livery with standard values for roughness and metallic (only paint) the procedure of the OP would work even if the aircraft gets an update.
            Previous template Next
            Working...
            X