| Summary: | [Presentation Time] Limited to 120 Hz syncing! | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | David G. <david> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | normal | CC: | david, nate, vlad.zahorodnii, xaver.hugl |
| Priority: | NOR | Keywords: | qt6 |
| Version First Reported In: | 6.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
David G.
2024-03-07 16:21:21 UTC
Important, the issue is non-reproducible if using a screen with a refresh rate under or equal to 120 Hz. Testing further (laptop with 120Hz screen): The amount and frequency of 'incorrect' p2p values (double the time it should take to present a frame on a display of a specified refresh rate) that weston-presentation-shm shows increases drastically when actively running Chromium displaying the https://vsynctester.com website. Sounds like KWin is dropping frames. What CPU and GPU is this on? It's a Ryzen 7 4800H laptop with integrated Radeon Graphics and dedicated Nvidia Graphics (1660Ti). Kwin is running on the integrated Radeon Graphics, of course It's definitely not an underpowered system, so I suggest attempting to reproduce this issue on your end as well I didn't mean to imply the problem was on your side, I only needed to know what kind of problem we're talking about. KWin dropping frames on older Intel iGPUs is one thing (and being worked on) but it dropping frames on a Ryzen is new. Of course, and the issue might still be on my side anyway, who knows :) I only have this laptop to test on. Hello, this still seems to be an issue as of kwin 6.0.2. Hello, is there any update on this issue? It is present in 6.0.3 also. Thank you Plasma 6.1 contains a bunch of performance and frame timing improvements, which might fix this. Please retest this once 6.1 is out . 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 bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! I will test this again once 6.1 is released on Arch. Currently that is not the case I can confirm this now works perfectly on kwin 6.1.0!! Both weston-presentation-shm and Chromium now correctly sync up to 240Hz (the highest I can test). Nope. Nevermind. It's not solved. But I've also figured out what this bug is actually related to. Here's what I found: seems like just *having the proprietary nvidia driver loaded* breaks Chromium vsync on 240Hz, despite Kwin running on my AMD GPU. The only reason I thought it was fixed was that I forgot that I was in the middle of switching to beta nvidia drivers, and I didn't finish it. So when I loaded up my system, it wasn't loaded, and I just so happened to have installed plasma 6.1 at the same time. I'll create a new bug report. |