When i started plasma on 4k resolution 200% scale, The desktop grid effect render in a very low fps, feels very laggy, But when i set my monitor in 1080p and then set it back to 4k, the fps grow a lot and animation looks great on the same monitor in same 4k resolution 200% scale *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Get a 4k monitor and scale 200% then reboot 2. Press super+w, very low fps 2. Set monitor to 1080p then set it back to 4k 3. Press super+w, fps looks pretty good OBSERVED RESULT Laggy animation , low fps EXPECTED RESULT High fps as i dont have to set resolution twice everytime when i boot up SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch linux, KDE plasma 5.27.8-1 (available in About System) KDE Plasma Version: KDE plasma 5.27.8-1 KDE Frameworks Version: plasma-framework5 5.111.0-1 Qt Version: qt5-base 5.15.11+kde+r138-1 ADDITIONAL INFORMATION
Created attachment 162517 [details] This effect needs me set my monitor resolution from 4k to 1080p then set it back to 4k everytime when i boot up
FYI i use i7-10510u + igpu + 16gb ram + 1tb ssd + mx150 and Arch + kde plasma + wayland
Does the same thing happen with the Overview effect (triggered via Meta+W)? I also have a 4K screen at 200% scale, and changing resolution to 1080p@100% and then back to 4k@200% does not fix the lagginess for me with Plasma 6.
(In reply to Nate Graham from comment #3) > Does the same thing happen with the Overview effect (triggered via Meta+W)? > > I also have a 4K screen at 200% scale, and changing resolution to 1080p@100% > and then back to 4k@200% does not fix the lagginess for me with Plasma 6. Sorry, It should be bootup with 1080p then set it to 4k@200%, My previous way was a mistake
I think the reason it is run better when bootup with 1080p then set it to 4k ,is that the effect still running in 1080p while the other apps are running in 4k, Is it possible there we have a option that set the effect resolution seprate from desktop resolution so we can trade effect resolution for better fps?
I can reproduce it now: - The effect is super smooth when booting at 1080p resolution - After changing to 4K resolution, the effect remains super smooth So the situation remains the same with the new combined Desktop Grid/Overview effect in Plasma 6. My theory is that the desktop itself is still internally at 1080p, and so the system doesn't have to work as hard to do the blur effect or something. I can see that the desktop wallpaper and the names of desktop files are visibly blurry.
(In reply to Nate Graham from comment #6) > I can reproduce it now: > - The effect is super smooth when booting at 1080p resolution > - After changing to 4K resolution, the effect remains super smooth > > So the situation remains the same with the new combined Desktop > Grid/Overview effect in Plasma 6. > > My theory is that the desktop itself is still internally at 1080p, and so > the system doesn't have to work as hard to do the blur effect or something. > I can see that the desktop wallpaper and the names of desktop files are > visibly blurry. Would you guys make this as a feature please? I really enjoy both smooth Overview effect and apps in 4k resolution, Desktop in 1080p with blurry file name is something im willing to trade off (Cause i dont have any file on desktop XD)
With all the performance work done on Overview recently, I can no longer reproduce the bug as I was able to before. Hooray!
Re-opening as I don't think we can quite call this fully fixed yet. There's still some frame drop when opening Overview with high resolution screens--the more of them there are, the worse it gets. It's already much better than when this bug was reported, but it's not perfect yet.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/kwin/-/merge_requests/4835
That was abandoned in favor of https://invent.kde.org/plasma/kwin/-/merge_requests/5041, which merged in its place.
With https://invent.kde.org/plasma/kwin/-/commit/51fb56773bdf4968646e4e9c5de100a1a62ea234 this is now greatly improved for me. With all the other changes recently. I feel more confident calling this fixed now.
(In reply to Nate Graham from comment #12) > With > https://invent.kde.org/plasma/kwin/-/commit/ > 51fb56773bdf4968646e4e9c5de100a1a62ea234 this is now greatly improved for > me. With all the other changes recently. I feel more confident calling this > fixed now. The performance has been greatly improved since the bug was reported, Thank you Nate, You are the hero!
Excellent! Note that I'm not the hero here: it's very much the KWin developers: Xaver Hugl, Vlad Zahorodnii, and David Edmundson, plus others. They're the ones who did the actual work here!
Thanks again for all of you guys, You guys are amazing!