[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-15 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=409763

--- Comment #8 from Martin Flöser  ---
(In reply to aska990 from comment #7)
> Fair enough.
> 
> Then I have 2 more questions, if you don't mind :
> 
> - Is there a reliable way to measure the actual refresh rate used by KWin ?
No. And it doesn't make any sense to try to measure. KWin renders only if
something changes, so in practice it's around 0 Hz on idle.
> - What should it be in theory in a mixed setup (say, 60Hz + 144Hz) ?

X11 only supports rendering to both screens at the same time. It doesn't make
sense to render with 144 Hz on a 60 Hz Screen, but a 144 Hz screen handles 60
Hz just fine.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-15 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409763

--- Comment #7 from aska...@hotmail.fr ---
Fair enough.

Then I have 2 more questions, if you don't mind :

- Is there a reliable way to measure the actual refresh rate used by KWin ?
- What should it be in theory in a mixed setup (say, 60Hz + 144Hz) ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-14 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=409763

Martin Flöser  changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |NOT A BUG

--- Comment #6 from Martin Flöser  ---
As you are quite aware of: fps effect is not a way to detect the actual used
refresh rate, especially not if refresh rate of screens is > 100 Hz.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409763

--- Comment #5 from aska...@hotmail.fr ---
I forgot to mention : setting "MaxFPS=144" makes the FPS indicator show "100"
in all 3 cases.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409763

aska...@hotmail.fr changed:

   What|Removed |Added

 Ever confirmed|0   |1
 Status|RESOLVED|REOPENED
 Resolution|NOT A BUG   |---

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-14 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409763

--- Comment #4 from aska...@hotmail.fr ---
Sorry to reopen, but it seems like there is still an issue with refresh rates.

So you were right, the screen was indeed running at 60Hz. I fixed that by
switching the refresh rate from "Auto" to "120Hz" in the Displays settings of
KDE.
(But then I switched it back to "Auto" and it kept the correct refresh rate,
even after a reboot...so I have no idea how the 60Hz happened in the first
place. I'm just going to assume some Xorg weirdness and move on).

Now xrandr reports the correct refresh rate :

eDP-1-1 connected 1920x1080+1919+0 (normal left inverted right x axis y axis)
344mm x 193mm
   1920x1080120.00*+  60.0159.9759.9659.93

And KWin as well :

Screen 1:
-
Name: eDP-1-1
Geometry: 1919,0,1920x1080
Scale: 1
Refresh Rate: 120.003

However the FPS counter still shows the wrong value when both monitors are
active. In summary, that's the current situation :

When both monitors are active : FPS shows "72"
When only the PRIME monitor is active : FPS shows "100"
When only the external monitor is active : FPS shows "100"

So, does that mean KWin is still running at the incorrect refresh rate when
both monitors are active ?

Also, even if one monitor was running at 60Hz and the other at 144Hz, shouldn't
KWin run at the highest value instead of some weird compromise like 72Hz ? Or
is that some kind of explicit hack to avoid tearing issues ?

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-13 Thread Martin Flöser
https://bugs.kde.org/show_bug.cgi?id=409763

Martin Flöser  changed:

   What|Removed |Added

 Resolution|--- |NOT A BUG
 Status|REPORTED|RESOLVED

--- Comment #3 from Martin Flöser  ---
According to the output of xrandr the screen is running at 60 Hz.

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409763

--- Comment #2 from aska...@hotmail.fr ---
Created attachment 121493
  --> https://bugs.kde.org/attachment.cgi?id=121493=edit
Current .kwinrc

-- 
You are receiving this mail because:
You are watching all bug changes.

[kwin] [Bug 409763] Kwin does not correctly detect refresh rate of PRIME monitor

2019-07-13 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=409763

--- Comment #1 from aska...@hotmail.fr ---
Created attachment 121492
  --> https://bugs.kde.org/attachment.cgi?id=121492=edit
Output of "xrandr -q"

-- 
You are receiving this mail because:
You are watching all bug changes.