@keking you probably want to disable f.lux's daily switching (uncheck "effects > use dark mode at sunset") and enable the Windows dark mode instead. Check Windows > Settings > Color settings

@Jaycee12 can you remap using AutoHotkey or similar?

The issue with system-global hotkeys is that the conflicts are very tricky to manage - there are many, many hotkeys used by other programs, and it isn't clear if you've remapped something that will be needed in one program or another later. So we move
rather slowly here.

I think a standalone app may be able to give you a better UI for setting this up than we will - even though, I totally agree with you that being able to do this is important.

@rand29 thank you we have it on our list to work on winget support. Right now it is not really done!

@BLARRY For games, it's usually because the game uses DirectX 9. That's as much as I know.

@herf Thank you.

@eivindlia said in Tinted screen on screenshots or when screen sharing v2:

@eivindlia said in Tinted screen on screenshots or when screen sharing v2:

Problem appears when using a USB-C Display Link docking. I have tried to set the key HKEY_LOCAL_MACHINE\SOFTWARE\DisplayLink\Core\EnableGammaRamp = true, but that disables f.lux from working on the external monitoring completely.

Intel Corporation 30.0.100.9864: Intel(R) Iris(R) Xe Graphics (20210820)
DisplayLink 10.1.2875.0: DisplayLink USB Device (20210811)
DisplayLink 10.1.2875.0: DisplayLink USB Device (20210811)

Generisk PnP-skjerm, 797 x 334mm, built 2020
Chromaticities:
R=0.676758 0.315430
G=0.286133 0.636719
B=0.135742 0.077148
W=0.313477 0.329102
sRGB gamut: 100%, AdobeRGB gamut: 77%

Generisk PnP-skjerm, 309 x 174mm, built 2019
Chromaticities:
R=0.639648 0.329102
G=0.299805 0.599609
B=0.149414 0.059570
W=0.130859 0.328125
sRGB gamut: 99%, AdobeRGB gamut: 64%

Unlimited gamma ramp=1, Internal ramp=0
Monitor 1 on Intel(R) Iris(R) Xe Graphics
Has VCGT profile=0, Gamma Ramp works=1
Monitor 2 on DisplayLink USB Device
Has VCGT profile=0, Gamma Ramp works=0

Windows Build: 19042.1415

Please assist :)

Upgraded drivers, but same problem occurs:
Intel Corporation 30.0.101.1191: Intel(R) Iris(R) Xe Graphics (20211203)
DisplayLink 10.2.6709.0: DisplayLink USB Device (20220110)
DisplayLink 10.2.6709.0: DisplayLink USB Device (20220110)

Generic PnP Monitor, 797 x 334mm, built 2020
Chromaticities:
R=0.676758 0.315430
G=0.286133 0.636719
B=0.135742 0.077148
W=0.313477 0.329102
sRGB gamut: 100%, AdobeRGB gamut: 77%

Generic PnP Monitor, 309 x 174mm, built 2019
Chromaticities:
R=0.639648 0.329102
G=0.299805 0.599609
B=0.149414 0.059570
W=0.130859 0.328125
sRGB gamut: 99%, AdobeRGB gamut: 64%

Unlimited gamma ramp=1, Internal ramp=1
Monitor 1 on Intel(R) Iris(R) Xe Graphics
Has VCGT profile=0, Gamma Ramp works=1
Monitor 2 on DisplayLink USB Device
Has VCGT profile=0, Gamma Ramp works=0

Windows Build: 19043.1466

Upgraded drivers again, but still same problem:
Intel Corporation 31.0.101.3222: Intel(R) Iris(R) Xe Graphics (20220711)
DisplayLink 10.2.6709.0: DisplayLink USB Device (20220110)
DisplayLink 10.2.6709.0: DisplayLink USB Device (20220110)

Generic PnP Monitor, 797 x 334mm, built 2020
Chromaticities:
R=0.676758 0.315430
G=0.286133 0.636719
B=0.135742 0.077148
W=0.313477 0.329102
sRGB gamut: 100%, AdobeRGB gamut: 77%

Generic PnP Monitor, 309 x 174mm, built 2019
Chromaticities:
R=0.639648 0.329102
G=0.299805 0.599609
B=0.149414 0.059570
W=0.130859 0.328125
sRGB gamut: 99%, AdobeRGB gamut: 64%

Unlimited gamma ramp=1, Internal ramp=1
Monitor 1 on Intel(R) Iris(R) Xe Graphics
Has VCGT profile=0, Gamma Ramp works=1
Monitor 2 on DisplayLink USB Device
Has VCGT profile=0, Gamma Ramp works=0

Windows Build: 19044.1889

@saimon yes you should turn off the f.lux setting that switches and use your system preferences to do it instead. We are built on top of those settings.

I wish Sharex would work with f.lux on getting this resolved. :-l

https://forum.justgetflux.com/topic/4653/tinted-screenshots-or-fullscreen-apps-and-games-missing-f-lux/1?_=1655838569867

@herf So, the 'white nights' are upon us once again, and still no solution to this 1.png