https://bugs.kde.org/show_bug.cgi?id=493745
Zamundaaa <xaver.h...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WAITINGFORINFO
CC| |xaver.h...@gmail.com
Status|REPORTED |NEEDSINFO
--- Comment #1 from Zamundaaa <xaver.h...@gmail.com> ---
Gaming on external GPUs is indeed very challenging. By default, what happens is
that
1. the app renders on the external GPU. Because of limited bandwidth of the USB
C connection and https://gitlab.freedesktop.org/mesa/mesa/-/issues/7340,
performance is worse compared to having it in a 16x PCIe slot
2. the driver copies the rendered results to a buffer in system memory
3. KWin gets that buffer in system memory, composites a results with the
integrated GPU
4. KWin either presents the composited result directly, or copies the
composited result back to the eGPU and presents it on a display connected to
that
There are efforts to fix that
(https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/268),
but none of this has changed in any way in the last few years.
> While trying to run a game fullscreen the eGPU gets used as expected (at
> least according to radeontop), but I don't see a picture, just a black screen
That sounds like a problem we can investigate though. If you put
KWIN_DRM_NO_DIRECT_SCANOUT=1 into /etc/environment and reboot, does anything
change in regard to that?
--
You are receiving this mail because:
You are watching all bug changes.
