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.

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

    Taken directly from the steam community

    "Note: To revert back, you need to have updated from 3.4.x directly to 3.5.x, no in between.

    When shut down, press the 3 dot menu, then press the Power button. Let go of the Power button, keep the 3 dot button pressed.

    You will be presented with a new boot menu, choose “Previous A”

    you need to do one step more at the end, because if you don’t do it, the moment you shutdown or restart your deck, its going to go back to the 3.5.5, so , in order to avoid that, you need to tell the system that the current BOOT/IMAGE is the priority, and for that, you just have to execute this command in the konsole from the desktop (you will need to create a sudo password before):

    sudo rauc status mark-active booted

    That way you will keep the current boot/so version even after a shutdown.