https://bugs.kde.org/show_bug.cgi?id=452315
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #12 from abulhair.sapa...@gmail.com ---
I also just tried using the "Show FPS" desktop effect. I think the FPS is
capped at 100, but at least it can tell us if the frame rate is <100. The
results so far:
X11:
testufo Firefox: 144Hz
testufo
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #11 from abulhair.sapa...@gmail.com ---
I kept getting 144Hz on Firefox, but I wasn't sure how much to trust it, since
I tried to guess the refresh rate simply based on my mouse/window movements and
it felt choppier. But that may have just
https://bugs.kde.org/show_bug.cgi?id=452315
Nate Graham changed:
What|Removed |Added
Status|NEEDSINFO |REPORTED
Resolution|WAITINGFORINFO
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #9 from abulhair.sapa...@gmail.com ---
Ah I tested it in Chromium. Do you know of a better way I can test the refresh
rate?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #8 from Zamundaaa ---
> https://testufo.com/ showed I was running at 60fps.
In what browser? Chromium has some known issues with high refresh rate on
Wayland
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #7 from abulhair.sapa...@gmail.com ---
I was able to get my monitor to run at 144Hz in X using the automatic X
configuration (i.e. no xorg.conf file; so both the receiver and monitor are on
the same X screen, which is also the Wayland
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #6 from abulhair.sapa...@gmail.com ---
I don't mind!
I noticed that kwin_wayland is supposed to let each monitor run at its native
refresh rate (https://kde.org/announcements/plasma/5/5.21.0/), but
https://testufo.com/ showed I was running
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #5 from Nate Graham ---
> I can't get 144Hz unless I disable the A/V receiver in Display Configuration,
> but doing so will
> prevent any audio going to the receiver
Would you mind if we used the bug report to track this specific issue?
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #4 from abulhair.sapa...@gmail.com ---
I just tried running with Wayland. It seems the screen/device configuration is
not managed by Wayland, but by the compositor. And so it behaves identically to
X when both the A/V receiver and monitor
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #3 from Nate Graham ---
Yes please. :)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=452315
--- Comment #2 from abulhair.sapa...@gmail.com ---
(In reply to Nate Graham from comment #1)
> (In reply to abulhair.saparov from comment #0)
> > I think this may be related to my Xorg configuration, since I have a monitor
> > connected via displayport
https://bugs.kde.org/show_bug.cgi?id=452315
Nate Graham changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|---
13 matches
Mail list logo
