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

Loss of FPS on P3D 5.2

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

    Loss of FPS on P3D 5.2

    Hi guys,
    Hope all is well.
    I know PMDG is not yet supporting P3D v.5.2 but I was wondering if any of you have had issues with low FPS on the latest version.
    My PMDG products work ok without issues but I get heavy FPS loss as soon as I start taxiing/flying.
    Anyone else having this issue?
    Thanks!
    Teofilo Homsany

    #2
    Hi,
    Please try this
    1. Delete any shader utilities/addons (like envshade)
    2. Delete your shaders folder (Usually in C:\Users"name"\AppData\Local\Lockheed Martin\Prepar3D v5)
    3. Delete your Shadershlsl folder (P3D root folder)
    4. Reinstall P3D 5.2 Client.

    Comment


      #3
      Originally posted by snapshot21 View Post
      Hi,
      Please try this
      1. Delete any shader utilities/addons (like envshade)
      2. Delete your shaders folder (Usually in C:\Users"name"\AppData\Local\Lockheed Martin\Prepar3D v5)
      3. Delete your Shadershlsl folder (P3D root folder)
      4. Reinstall P3D 5.2 Client.
      Just did it, will test and see if it helps.
      Also I don't use Envshade nor any of that, just vanilla P3D.
      I removed and installed the client, content and scenery last time but will reinstall the client.
      Last edited by citation79; 11Jun2021, 03:17.
      Teofilo Homsany

      Comment


        #4
        Looks like deleting the ShadersHLSL folder did the trick.
        Already tried the other shader folder and didn't help. Now it seems to be smooth.

        Thanks!!!
        Teofilo Homsany

        Comment


        • snapshot21
          snapshot21 commented
          Editing a comment
          Glad it did the trick enjoy!

        • HiImSmalls
          HiImSmalls commented
          Editing a comment
          Helped me too! Lost 10-15 FPS depending on the situation before this, back at FPS cap now. Many thanks.

        #5
        For me, I noticed FPS went to single digits, so I uninstalled the 5.2 client, deleted the Shaders folder, reinstalled the 5.2 client, and got my FPS back to normal.
        Luis Linares
        i9-6700K, GTX 2080Ti, 64GB DDR4

        Comment


          #6
          Danymic lights are much brighter in P3D. As a result the FPS impact is much more significant and PMDG will need to adjust accordingly to achieve the same performance impact in v5.1 HF1
          Leo Cal

          Comment


            #7
            Originally posted by Calzonister View Post
            Danymic lights are much brighter in P3D. As a result the FPS impact is much more significant and PMDG will need to adjust accordingly to achieve the same performance impact in v5.1 HF1
            Can you elaborate? We do not plane to do any updates specific to 5.2 as we do not see any issues with current products as it is.
            Chris Makris (Olympic260)
            PMDG Technical Support
            http://www.pmdg.com

            Comment


              #8
              Hello guys

              Rainmaker not working in 5.2

              Jose Zubillaga

              Comment


                #9
                After updating to 5.2 flying in NGX was impossible, even with full p3d reinstall, cleared shaders, deleted generated files... Stutter fest on taxing, takeoff and landing, just ridiculous. Decided to nuke my system and will try from scratch and see it is makes any difference.
                Ivan Majetic

                Comment


                • snapshot21
                  snapshot21 commented
                  Editing a comment
                  did you delete just the shaders folder? and not the shadershlsl folder in P3D root directory?

                • Ivan.majetic
                  Ivan.majetic commented
                  Editing a comment
                  snapshot21 I did, and a few times after the reinstall to be more precise. Something was wrong with the install, or with some addon causing massive stuttering.

                #10
                i reinstalled, delete all and begin the zero and very much Stutterts 😭
                Jose Zubillaga

                Comment


                  #11
                  Originally posted by cmakris View Post

                  Can you elaborate? We do not plane to do any updates specific to 5.2 as we do not see any issues with current products as it is.
                  Hi Chris, v5.2 shaders were significantly changed (as has happened with each recent v0.1 update).
                  As a consequence darkness conditions are ~50% ‘brighter’ than it was in V5.1 HF1. The same .fx dynamic light results in a 50% brighter rendering in v5.2

                  If you turn on all the forward facing lights on the -400/-8 sitting on a runway the resultant GPU loading (when turning on the dynamic lights) is about 50% greater than it was in V5.1 HF1. Brother the lights the more rendering the PGU needs to do.

                  Simply put they don’t need to be as bright as they were in V5.1 HF1. Keeping them as is simply results in a greater GPU load than it did in v5.1 HF1

                  It would be greatly appreciated if someone from the team could tweak the associated .fx files for QOTS II/NGXu/B777 to adjust for V5.2.

                  Last edited by Calzonister; 12Jun2021, 02:01.
                  Leo Cal

                  Comment


                  • Wise87
                    Wise87 commented
                    Editing a comment
                    Your the first I heard of reporting the lights be so bright. This might be specific to your system. If they turn them down as you requested how will that effect those still on 5.1? Lots of folks are in no rush to update to 5.2 as their sims are running great and many programs haven’t been updated yet.
                    Last edited by Wise87; 12Jun2021, 13:25.

                  • Calzonister
                    Calzonister commented
                    Editing a comment
                    Adjusting the lights to appear properly in V5.2, and thereby also ensuring they don’t have a worse performance impact than they did in V5.1 HF1 would of course result in a dimmer dimmer light in V5.1 HF1

                    As mentioned above, the night environment shaders were approximately 50% darker in v5.1 HF1 than they are now in v5.2. As a result every dynamic light is equally brighter and the brighter a dynamic light appears in P3D, the more resource intensive it is!

                    The argument of holding a product back to support older versions of a simulator has been beaten to death and is absolutely pointless. As the simulator progresses so should and will products. Onwards and upwards!
                    Last edited by Calzonister; 12Jun2021, 20:39.

                  #12
                  Deleted the shaders folder, reinstalled 5.2 client and content, and also noticing a bit of a performance drop here. Not as bad in the 777, but then again that doesnt have a PBR cockpit. The darker cockpit issue seems to be uniform across the board due to shader changes in 5.2
                  -Spencer Hoefer

                  Comment


                    #13
                    Originally posted by Calzonister View Post

                    Hi Chris, v5.2 shaders were significantly changed (as has happened with each recent v0.1 update).
                    As a consequence darkness conditions are ~50% ‘brighter’ than it was in V5.1 HF1. The same .fx dynamic light results in a 50% brighter rendering in v5.2

                    If you turn on all the forward facing lights on the -400/-8 sitting on a runway the resultant GPU loading (when turning on the dynamic lights) is about 50% greater than it was in V5.1 HF1. Brother the lights the more rendering the PGU needs to do.

                    Simply put they don’t need to be as bright as they were in V5.1 HF1. Keeping them as is simply results in a greater GPU load than it did in v5.1 HF1

                    It would be greatly appreciated if someone from the team could tweak the associated .fx files for QOTS II/NGXu/B777 to adjust for V5.2.
                    5.2 seems to have HDR enabled by default. This can cause what you see. You can disable HDR from the cfg and this should make them same as before
                    Chris Makris (Olympic260)
                    PMDG Technical Support
                    http://www.pmdg.com

                    Comment


                      #14
                      Originally posted by cmakris View Post

                      5.2 seems to have HDR enabled by default. This can cause what you see. You can disable HDR from the cfg and this should make them same as before
                      I did not use HDR in v5.1 HF1 and I dont use it in v5.2

                      The easiest way to test this is to run v5.1 and make note of both the darkness the GPU load (in a scenario as previously described) and then try the same in v5.2 and you will easily see how much brighter it is at night. The stronger and more visible dynamic lights are the more GPU rendering and load occurs.
                      Leo Cal

                      Comment


                        #15
                        Originally posted by Calzonister View Post

                        I did not use HDR in v5.1 HF1 and I dont use it in v5.2

                        The easiest way to test this is to run v5.1 and make note of both the darkness the GPU load (in a scenario as previously described) and then try the same in v5.2 and you will easily see how much brighter it is at night. The stronger and more visible dynamic lights are the more GPU rendering and load occurs.
                        Leo,

                        Even if you do not use it, it is enabled an operating by default on 5.2
                        Chris Makris (Olympic260)
                        PMDG Technical Support
                        http://www.pmdg.com

                        Comment


                          #16
                          Originally posted by cmakris View Post

                          Leo,

                          Even if you do not use it, it is enabled an operating by default on 5.2
                          Chris,

                          HDR is only enabled by default (and cannot be disabled) if Enhanced Atmosphere (EA) is enabled.

                          I don’t use Enhanced Armosphere, and therefore I can can and have disable HDR. This is unchanged from V5.1
                          Leo Cal

                          Comment


                            #17
                            Originally posted by Calzonister View Post

                            Chris,

                            HDR is only enabled by default (and cannot be disabled) if Enhanced Atmosphere (EA) is enabled.
                            So this work around no longer works? To disable HDR when EA is on you will have to modify HDR=1 to HDR=0 in prepar3d.cfg
                            Dan Moore

                            Comment


                              #18
                              Could someone let me know, the cockpit was already pretty dark in 5.1, is it now darker in 5.2!?

                              Also, am I to understand that official advice from PMDG is to not use HDR? Thanks.
                              Mr. James Alexander.

                              Comment


                                #19
                                Originally posted by severniae View Post
                                Could someone let me know, the cockpit was already pretty dark in 5.1, is it now darker in 5.2!?

                                Also, am I to understand that official advice from PMDG is to not use HDR? Thanks.
                                It's not an official advise. I just said that it can be disabled if someone does not like the effects of it
                                Chris Makris (Olympic260)
                                PMDG Technical Support
                                http://www.pmdg.com

                                Comment


                                  #20
                                  Originally posted by severniae View Post
                                  Could someone let me know, the cockpit was already pretty dark in 5.1, is it now darker in 5.2!?

                                  Also, am I to understand that official advice from PMDG is to not use HDR? Thanks.
                                  When EA is ON disabling HDR in V5.1 via the .cfg does not actually disable HDR. EA requires HDR to function and that is why LM removed the option to disable the latter when EA is ON.

                                  As P3D developer Beau Hollis outlined:

                                  ”We decided to always enable HDR when Enhanced Atmospherics is enabled because the the techniques used for rendering clouds and the more physically based values used for sun/moon light intensity need an HDR image buffer to work properly. You can disable the bloom and auto-exposure options which will reduce the GPU work and visual impact of the HDR effect.”
                                  Leo Cal

                                  Comment


                                    #21
                                    Originally posted by cmakris View Post

                                    It's not an official advise. I just said that it can be disabled if someone does not like the effects of it
                                    I'd had some oddities so wondered if there was some incompatibility. Thanks for clearing it up (suspect the issue is my system itself!).
                                    Mr. James Alexander.

                                    Comment


                                      #22
                                      I tested trick with HDR=0 in the .cfg file and successfully in P3Dv5.2 EA on with legacy clouds :
                                      EA off, HDR off :



                                      EA on, in the .cfg HDR=0 :



                                      and EA on, HDR=1 in the .cfg

                                      Last edited by Rado Sutto; 16Jun2021, 16:05.

                                      Comment


                                        #23
                                        The thing is, all addons look like that in V5. LM simply broke the lighting/PBR making the dymanic range super bad and almost all cockpits appear super dark. Your best bet is EA and HDR off if you want a more realistic and less "gamey" or cinematic look.
                                        Bogdan Misko

                                        Comment

                                        Working...
                                        X