HDR colors incorrect in gamescope session, but perfect in desktop mode
Hi all, hopefully someone can help me out. My biggest issue right now in Bazzite, (Fresh install yesterday), is that my colors are extremely vibrant, like someone turned the vivid slider up to 1000 in the standard gaming mode. Games and videos are overwhelminly vibrant, red especially is extremely intense. This is HDR, with my specs below.
Switching to Desktop though, everything is perfect! Games and movies both look perfect. I've tried setting gamescope variables, but honestly I can't tell if they're actually doing anything. (If my environment variable is even set, afaik I just modified a config file, I can't tell if it's actually used anywhere).
Kernel: 6.10.3-202.fsync.fc40.x86_64 GPU: AMD Radeon 7900XTX Display: 4K HDR (LG TV, through a receiver)
Kernel: 6.10.3-202.fsync.fc40.x86_64 GPU: AMD Radeon 7900XTX Display: 4K HDR (LG TV, through a receiver)
14 Replies
New updates, I've manually added Gamescope and the parameters online (--enable-hdr, --force-composition) to Steam in desktop mode, launched the apps and games, and can now reproduce the same thing in desktop mode. So it appears to be a gamescope specific issue, but I'm not sure what I'm looking for still
I've confirmed the same behavior in ChimeraOS too, so this appears to be something Gamescope specific, not Bazzite specific. Continuing to dig
After testing multiple games, i found that this only happens on games that dont support HDR. Tested on gaming mode with an rx 6800.
Unfortunately that's the problem, it's hdr games with hdr fully enabled. But, since it's in chimera, and when launched with game scope, I think this is officially a game scope issue
So, I've run into a similar issue, using "--enable-hdr" without "--force-composition" won't cause the issue in desktop mode. Is "--force-composition" required for the game mode session?
Additionally, are we able to edit the gamescope session's parameters? I'd like to test things out, but I'm not sure where to start with this.
I did some testing modifying the gamescope session in the bazzite-deck image. Using the same arguments in the standalone session in gamemode gives the super saturated, broken HDR vs. the embedded session in plasma where the HDR works fine.
I don't know enough to know whether or not the different environment variables that gamemode configures, or if the stuff it does with xdg, etc, would affect this. This is all I have.
More testing, setup a standalone gamescope session without using gamescope-session, the same HDR issue appeared. This is definitely an issue with running gamescope as a standalone session.
Easiest way to test if colors are wrong is to open a browser and watch DBZ, Goku's gi will look blood red instead of orange, and you will also not be able to see the stars on the dragon balls, or just open a game like Warframe that gives you access to a ton of paint customization.
In this instance, the colors are very clearly wrong. Yellows are red, greens are blinding. It is immediately clear when HDR is enabled that the colors are incorrect. It’s also not just a monitor issue, since streaming HDR over Moonlight presents the same problem on my LG OLED, my iPhone, etc…
Seconded here, what is your info? First off I notice I am also on an LG OLED, and a 7900XTX. I am also using a receiver in between the GPU and TV, but if you don't have one then I'll assume that's not the issue. I'm thinking I may have to open an issue for Gamescope itself
I don’t have a receiver. Using both a cable, and streaming HDR to Moonlight from Sunshine all result in the same thing.
For good measure, I’ve also tested a number of HDR-enabled EDIDs (enabled as virtual monitors through kernel args) and streaming Sunshine headless, nothing changes.
I’m running my gamescope session from a VM with a passed-through 6900XT.
Okay that aligns with what I've been finding too. One thing though, whenever I enable gamescope, from the session or just with steam args, the issue crops up. You mentioned that without --force-composition when launching a game it does look fine?
So, realistically, there shouldn’t be any funky hardware quirks. Everything is virtualized other than the GPU
It looked fine in the nested session running over Plasma. It didn’t look fine in the standalone session (gamemode). I wondered if it was enabled in default by gamescope-session and found that wasn’t the case.
To get it to look fine when running from Plasma, this is the command I used.
There’s nothing really special about it, but this is all I needed to get HDR working well on Plasma.
Interesting, nothing stands out to me there that looks crazy except not having force composition
I couldn’t find a combination of commands that would get HDR working well in the gamescope standalone session, though.
It looks like someone beat us to the punch starting a bug over on gamescope, I'm filling out some info tonight and I'll probably fill it out more tomorrow:
https://github.com/ValveSoftware/gamescope/issues/1497
GitHub
Broken colors with steam and --hdr-enabled · Issue #1497 · ValveSof...
OS: Gentoo GPU: [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) Monitor: Odyssey G70NC Linux: 6.10.7 gamescope: 3.15.3 mesa: Mesa 24.3.0-devel (git-94e470a32d) vulkan-headers...
I rebased to desktop image and followed arch linux HDR guide, and i dont have broken colors so something in gamemode is fucked i guess