https://bugs.kde.org/show_bug.cgi?id=395632
--- Comment #50 from Kailash <kailash.sudha...@gmail.com> --- (In reply to Roman Gilg from comment #49) > (In reply to Benjamin Xiao from comment #48) > > (In reply to Roman Gilg from comment #45) > > > What would help me is if you guys would be on KWin master branch (for > > > example via KDE Neon dev unstable) to test upcoming patches. > > > > > > I have here an AMD RX470 and a 75Hz display but the monitor is probably > > > not > > > enough. I'm gonna look for some 144Hz display to buy. You are using AMD > > > graphics cards right? > > > > > > Does this mean you noticed low refresh rates on a laptop with high refresh > > > rate display and Intel graphics as well? > > > > I don't have a spare machine to put KDE Neon on, how possible would it be to > > apply patches to Kwin 5.16.4? I can definitely apply patches onto that > > version of KDE. > > It's difficult because I rewrote larger parts. I would not recommend it. If > you have some space on the HDD you can re-partition the disk and do a dual > boot on the same machine. In GRUB then your default boot entry could still > be Fedora. > > > Maybe try with the 75Hz display first and see if the issue exists there too? > > I think the issue will happen for anything above 60, but I could be wrong. > > Oh most likely it will happen. I assume it will just be less obvious to spot > with a 15Hz difference. And since the internal perf tools of KWin seem not > to be reliable just visual analysis could be needed. > > > Martin Floser was saying that if Painting blocks with vertical retrace is no > > then refresh rate is ignored, so I figured the issue would happen on Intel > > as well. I haven't done extensive testing on that yet. I've only done > > testing on AMD cards. > > Alright, if you could test it out would be great just to limit the problem > scope. I am on Arch Linux and can apply patches on top of kwin-git, I face this same issue on a Intel HD 530, what exactly do I need to do? -- You are receiving this mail because: You are watching all bug changes.
