That would be cool,cause I play games mostly in borderless fullscreen,but I hate it that I have to disable the compositor manually.
this can be done using window rules, albeit only on a per-application basis
(In reply to Nicolas Fella from comment #1) > this can be done using window rules, albeit only on a per-application basis What is "albeit"? And with "per application basis",do you mean that I have to use an env var for that?
> What is "albeit"? Basically a synonym for "however". > And with "per application basis",do you mean that I have to use an env var for that? He means you can set up window rules to do this in the Window Rules KCM in System Settings. Satisfying the desire for these kinds of niche use case is one of its primary functions, in fact.
*** Bug 435138 has been marked as a duplicate of this bug. ***
Wanting to disable the compositor in full-screen isn't the exception, but the rule. 95% of user cases. Nearly all full-screen applications can enable v-sync by themselves, preventing tearing when composition is off. And not having to render desktop effects actually makes a perceivable difference. The worst thing that happens by disabling composition while being in full-screen is not having shadows and animations in a desktop you aren't actually seeing. I would say that if the option "allow applications to block compositing" is on, kwin should assume that any full-screen window wants to block compositing. And perhaps only keep composition if the window has a rule for it. I would go further and say that this option alone is enough reason to favor kwin-lowlatency over the official kwin right now, as the first gives this option and has it enabled by default. They got it right.
I despise made up stats, it's also not remotely true, on my typical day-to-day my fullscreen apps are: - ksplash, kdevelop, lockscreen, and the logout greeter None of those are cases to disable compositing. >I would go further and say that this option alone is enough reason to favor kwin-lowlatency over the official kwin right now They don't disable compositing. It's fullscreen undirection which comes with it's own share of different problems
It should be the other way around, those applications explicitly requesting not to block composition. You are overlooking an important issue here.
My opinion is this design is amateuristic, and shows low compromise with quality. Having to disable all composition so only specific content is not composite, and that not being done automatically but explicitly by each application (won't happen). It is, at its best, a collection of ugly work-arounds. Windows 98 had lower input latency for gaming than 2021 Plasma. Perhaps in another 15 years you will figure it out.