Discussion:
[kwin] [Bug 401797] New: KWin/Wayland capping framerate to 60 fps in XWayland in borderless fullscreen (Wine)
Add Reply
Shmerl
2018-12-05 20:09:35 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

Bug ID: 401797
Summary: KWin/Wayland capping framerate to 60 fps in XWayland
in borderless fullscreen (Wine)
Product: kwin
Version: 5.14.3
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-***@kde.org
Reporter: ***@gmail.com
Target Milestone: ---

When using KWin/Xorg, I get unlimited framerate in Wine, even though my monitor
has 60 Hz refresh rate.

However KWin/Wayland is capping framerate to 60 fps in XWayland (Wine relies on
X still). I noticed it with games run in fullscreen borderless mode (not true
fulscreen).

According to this XWayland bug report:
https://bugs.freedesktop.org/show_bug.cgi?id=103282
only true fullscreen would work with XWayland without capping by default, and
in other cases compositors need to support it.

Is there some way to make KWin/Wayland run Wine in XWayland with unlimited
framerate when using borderless fullscreen? Vsync (in game settings) was
disabled in my tests.

Configuration:

* OS: Debian testing with kernel 4.19.5
* XWayland: 1.20.3
* Plasma / KWin: 5.14.3
* GPU: Sapphire Pulse Radeon Vega 56
* Graphics: OpenGL/Vulkan: Mesa master (for Wine and games), Mesa 18.3.0-rc5
(for the desktop).
--
You are receiving this mail because:
You are watching all bug changes.
David Edmundson
2018-12-05 20:30:18 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

David Edmundson <***@davidedmundson.co.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |***@davidedmundson.co.uk

--- Comment #1 from David Edmundson <***@davidedmundson.co.uk> ---
What's the purpose of having a refresh rate higher than your monitor?
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-05 20:32:02 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #2 from Shmerl <***@gmail.com> ---
(In reply to David Edmundson from comment #1)
Post by David Edmundson
What's the purpose of having a refresh rate higher than your monitor?
Testing performance of graphics drivers for instance.
--
You are receiving this mail because:
You are watching all bug changes.
Martin Flöser
2018-12-06 05:21:20 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

Martin Flöser <***@kde.org> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |NOT A BUG
Status|REPORTED |RESOLVED

--- Comment #3 from Martin Flöser <***@kde.org> ---
KWin is synced to the frame rate of the screen. On the other hand KWin does not
limit the frame rate of windows. They can render as many frames as they want.
Just KWin won't render them.
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-06 05:24:52 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #4 from Shmerl <***@gmail.com> ---
(In reply to Martin Flöser from comment #3)
Post by Martin Flöser
KWin is synced to the frame rate of the screen. On the other hand KWin does
not limit the frame rate of windows. They can render as many frames as they
want. Just KWin won't render them.
So if it doesn't limit it, why is framerate reported as unlimited in KWin/X
(i.e. it can fluctuate and go above 60 fps), and capped at 60 fps in
KWin/XWayland? I used dxvk internal HUD to display it and it shows the
difference.
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-06 05:30:49 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #5 from Shmerl <***@gmail.com> ---
May be then calculation of the (potential) framerate should be done differently
somehow? I.e. physical framerate is always capped by the monitor refrerh rate
either way. When various HUDs report framerate in X it's the potential one. But
somehow this calculation produces different results now in X and XWayland with
KWin.
--
You are receiving this mail because:
You are watching all bug changes.
Martin Flöser
2018-12-06 15:34:34 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #6 from Martin Flöser <***@kde.org> ---
You have to ask the XWayland developrs why they cap the frame rate. As I wrote
KWin does not limit applications, they can render at whatever frame rate they
want. We honestly don't care at all.
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-06 15:49:21 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #7 from Shmerl <***@gmail.com> ---
OK, I'll follow up with XWayland developers.
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-06 22:17:03 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #8 from Shmerl <***@gmail.com> ---
Opened new XWayland bug:
https://gitlab.freedesktop.org/wayland/wayland/issues/67
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-06 22:28:09 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797
Basically, the compositor must not reparent a "borderless fullscreen" X11 window to a larger X11 window (e.g. for drop shadows).
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-07 01:41:09 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #10 from Shmerl <***@gmail.com> ---
Sorry for confusion, I opened it for the wrong project (Wayland). It should
have been for Xorg, so here is the correct one:

https://gitlab.freedesktop.org/xorg/xserver/issues/20
--
You are receiving this mail because:
You are watching all bug changes.
Martin Flöser
2018-12-07 05:57:35 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #11 from Martin Flöser <***@kde.org> ---
We reparent all x windows and we won't change that.
--
You are receiving this mail because:
You are watching all bug changes.
Shmerl
2018-12-09 06:01:49 UTC
Reply
Permalink
https://bugs.kde.org/show_bug.cgi?id=401797

--- Comment #12 from Shmerl <***@gmail.com> ---
To give an update. This actually looks specific to Wine+dxvk (Vulkan) case and
it doens't happen in Wine+wined3d (OpenGL).
--
You are receiving this mail because:
You are watching all bug changes.
Loading...