| Summary: | GPU underutilization on Star Citizen (vulkan) | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Bernard <w.iron.zombie> |
| Component: | performance | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | REPORTED --- | ||
| Severity: | normal | CC: | gort818, nate |
| Priority: | NOR | ||
| Version First Reported In: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Star Citizen KWin Wayland vs X11 comparison | ||
|
Description
Bernard
2024-08-22 22:31:48 UTC
Created attachment 172863 [details]
Star Citizen KWin Wayland vs X11 comparison
I can also reproduce this on Arch. For now I am using gamescope as a workaround to bypass kwin, I now get over 95% GPU utilization and much high frame rates when using the wayland session. I tried star citizen's PTU build today and apparently pausing and unpausing the game now gets rid of the underutilization issue but it's still happening before then (In reply to Bernard from comment #3) > I tried star citizen's PTU build today and apparently pausing and unpausing > the game now gets rid of the underutilization issue but it's still happening > before then Oopsie, forgot to mention that I did this testing with the DirectX backend & not the Vulkan one So now in SC 3.24.2 it will affect both backends (haven't tried vulkan again as it is currently completely broken on that testing version but I'd assume it will still happen) |