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

Blurry display change with new NVIDIA DLSS

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

    Blurry display change with new NVIDIA DLSS

    Hi guys, now that I enabled the new Nvidia DLSS function inside FS2020 I am getting blurry displays when I change the speed, altitude, etc on the mcp.
    Also anything there is a change in the engine parameters etc it just becomse blurry as the numbers increase/decrease.
    Is this a normal behavior of DLSS on this aircraft? How can I sharpen it so it works as it was working with TAA? I had no issues with blurry numbers when increasing/decreasing.

    Teo
    Teofilo Homsany

    #2
    Same here...

    Steve Spicer
    Steve Spicer

    Comment


      #3
      From what I read on the various forums, this is a general issue with glass panels and DLSS. I see no performance advantage with DLSS vs TAA using the latest nVidia driver and so have lost interest. It appears that nVidia now claims that their new DLSS 3 actually provides a large performance upgrade, but that seems to require a 4xxx GPU card.
      John Wiesenfeld - KPBI
      PPL/IFR, VATSIM C1 (ZNY)

      Comment


        #4
        Same here, I came to the forums just to check this out
        Francesco Tondelli

        Comment


          #5
          Originally posted by citation79 View Post
          Hi guys, now that I enabled the new Nvidia DLSS function inside FS2020 I am getting blurry displays when I change the speed, altitude, etc on the mcp.
          Also anything there is a change in the engine parameters etc it just becomse blurry as the numbers increase/decrease.
          Is this a normal behavior of DLSS on this aircraft? How can I sharpen it so it works as it was working with TAA? I had no issues with blurry numbers when increasing/decreasing.

          Teo
          This actually works pretty well:

          https://forums.flightsimulator.com/t...ve-dlss/543857
          Mike Murphy
          Commercial, Instrument, Rotorcraft-Helicopter

          Comment


          • Steve M
            Steve M commented
            Editing a comment
            Anyone who is using 1080, be aware this will while improving visuals, actually lower your frame rate at the same time.
            Not an issue if you have a system that is already giving more FPS than you need, but for anyone who is already borderline in 1080 resolution, better to not use DLSS at all.
            Possibly when DX12 is not a beta, and with new drivers, things might change in the future.

          #6
          This is a known issue that was brought up during the beta - Asobo has acknowledged it. They are hoping to implement masks that will mask out the displays so that DLSS is not applied to them. They have not given a timeline for implementing this.
          Charles Vomacka

          Comment


            #7
            As others have said many have noted the issue with gauges. Aside from possible future Asobo development, nobody in the general community has seen the new NVidia driver that seems likely to change the behavior of DLSS. That is supposed to be out any time now, so I'd probably take another look once it is released.

            From the reviews of DLSS so far it sounds like Quality mode is the only one worth using as the others substantially degrade appearance and probably are no better than just turning down the resolution/settings/etc.

            I'm definitely hopeful that DLSS improves 4k performance for me as I have definitely had a quality impact when I moved to a 4k monitor. I guess I could always render in 1440p instead, but once the new driver is out I'll try taking a look to see if anything has gotten better.

            The new info on DLSS v3 sounds interesting, though I've seen speculation that it will increase latency, and since it works by using AI to predict frames, I'm not sure how well that is going to work with something like a glass cockpit, since obviously you can't predictively render something like text the way you'd render an object flying across the screen. Reviews will tell all I'm sure, and I'll probably wait for some before I go and buy something like a 4090. (The MSFS benchmarks they showed off were for DLSS performance mode, which is already pretty lousy.)
            Richard Freeman

            Comment


            • PositiveZero
              PositiveZero commented
              Editing a comment
              I thought the pending driver release from Nvidia was to correct the artifact bug in DX12 that was discovered during the beta. Not sure that it will address the DLSS issue.

            • Steve M
              Steve M commented
              Editing a comment
              Actually, DX12 itself is still just a beta, and so things are not yet finalized.
              Who knows what effect that will have when it is finally finished?
              All we can do is live in hope...
          Working...
          X