https://bugs.kde.org/show_bug.cgi?id=395632
Sergey Kondakov <virtuous...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |virtuous...@gmail.com
--- Comment #60 from Sergey Kondakov <virtuous...@gmail.com> ---
(In reply to Kailash from comment #59)
> (In reply to Benjamin Xiao from comment #58)
> > Did the session start at 120fps and you turned it down to 100? That's one of
> > the bugs I am experiencing, where Chrome seems to use the refresh rate value
> > that was set at the beginning of the X session.
>
> The session started at 60 fps and stays at 60 even if I switch to 100, but
> chromium shows 120 fps with vsync. I have no idea why or how to debug this :(
How do you check "real fps" that it supposedly "stays at" ?
I've forced T11071 patches into my build of kwin-5.16.5 release and get:
maxFpsInterval: 16666666
refreshRate: 0
vBlankTime: 6000000
glStrictBinding: false
glStrictBindingFollowsDriver: true
glCoreProfile: true
glPreferBufferSwap: 99
glPlatformInterface: 2
windowsBlockCompositing: false
…
Screen 0:
---------
Name: DVI-D-0
Geometry: 0,0,1920x1080
Scale: 1
Refresh Rate: 72.9249
Screen 1:
---------
Name: HDMI-A-0
Geometry: 1920,0,1920x1080
Scale: 1
Refresh Rate: 71.8263
With my 2 OC'ed native 60fps displays. vsynctester.com in FF and all native
apps show exact frame-time of what ~73 fps would get, as does the monitor
itself. But kwin says "maxFpsInterval: 1(6), refreshRate: 0 and vBlankTime:
6*10^6" which is suspicious. All feels nice and snappy even though current
kernel amdgpu has a bug that prevents me from enabling PageFlip.
But how to be sure that kwin does not limit actual framerate between it and GPU
by increasing frame-time after getting frames from the apps or something like
that ?
I also use these envvars, "just to be sure":
KWIN_OPENGL_INTERFACE=egl
KWIN_TRIPLE_BUFFER=0
KWIN_USE_BUFFER_AGE=1
KWIN_USE_INTEL_SWAP_EVENT=1
KWIN_PERSISTENT_VBO=1
(In reply to Roman Gilg from comment #45)
> I'm currently working on the compositing. There have been already several
> patches landed as preparations: https://phabricator.kde.org/T11071
>
> What would help me is if you guys would be on KWin master branch (for
> example via KDE Neon dev unstable) to test upcoming patches.
>
> I have here an AMD RX470 and a 75Hz display but the monitor is probably not
> enough. I'm gonna look for some 144Hz display to buy. You are using AMD
> graphics cards right?
>
> > This issue isn't RX Vega 64 specific it seems. On my laptop with Intel
> > graphics, Painting blocks on vertical retrace is also returning No.
>
> Does this mean you noticed low refresh rates on a laptop with high refresh
> rate display and Intel graphics as well?
Please, don't allow your changes to bit-rot like what happened with fredrik's
'linux-dmabuf', 'vulkan' and 'swap-event-wip2' branches. kwin is pretty much #1
feature of all KDE, especially after deaths and stagnation of many core apps
such as kde-telepathy, gwenview, akregator, etc.
--
You are receiving this mail because:
You are watching all bug changes.
