A little known feature is that having "Custom Color" ON with "Color Temperature Control" OFF lets the GPU read data about the monitor's colour space over the HDMI/DP connection, and adjust the color output accordingly. This allows wide-gamut displays that don't have sRGB clamping to correctly display sRGB content without the need for ICC profiles (or in apps where they aren't supported, ie; most games). It's an awesome feature that saved me from having to return the Dell S2721DGF that suffered from incurable over-saturation without.
The problem is that after exiting any fullscreen game, the setting is reset to OFF. Sometimes the UI resets to OFF, and other times the UI still shows the ON setting, while the feature itself is clearly disabled. I've done some testing and have found that it doesn't matter if the game's profile uses Custom Color. When exiting the desktop, the global setting is always reset to OFF.
NOTE: This issue existed on previous versions as well.
what HW do you have?
latest Win10 version?
i use Win10 20H2; 20.12.1; R7 2700X + RX580 4G + X370 and dont have that problem ;)
Are you using it in the same manner as I am? Custom Color ON, but crucially Temperature Control which defaults to ON, is OFF?
3700X on X570
Monitors are connected via DisplayPort. No ICC profiles active.
I don't see why hardware should matter for this though.
yes i use custom color on and temp off
but i also have icc profiles loaded
btw - update your windows to 20H2 - as 20.12.1 works best with it ;)
if update is not resolving issue - clean old driver with DDU and install again
Did both, no dice. Really think it's something on the software end that I can't do anything about. In any case even if there was some specific step that fixes it, I'd say the fact that it doesn't work as is makes it a bug.
Since I can't edit the OP, I'll have to mention here that it takes a few seconds after exiting the game for the feature to reset. I've recorded a video of this in order to be of help to any AMD Staff: https://streamable.com/u5xuud
I also tested this on both my monitors to rule out anything related to one specific display.