https://bugs.kde.org/show_bug.cgi?id=477016
--- Comment #37 from Zamundaaa <xaver.h...@kde.org> --- (In reply to AdamKafei from comment #35) > (In reply to Zamundaaa from comment #32) > >There is a way to tell the driver which > > parts of the image changed (and I think you can send an empty rectangle too) > > but I'll have to experiment with that to figure out how well it works / how > > much the drivers actually use that. > > Have you had any luck with this? Unfortunately PSR doesn't seem to be working on my laptop, so I haven't been able to test it properly. (In reply to Tim from comment #36) > As far as the VRR defaulting to 48hz, this behavior does not make sense to > me. 48hz is low and kind of defeats the point of having a monitor that can > do much higher refresh. If the GPU can do 240 FPS then the refresh needs to > follow the GPU in my opinion. With VRR off, Kwin debug and the FPS counter > on, we can see that on my system I getting around 230 FPS per its reporting > and is somewhat stable. Turning on VRR causes the FPS to tank and is all > over the place. If it is indeed to conserve power, why would it consume more > power than when it is off and doing an higher FPS? With these modern GPUs, > they can refresh a 2D desktop screen at max and not even break a sweat. There is no default refresh rate. When nothing changes, fps just goes down, that's how adaptive sync is meant to work. If you don't like it, don't use it. This is also not related to the bug report. -- You are receiving this mail because: You are watching all bug changes.
