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.
Was looking into this bug the other night and noticed that the bug didn’t seem to be there when using the ps3 emulator RPCS3. The gpu used the full range between 200mhz and 1040mhz. Was getting numbers in between these. Very strange but it may be just visual for some and cause performance issues for others.