https://bugs.kde.org/show_bug.cgi?id=516957
Bug ID: 516957
Summary: Direct Scanout Broken
Classification: Plasma
Product: kwin
Version First 6.6.1
Reported In:
Platform: CachyOS
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: compositing
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
SUMMARY
Direct Scanout was working before moving kde 6.6.1, not sure if it was working
on 6.6.0.
Compositing debug message doesn't go away when the app is move to fullscreen.
STEPS TO REPRODUCE
1. Open debug console `qdbus6 org.kde.KWin /KWin showDebugConsole`
2. Go to effect tab, and load showcompositing
3. Run vkcube, and fullscreen it using window rule, or browser fullscreen or
any game.
4. Compositing is still shown, you can enable show paint aswell and you can you
see direct scanout not working as it suppose to do.
OBSERVED RESULT
Compositing is still shown, you can enable show paint aswell and you can you
see direct scanout not working as it suppose to do.
Tried both gpu, Integrated IGPU (AMD) and also dedicated DGPU (Nvidia) didn't
work on both.
EXPECTED RESULT
Compositing shouldn't show.
SOFTWARE/OS VERSIONS
Operating System: CachyOS Linux
KDE Plasma Version: 6.6.1
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.5-3-cachyos (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 6600H with Radeon Graphics
Memory: 64 GiB of RAM (62.0 GiB usable)
Graphics Processor 1: AMD Radeon 660M
Graphics Processor 2: NVIDIA GeForce RTX 3050 Laptop GPU
ADDITIONAL INFORMATION
Am curious if direct scanout make a huge difference in game performance, as in
like fps, frametimes and latency wise. If it does how much of a difference it
makes. Or we shouldn't care about if direct compositing working or no, cause
compositor is already optimized?
--
You are receiving this mail because:
You are watching all bug changes.
