https://bugs.kde.org/show_bug.cgi?id=450914
tomblackwh...@outlook.com changed:
What|Removed |Added
CC||tomblackwh...@outlook.com
--
You
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #37 from Samuel ---
Update: This issue will be fixed in the upcoming NVIDIA 545 Driver
(https://forums.developer.nvidia.com/t/nvidia-bug-kde-wayland-games-are-force-vsynced/237880/21).
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=450914
Nate Graham changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #35 from Samuel ---
Here is the NVIDIA Developer forum link for this bug :
https://forums.developer.nvidia.com/t/nvidia-bug-kde-wayland-games-are-force-vsynced/237880
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #34 from Samuel ---
Here is the latest news on this bug:-
"Hi, I’m currently working on a driver-side change that should resolve the
forced vsync issue, as well as enable direct scan-out for eligible Xwayland
applications.
Work on Gamma
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #33 from kodatar...@yahoo.com ---
Perhaps this should be reported to the nvidia forums and kept track on there,
maybe that would help out on a solution for this issue.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #32 from Samuel ---
(In reply to Erik Kurzinger from comment #25)
> It should be pretty easy to fix, but that will need to be in an
> upcoming driver release.
I updated to latest stable NVIDIA proprietary driver version - 525.60.11 and
the
https://bugs.kde.org/show_bug.cgi?id=450914
Fushan Wen changed:
What|Removed |Added
CC||qydwhotm...@gmail.com
--- Comment #31 from Fushan
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #30 from kodatar...@yahoo.com ---
Any ETA of when this might be resolved ? Note: The forced Vsync is not the
issue, real problem is when you have multiple monitors it cuts the game's
performance in 70% which is more than half and on
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #29 from kodatar...@yahoo.com ---
(In reply to Samuel from comment #28)
> (In reply to Erik Kurzinger from comment #25)
> > It should be pretty easy to fix, but that will need to be in an
> > upcoming driver release.
>
> Just to get it
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #28 from Samuel ---
(In reply to Erik Kurzinger from comment #25)
> It should be pretty easy to fix, but that will need to be in an
> upcoming driver release.
Just to get it clarified, direct scan-out will be fixed by next driver update
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #27 from Zamundaaa ---
> Firstly, I noticed that, unfortunately, direct scan-out for Xwayland
> applications doesn't work at all with our driver right now. This is an issue
> on our end, we're allocating compressed buffers which aren't
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #26 from Samuel ---
(In reply to Erik Kurzinger from comment #25)
> But is that really the solution users want? Sure, it would technically let
> the game run at an uncapped refresh rate, but as I understand it the main
> reason people want
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #25 from Erik Kurzinger ---
So I did look into this a bit further, and can provide some hopefully relevant
information...
Firstly, I noticed that, unfortunately, direct scan-out for Xwayland
applications doesn't work at all with our driver
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #24 from kodatar...@yahoo.com ---
(In reply to Samuel from comment #23)
> Is there anything that we can do to assist fixing this bug @Zamundaa and
> @Erik? This is a "Wayland Showstopper"-tier bug for gamers running
> FPS/Shooter/Battle
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #23 from Samuel ---
Is there anything that we can do to assist fixing this bug @Zamundaa and @Erik?
This is a "Wayland Showstopper"-tier bug for gamers running FPS/Shooter/Battle
Royale games.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #22 from kodatar...@yahoo.com ---
Any update on this? It's been a while and this hinders the performance a lot of
some of the more demanding titles
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450914
Raul José Chaves changed:
What|Removed |Added
CC||rjchave...@gmail.com
--- Comment #21 from
https://bugs.kde.org/show_bug.cgi?id=450914
mira...@mirandastreeter.com changed:
What|Removed |Added
CC||mira...@mirandastreeter.com
--
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #20 from kodatar...@yahoo.com ---
Update as of Plasma 5.25 Beta(5.24.90)
On multiple displays it properly detects the refresh rate and sets proper
V-Sync now, but limits the framerate to the monitor's refresh rate(165fps //
165hz), other
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #19 from Samuel ---
(Gameplay in Plasma Wayland was smooth because VSync was forced.)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #18 from Samuel ---
I experienced hitching and some stuttery gameplay in GNOME, Sway and Plasma
Wayland as soon as the FPS of game exceeds/deceases above/below Screen's
refresh rate.
--
You are receiving this mail because:
You are
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #17 from kodatar...@yahoo.com ---
(In reply to kodatarule from comment #16)
> Ok, with the new driver, most of the issues seem remedied, but I think once
> this issue is fixed freesync/gsync should also be looked at as it's working
> on
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #16 from kodatar...@yahoo.com ---
Ok, with the new driver, most of the issues seem remedied, but I think once
this issue is fixed freesync/gsync should also be looked at as it's working on
Sway.
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=450914
patrik...@protonmail.com changed:
What|Removed |Added
CC||patrik...@protonmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=450914
kodatar...@yahoo.com changed:
What|Removed |Added
CC||kodatar...@yahoo.com
--- Comment #15
https://bugs.kde.org/show_bug.cgi?id=450914
Zamundaaa changed:
What|Removed |Added
CC||nexustc...@gmail.com
--- Comment #14 from
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #13 from Alessandro Astone ---
(In reply to Alessandro Astone from comment #12)
> Zamundaaa this is the same bug we discussed here
> https://bugs.kde.org/show_bug.cgi?id=448918
>
> Not only is the application being "vsynced" (meaning the
https://bugs.kde.org/show_bug.cgi?id=450914
Alessandro Astone changed:
What|Removed |Added
CC||ales.ast...@gmail.com
--- Comment #12 from
https://bugs.kde.org/show_bug.cgi?id=450914
Samuel changed:
What|Removed |Added
Version|5.24.2 |5.24.3
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=450914
Nate Graham changed:
What|Removed |Added
Status|REOPENED|CONFIRMED
CC|
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #11 from Samuel ---
(In reply to Zamundaaa from comment #10)
> @Samuel you can quickly check if direct scanout makes a difference by putting
> KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment and rebooting
No. Checked using `env`
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #10 from Zamundaaa ---
There is some weird interaction of Xwayland with windowed contents that can
cause something similar:
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1309
The timer in Xwayland is about 58-59fps, not 60 though, so
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #9 from Samuel ---
(In reply to Erik Kurzinger from comment #8)
> Probably the important different there is that Xwayland will use the "copy"
> path in xwayland-present.c for windowed applications but will use the "flip"
> path for
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #8 from Erik Kurzinger ---
Tried this with a debug NVIDIA driver, and it looks like the application is
spending most of its time waiting for the PresentIdleNotify event from
Xwayland. If vsync is disabled this should get delivered pretty
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #7 from Samuel ---
I also noticed something interesting. In Fullscreen and Borderless modes, VSync
is being forced in Plasma while the Windowed mode doesnt have this problem.
Windowed mode has uncapped FPS similar to other compositors.
--
https://bugs.kde.org/show_bug.cgi?id=450914
Zamundaaa changed:
What|Removed |Added
CC||ekurzin...@nvidia.com
--- Comment #6 from
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #5 from Zamundaaa ---
*** Bug 451066 has been marked as a duplicate of this bug. ***
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #4 from Samuel ---
i can get unlocked fps in sway (wlroots) too in Apex Legends... Re-opening to
confirm if it really is an upstream bug.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450914
Samuel changed:
What|Removed |Added
Resolution|UPSTREAM|---
Status|RESOLVED
https://bugs.kde.org/show_bug.cgi?id=450914
Samuel changed:
What|Removed |Added
CC||samping...@gmail.com
--- Comment #3 from Samuel ---
https://bugs.kde.org/show_bug.cgi?id=450914
--- Comment #2 from Alexander Streng ---
Ah, I just thought that it might be a bug with kwin since I've heard that Gnome
doesn't have this issue in Wayland session 樂
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=450914
Zamundaaa changed:
What|Removed |Added
Resolution|--- |UPSTREAM
CC|
43 matches
Mail list logo
