https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #59 from Blazer Silving ---
(In reply to Brandon Wright from comment #58)
> You're missing the
> #include
> line. FYI The use of Qt private API is the only reason why this patch is in
> any way controversial.
Thanks, fixed! To note, is a
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #58 from Brandon Wright ---
You're missing the
#include
line. FYI The use of Qt private API is the only reason why this patch is in any
way controversial.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #57 from Blazer Silving ---
(In reply to Brandon Wright from comment #54)
> (In reply to Blazer Silving from comment #53)
> > Brandon, do you have a KDE Invent account? I can create a merge request
> > upstream, but I want to ensure you rece
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #56 from Bug Janitor Service ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/kwin-x11/-/merge_requests/68
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485927
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #55 from Bug Janitor
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #54 from Brandon Wright ---
(In reply to Blazer Silving from comment #53)
> Brandon, do you have a KDE Invent account? I can create a merge request
> upstream, but I want to ensure you receive credit for the fix. I don't think
> anyone else
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #53 from Blazer Silving ---
(In reply to Brandon Wright from comment #51)
> Could we get attachment 180290 [details], "Patch using private API to update
> scene graph timers when window refreshed 2" added in for kwin 6.4? Aside
> from using
https://bugs.kde.org/show_bug.cgi?id=485927
hf...@hotmail.com changed:
What|Removed |Added
CC||hf...@hotmail.com
--- Comment #52 from hf...
https://bugs.kde.org/show_bug.cgi?id=485927
Timothy B changed:
What|Removed |Added
CC||yule2...@live.com
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=485927
Kuro changed:
What|Removed |Added
CC||kuro...@foxmail.com
--
You are receiving this mail beca
https://bugs.kde.org/show_bug.cgi?id=485927
Lars Veldscholte changed:
What|Removed |Added
CC||l...@tuxplace.nl
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=485927
Shibi J M changed:
What|Removed |Added
CC||shibi...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=485927
Andrey Khanov changed:
What|Removed |Added
CC||avkha...@gmail.com
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #51 from Brandon Wright ---
Could we get attachment 180290, "Patch using private API to update scene graph
timers when window refreshed 2" added in for kwin 6.4? Aside from using private
API, which kwin already does in that file, it's the si
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #50 from Merkurio ---
(In reply to Zamundaaa from comment #28)
> (In reply to Merkurio from comment #27)
> > At 120Hz, I don't have major issues, but as soon as I switch to 240Hz, the
> > whole system feels like it's running at 60Hz (I even
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #49 from Brandon Wright ---
(In reply to Brandon Wright from comment #48)
> Created attachment 180356 [details]
> Patch using public API and setting interval to lowest refresh rate on hotplug
>
> Here's a better patch that might be of appro
https://bugs.kde.org/show_bug.cgi?id=485927
Brandon Wright changed:
What|Removed |Added
Attachment #180293|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #42 from Brandon Wright ---
Created attachment 180257
--> https://bugs.kde.org/attachment.cgi?id=180257&action=edit
Patch using private API to update scene graph timers when window refreshed
I've attached a patch for kwin that uses the pr
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #47 from Brandon Wright ---
Created attachment 180293
--> https://bugs.kde.org/attachment.cgi?id=180293&action=edit
Patch using public API and setting interval to 4ms
Here's a patch using the public QAnimationDriver API and using it to se
https://bugs.kde.org/show_bug.cgi?id=485927
Brandon Wright changed:
What|Removed |Added
Attachment #180257|0 |1
is obsolete|
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #45 from David Edmundson ---
>I'm also wondering whether other components using QtQuick would need changes.
Most others are fine. If you're using threaded rendering (which is the default)
you get a custom animation driver provided by QSGGui
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #44 from Brandon Wright ---
(In reply to David Edmundson from comment #43)
> >The presumably sanctioned alternative is to inherit QAnimationDriver and use
> >the install() method, which replaces the global animation driver.
>
> Yeah, that'
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #43 from David Edmundson ---
>The presumably sanctioned alternative is to inherit QAnimationDriver and use
>the install() method, which replaces the global animation driver.
Yeah, that's what I had in #24, though it seemed that got lost in
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #41 from Brandon Wright ---
Sticking
QUnifiedTimer::instance(false)->updateAnimationTimers(); at the beginning of
OffscreenQuickView::update()
is probably the wanted behavior.
--
You are receiving this mail because:
You are watching all bu
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #39 from Brandon Wright ---
Ok, here's a hacky example of how to fix it:
> diff --git a/src/effect/offscreenquickview.cpp
> b/src/effect/offscreenquickview.cpp
> index 3dc83f9b2e..44ed0e8eae 100644
> --- a/src/effect/offscreenquickview.cpp
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #40 from Brandon Wright ---
I didn't notice the overload on instance() which lets you keep the current, so
here's a better version using the private API:
> diff --git a/src/effect/offscreenquickview.cpp
> b/src/effect/offscreenquickview.cpp
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #38 from Zamundaaa ---
hmm right, QQuickRenderControl that we do use doesn't seem to have equivalent
logic.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #37 from David Edmundson ---
>QSGRenderThread::syncAndRender advances the animation driver every time right
>before rendering, afaict that is not throttled below the display refresh rate.
KWin won't use that.
Kwin *currently at least* onl
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #36 from Brandon Wright ---
I looked into it further, and most of what Zamundaaa says is correct, except
this:
> this happens when KWin tells Qt to render the window.
The only time that syncAndRender is called is directly from the render lo
https://bugs.kde.org/show_bug.cgi?id=485927
madness...@proton.me changed:
What|Removed |Added
CC||madness...@proton.me
--
You are receivin
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #35 from Brandon Wright ---
(In reply to Zamundaaa from comment #34)
> There's nothing to be public, this happens when KWin tells Qt to render the
> window.
It definitely says it's supposed to, but that doesn't seem to be true. I traced
the
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #34 from Zamundaaa ---
There's nothing to be public, this happens when KWin tells Qt to render the
window.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485927
Nate Graham changed:
What|Removed |Added
CC||zupnikszyd...@gmail.com
--- Comment #23 from Nate
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #25 from Blazer Silving ---
(In reply to David Edmundson from comment #24)
> Blazer, can you try cherry-picking the commit from:
> work/d_ed/animation_driver in kwin.
>
> I wrote it ages ago, when looking into the same issue, but it all loo
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #32 from Zamundaaa ---
(In reply to Brandon Wright from comment #22)
> I've been trying to investigate this a bit, and here are some findings:
>
> In qabstractanimation.cpp:
>
> 1. QUnifiedTimer isn't actually used directly in this case. I
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #33 from Brandon Wright ---
(In reply to Zamundaaa from comment #32)
> (In reply to Brandon Wright from comment #22)
> > I've been trying to investigate this a bit, and here are some findings:
> >
> > In qabstractanimation.cpp:
> >
> > 1.
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #31 from Brandon Wright ---
(In reply to Brandon Wright from comment #30)
> (In reply to Blazer Silving from comment #29)
> > It's still worth reporting upstream to QT, considering the
> > mission-criticality of the value. If I understand, t
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #30 from Brandon Wright ---
(In reply to Blazer Silving from comment #29)
> It's still worth reporting upstream to QT, considering the
> mission-criticality of the value. If I understand, they only need to provide
> a separate public, dynami
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #29 from Blazer Silving ---
> If Qt adds a public API to access the timer then kwin could change the timer
> step before initiating a window switch effect.
> If Qt can't change, this would need a reversion of the use of QtQuick scenes
> i
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #28 from Zamundaaa ---
(In reply to Merkurio from comment #27)
> At 120Hz, I don't have major issues, but as soon as I switch to 240Hz, the
> whole system feels like it's running at 60Hz (I even confirmed this with
> Blur Busters).
That's de
https://bugs.kde.org/show_bug.cgi?id=485927
Merkurio changed:
What|Removed |Added
CC||merkurio...@hotmail.com
--- Comment #27 from Merkuri
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #26 from Brandon Wright ---
Unfortunately, I don't think this will be fixed. The problem started when kwin
switched over to a QtQuick scene for the window switching effects. QtQuick
scene animations have only ever operated at 60hz:
* Qt is
https://bugs.kde.org/show_bug.cgi?id=485927
David Edmundson changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk
--- Comment #24 fro
https://bugs.kde.org/show_bug.cgi?id=485927
John changed:
What|Removed |Added
CC||ilikef...@waterisgone.com
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=485927
Brandon Wright changed:
What|Removed |Added
CC||bear...@gmail.com
--- Comment #22 from Brandon
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #21 from Blazer Silving ---
Kindly, can we get acknowledgement from someone KDE-side here? A knowledgable
dev could know Kwin's role in this timing value, or insight on how this could
be handled upstream in QT
--
You are receiving this mai
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #20 from Orlando Rodriguez ---
(In reply to Blazer Silving from comment #19)
> The quickest way to test a one-line fix like this is to build a patched
> package for your distro, and install it over the system version.
> Most offer tools and
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #19 from Blazer Silving ---
(In reply to n.parkanyi from comment #17)
> (In reply to Blazer Silving from comment #16)
> > > It looks like these animations are all being driven by QUnifiedTimer
> >
> > I'm curious how you found this!
>
> T
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #18 from Orlando Rodriguez ---
It's great having a possible solution for this issue!!! Thanks!!!. Just a quick
question, is there any guide about how to patch qtbase and reinstall it, so I
can also test this? I have been googling a little bi
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #17 from n.parka...@gmail.com ---
(In reply to Blazer Silving from comment #16)
> > It looks like these animations are all being driven by QUnifiedTimer
>
> I'm curious how you found this!
This was bothering me, so I was grepping around in
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #16 from Blazer Silving ---
> I assume this is upstream with qt. Does anyone know who I have to contact in
> order to upstream this?
A case can be opened at https://bugreports.qt.io/projects/QTBUG/issues,
but..
This is still techn
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #15 from Paul ---
Tried the patch on my system, X11 and Wayland both butter smooth now. (I used 4
ms to have a high enough refresh rate for a 240 Hz monitor).
Arch Linux
KDE Plasma: 6.2.4
KDE Frameworks: 6.8.0
Qt: 6.8.1
Kernel: 6.12.1-arch1
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #14 from dominickator122...@gmail.com ---
WOW! This completely solves everything!!! I'm still kind of new to the whole
Linux bug submitting experience, and I assume this is upstream with qt. Does
anyone know who I have to contact in order to
https://bugs.kde.org/show_bug.cgi?id=485927
fililip changed:
What|Removed |Added
CC||t...@nitrosubs.live
--- Comment #13 from fililip ---
https://bugs.kde.org/show_bug.cgi?id=485927
Blazer Silving changed:
What|Removed |Added
CC||kdebugs@paul.network
--- Comment #12 from Blaz
https://bugs.kde.org/show_bug.cgi?id=485927
Blazer Silving changed:
What|Removed |Added
CC||breakingsp...@gmail.com
--- Comment #11 from B
https://bugs.kde.org/show_bug.cgi?id=485927
n.parka...@gmail.com changed:
What|Removed |Added
CC||n.parka...@gmail.com
--- Comment #9 from
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #10 from n.parka...@gmail.com ---
Created attachment 176255
--> https://bugs.kde.org/attachment.cgi?id=176255&action=edit
hack to increase qt6 animation tick
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #8 from copil...@gmail.com ---
(In reply to copilexp from comment #7)
> I get strange behavior on X11, It is "low refresh rate" when I log in, but
> it somehow fixes itself after like two minutes, and then it is silky smooth.
> However, the s
https://bugs.kde.org/show_bug.cgi?id=485927
copil...@gmail.com changed:
What|Removed |Added
CC||copil...@gmail.com
--- Comment #7 from copi
https://bugs.kde.org/show_bug.cgi?id=485927
Thomas Duckworth changed:
What|Removed |Added
CC||tduck973...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=485927
justas changed:
What|Removed |Added
CC||jjom...@gmail.com
--- Comment #6 from justas ---
Stil
https://bugs.kde.org/show_bug.cgi?id=485927
nethshanpe...@gmail.com changed:
What|Removed |Added
CC||nethshanpe...@gmail.com
--- Comment #5
https://bugs.kde.org/show_bug.cgi?id=485927
username changed:
What|Removed |Added
CC||linx.system@gmail.com
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=485927
Vlad Zahorodnii changed:
What|Removed |Added
Component|wayland-generic |performance
--
You are receiving this mail b
https://bugs.kde.org/show_bug.cgi?id=485927
--- Comment #4 from goingtosleep ---
I encountered the same issue on wayland, with 165hz monitor, AMD RX 6600 XT,
Plasma 6.1.5 on kernel 6.10.10.
On X11 the animation is smooth, but every startup, I have to unsnap and snap a
window to make it smooth, ot
https://bugs.kde.org/show_bug.cgi?id=485927
goingtosleep changed:
What|Removed |Added
CC||goingtosleep...@gmail.com
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=485927
reports_go_brrr changed:
What|Removed |Added
CC||gooda...@starmail.net
Ever confirmed|0
https://bugs.kde.org/show_bug.cgi?id=485927
Orlando Rodriguez changed:
What|Removed |Added
CC||sort...@gmail.com
--- Comment #3 from Orlan
https://bugs.kde.org/show_bug.cgi?id=485927
Nate Graham changed:
What|Removed |Added
Component|"Manage Desktop and Panels" |wayland-generic
|window
70 matches
Mail list logo
