https://bugs.kde.org/show_bug.cgi?id=466454
David Edmundson changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #28 from Mark Richardson ---
What's the blocker to getting this fixed? Plasma 6 is going wayland by default,
and with qt6's native fractional scaling support being advertised, I see a lot
of angry and confused users unable to play any games
https://bugs.kde.org/show_bug.cgi?id=466454
Zamundaaa changed:
What|Removed |Added
CC||jacobstephens...@gmail.com
--- Comment #27 from
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #26 from David Edmundson ---
X developers were super fast.
https://gitlab.freedesktop.org/xorg/xserver/-/issues/1540
This fixes the issues with "thedarkmod" for me. If you can confirm that, it
would be great.
--
You are receiving this
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #25 from David Edmundson ---
filed at: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1540
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #24 from David Edmundson ---
The darkmod case seems to be different.
With the fractional scaling xserver ends up being told a logical size like
2133. X will then use that as a screen size, but set a mode size of 2128
(rounded down to the
https://bugs.kde.org/show_bug.cgi?id=466454
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #23 from Bug
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #22 from Mark Richardson ---
(In reply to Zamundaaa from comment #21)
> > However on native wayland, the max extant is always 16k. not what I would
> > call optimal usage
> I thought this was obvious but maybe I didn't describe it well:
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #21 from Zamundaaa ---
> However on native wayland, the max extant is always 16k. not what I would
> call optimal usage
I thought this was obvious but maybe I didn't describe it well: When picking a
swapchain size, Vulkan requires you to
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #20 from Mark Richardson ---
Created attachment 158165
--> https://bugs.kde.org/attachment.cgi?id=158165=edit
xwayland_swapchain_kwin_150scale
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #19 from Mark Richardson ---
(In reply to David Edmundson from comment #18)
> > I don't see a cross platform way to set the swapchain size, unless kwin
> > gives a surface of either 1px-16384px like it does on wayland, or exactly
> >
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #18 from David Edmundson ---
> I don't see a cross platform way to set the swapchain size, unless kwin gives
> a surface of either 1px-16384px like it does on wayland, or exactly matching
> the window size like on xwayland with no scaling
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #17 from Mark Richardson ---
(In reply to Zamundaaa from comment #15)
>
> What specific game and Proton version did you use? This is not happening for
> me and afaict from the dxvk code, it's handling the min/max surface extends
>
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #16 from Mark Richardson ---
(In reply to Zamundaaa from comment #15)
> (In reply to Mark Richardson from comment #13)
> > What can/should an app do about being lied to about the window size?
> You need to query the surface capabilities
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #15 from Zamundaaa ---
(In reply to Mark Richardson from comment #13)
> What can/should an app do about being lied to about the window size?
You need to query the surface capabilities with
vkGetPhysicalDeviceSurfaceCapabilitiesKHR, and
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #14 from David Edmundson ---
I don't think the app is being lied to.
It's being resized.
The vulkan code above is reading the current size the window is.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #13 from Mark Richardson ---
(In reply to David Edmundson from comment #11)
> I strongly suspect our window is configured to the 1280x721size; at which
> point it's partly client side problems for not handling that correctly.
> Turning a
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #12 from Mark Richardson ---
(In reply to David Edmundson from comment #10)
> Can you confirm that "X applications scale themselves" setting is currently
> checked, and that unchecking it avoids the problem?
makes no difference
--
You
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #11 from David Edmundson ---
Relevant mesa code:
wsi_common_x11.c: 659
```
x11_surface_get_capabilities(VkIcdSurfaceBase *icd_surface,
struct wsi_device *wsi_device,
https://bugs.kde.org/show_bug.cgi?id=466454
David Edmundson changed:
What|Removed |Added
Priority|NOR |HI
--- Comment #10 from David Edmundson ---
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #9 from Mark Richardson ---
testing with the latest tumbleweed under virtualbox shows the same problem with
both llvmpipe and SVGA3D GL drivers.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #8 from Mark Richardson ---
Just tested ubuntu 23.04 beta, absolutely no problems with any scaling factors
on gnome/whatever they are using. This is solely a Kwin problem.
--
You are receiving this mail because:
You are watching all bug
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #7 from Mark Richardson ---
Still happens on Plasma 5.27.4, is anyone looking into this? I would like to
continue using Linux and KDE, and am more than willing to help test images and
builds as long as this bug isn't going to rot or be
https://bugs.kde.org/show_bug.cgi?id=466454
Fushan Wen changed:
What|Removed |Added
CC||qydwhotm...@gmail.com
--- Comment #6 from Fushan
https://bugs.kde.org/show_bug.cgi?id=466454
Juan changed:
What|Removed |Added
CC||mauxili...@gmail.com
--- Comment #5 from Juan ---
Hi,
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #4 from Mark Richardson ---
(In reply to Mark Richardson from comment #3)
> None of this happens on the lavapipe vulkan driver, min/max extant always
> matches the window size exactly on Xorg and XWayland, and always returns min
> of (1,1)
https://bugs.kde.org/show_bug.cgi?id=466454
--- Comment #3 from Mark Richardson ---
After even more testing this appears to only happen with XWayland windows and a
scale set to 150%, or 250%, no other fractional scale factors trigger the
disconnect between the window size, and the vulkan surface
https://bugs.kde.org/show_bug.cgi?id=466454
Oleg changed:
What|Removed |Added
CC||o...@np880.ru
--- Comment #2 from Oleg ---
Can confirm
https://bugs.kde.org/show_bug.cgi?id=466454
Zamundaaa changed:
What|Removed |Added
CC||xaver.h...@gmail.com
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=466454
Nate Graham changed:
What|Removed |Added
CC||k...@davidedmundson.co.uk,
|
30 matches
Mail list logo
