https://bugs.kde.org/show_bug.cgi?id=417055
Rinigus changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #13 from Bug Janitor Service ---
Dear Bug Submitter,
This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #12 from Arjen Hiemstra ---
The default for the render loop is primarily based on platform. It will check
to see if threaded OpenGL is available and if so, default to the threaded
render loop. See
https://code.qt.io/cgit/qt/qtdeclarative.git
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #11 from Rinigus ---
Thanks! I presume that variable is acquired from underlying video card. Do you
know how that's done?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #10 from Arjen Hiemstra ---
It's a Qt only variable, GL has little to do with the render loop. Since you
mention flatpak, most likely that overrides or ignores the value.
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #9 from Rinigus ---
QSG_RENDER_LOOP=basic has been tested and improved the performance. Sorry, that
we did a while ago while discussing at Plasma Mobile IRC. Question is where its
set in Qt or GL, so I could start digging into why its wrong.
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #8 from Arjen Hiemstra ---
Alternatively, launch with QSG_RENDER_LOOP=basic
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #7 from Arjen Hiemstra ---
As David mentioned:
(In reply to David Edmundson from comment #3)
> You can test if it's the known vsync issue by setting the render loop to
> basic in kcmshell5 qtquicksettings
--
You are receiving this mail be
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #6 from Rinigus ---
Its ARM device, no nvidia here. As its using libhybris (originally Android
phone), no surprise if something is off on GL level. So, vsync suspicion makes
sense. Any tips on how I can check whether vsync works properly?
-
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #5 from Arjen Hiemstra ---
Since this is a Sailfish OS (so presumably ARM) device, I doubt that is going
to provide anything but "file not found". :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #4 from David Edmundson ---
Also, as I'm curious if we can fix it, output of
sudo cat /sys/module/nvidia_drm/parameters/modeset
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=417055
David Edmundson changed:
What|Removed |Added
Resolution|--- |WAITINGFORINFO
CC|
https://bugs.kde.org/show_bug.cgi?id=417055
--- Comment #2 from Arjen Hiemstra ---
The most likely cause of this is a lack of vsync in whatever driver your system
uses. There are a few related bugreports, but for example
https://bugreports.qt.io/browse/QTBUG-59300 mentions how animations will run
https://bugs.kde.org/show_bug.cgi?id=417055
Nate Graham changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=417055
Rinigus changed:
What|Removed |Added
CC||rinigus@gmail.com
--
You are receiving this mail
15 matches
Mail list logo
