Are you using tone mapping through the Steam UI (I think the Deck has its own controls for HDR inverse tone mapping) or through the command line options you can use for games? If you are using the UI, it might be worth using the command line toggles instead as maybe the UI is setting some wrong settings. If it helps, here is the set of command line options I use on my system (modify brightness, refresh rate, and resolution to fit your display) DXVK_HDR=1ENABLE_HDR_WSI=1gamescope-f-r165-W3440-H1440--adaptive-sync--hdr-enabled--hdr-itm-enable--hdr-itm-sdr-nits350--hdr-sdr-content-nits800--hdr-itm-target-nits1000 gamemoderun--%command%. In addition, it might be worth looking through the display settings to see if it’s in any sort of colour boosting HDR modes - my Alienware had to be set to “HDR Peak 1000” for colours to look as they should, as by default it messes around with things a bit. If you can as well, try some other devices that can output HDR (like a game console or Blu Ray player or something) to see if it’s making those outputs look a bit red too - if so, it’s to do with the display, and if not it’s a configuration issue.
I have not started using the launch flags yet, I’ll have to give those a try. Wonder if it’s possible to set those nits values globally per display in a config file somewhere?
As far as I know, no. I guess it’s not exactly a good idea globally, as some games sometimes need some changes. For example there’s one or two that don’t like ITM and will have display corruption (at least last time I tested, possibly fixed now), and I have to use some extra flags to get TF2’s mouse controls working in Gamescope.
Are you using tone mapping through the Steam UI (I think the Deck has its own controls for HDR inverse tone mapping) or through the command line options you can use for games? If you are using the UI, it might be worth using the command line toggles instead as maybe the UI is setting some wrong settings. If it helps, here is the set of command line options I use on my system (modify brightness, refresh rate, and resolution to fit your display)
DXVK_HDR=1 ENABLE_HDR_WSI=1 gamescope -f -r 165 -W 3440 -H 1440 --adaptive-sync --hdr-enabled --hdr-itm-enable --hdr-itm-sdr-nits 350 --hdr-sdr-content-nits 800 --hdr-itm-target-nits 1000 gamemoderun -- %command%. In addition, it might be worth looking through the display settings to see if it’s in any sort of colour boosting HDR modes - my Alienware had to be set to “HDR Peak 1000” for colours to look as they should, as by default it messes around with things a bit. If you can as well, try some other devices that can output HDR (like a game console or Blu Ray player or something) to see if it’s making those outputs look a bit red too - if so, it’s to do with the display, and if not it’s a configuration issue.I have not started using the launch flags yet, I’ll have to give those a try. Wonder if it’s possible to set those nits values globally per display in a config file somewhere?
As far as I know, no. I guess it’s not exactly a good idea globally, as some games sometimes need some changes. For example there’s one or two that don’t like ITM and will have display corruption (at least last time I tested, possibly fixed now), and I have to use some extra flags to get TF2’s mouse controls working in Gamescope.