On github Valve employee was denying bug, telling people that it’s only bug in performance overlay (like it simply slow to draw frequencies in between 200-1040) but was proven wrong in the same bug report thread. Demonstration of this bug presented here.

I just tested it myself and you still get major performance issues with gpu set to auto. “Allow tearing” setting has no effect on this. Even if game can go above 1040 mhz by itself it drop frequencies and frames hard on auto because occasionally it switches to 200 mhz or 1040 in scenes where it should not do that.For example Code Vein is not able to hold stable 60 FPS but able to hold stable 50, with locked GPU you will get flat line on frame time graph. With auto you will get major dips.

I guess we’re stuck with “unstable” stable OS 3.5.5 - 3.5.7 for a while because holidays starting in US.

  • akane9@alien.topB
    link
    fedilink
    English
    arrow-up
    1
    ·
    10 months ago

    I think there are two bugs here we are associating together in error.

    1. Steam OS fails to properly balance power between the GPU and CPU, when the GPU is left to auto clock. Some games are effected by this more than others. This issue seemed to me to exist in 3.4 as well.
    2. New to 3.5. Now when the GPU is clocked at or below 1040, instead of reporting the right frequency. SOMETIMES, it reports in intervals of 200 and 1040 instead.

    These are my observations on my deck. I may be off base but I think I’m at least close here.

    • Mervium@alien.topB
      link
      fedilink
      English
      arrow-up
      1
      ·
      10 months ago

      If it were a reporting ossue, shouldn’t it still occur when fo4cing the GOU to a frequency between those two values? If you do that, it shows the number you set it to.

      • akane9@alien.topB
        link
        fedilink
        English
        arrow-up
        1
        ·
        10 months ago

        Not necessarily. If you force your GPU clock to 200 mhz, do you ever get frame rate dips as low as those settings produce? If not, I think it’s safe to assume you GPU isn’t actually operating at that clock speed. Also I found this post from a YEAR ago that is talking about issue number 1 and how manual settings must be used to achieve the best frame rates. I am very confident these are two separate issues.

        https://www.reddit.com/r/SteamDeck/s/3BOuWPyzeM