Gamescope Session Plus with WSI increases powerdraw and requires so much cpu time it lags out games that otherwise run fine

[waffshappen]

Describe the bug

When playing Forza Horizon 4 the deck (steamos / bazzite on gamescope legacy) idles on ~2-3W (low preset) when sitting still, and generally manages 60FPS with slight dips.

However, when using the current bazzite defaults (ENABLE_GAMESCOPE_WSI + return (default) 1 from /usr/libexec/gamescope-sdl-workaround) it jumps at 8-10W sitting idle, while the framegraph is all over the place. This increased powerdraw is bad enough that FH4 goes from "mostly 60 with short dips for loading" to "40 average" in most places while moving.

If i override ENABLE_GAMESCOPE_WSI in /usr/share/gamescope-session-plus/gamescope-session-plus to 0 i drop down to 5W idle, if i also force /usr/libexec/gamescope-sdl-workaround to return 0 (and thus force gamescope legacy) i am back to the original powerdraw (at the cost of properly working tonemapping).

This is reducing the time i can play on battery by almost half, significantly increases heat and the uneven frametimes are so beyond terrible in races i almost get motion sick.

What did you expect to happen?

Gamescope Session Plus with WSI should take equal resources to the legacy gamescope.

Output of rpm-ostree status

State: idle
Deployments:
● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:stable
                   Digest: sha256:bfd698a496a41a55255d03270e7c3cdbe996c62c62fb7dde81dde9ef4b214eb9
                  Version: 40.20240922.0 (2024-09-23T05:03:03Z)
          LayeredPackages: sunshine

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-deck-gnome:stable
                   Digest: sha256:de80c8782dab06226afd3c4f9b5a6911cfc6ecf0c3168e14f416914af93c42a4
                  Version: 40.20240921.1 (2024-09-22T12:36:37Z)
          LayeredPackages: sunshine

Hardware

Jupiter

Extra information or context

No response