@herf I think I already wrote a reply but it didnt get approved yet? mby you have a xmas break (or mby I misremember)

anyway, so my 4070ti has two screens, one is monitor end DVI <----> GPU HDMI, this is the screen that doesnt get "respected" by flux, i.e. if I run a program in fullscreen on this screen, non of my 2 screens flux filter gets turned down,

my other monitor is monitor end displayport <----> GPU displayport, this monitor is the one that flux respects, if I run a program in fullscreen, the flux filter lifts from both screens.

Oof. I think you've identified it. The solution suggested on reddit seems to be a clean reinstall of NVIDIA's drivers... which... well... I'm going to go make peace with my bright red screen instead. :/

Thank you for digging into this. At least now I have something I can potentially try if I decide to fix things.

Have a good week ahead!

@herf It varies from a few times a day, and up to a few minutes apart.
I have been making changes to the network, but all on same net now with fixed ip.
Still quite often, so does not seem to be dhcp or routing related.
Turned off all automations in apps. Not using wall dimmers etc.
I did turn the lights down using the app about an hour ago, and have seen 3 notifications since, but none in the hours before using the app. - so probably like you say, its slowly undoing the change I made manually.

Changed to fast gaming transition now, and turned the lights all the way down in app. About 10% up again after 5 mins, but no notification yet.
Does seem a bit random when it displays :)

Actually, with the option checked to Back of flux when making app changes I expected flux to leave the lights alone for longer. Until the sun is up preferably ;)

@JoeNola Hi Joe - sorry for this, we have started to warn that Intel Xe adapters (11th and 12th gen) have this issue, it's an unfortunate bug that's somewhat out of our control. If Alt+End does not reset it, a reboot could be necessary to do so.

@p1r473 are you seeing this often?

It should be infrequent & only when someone is adjusting the lights external to f.lux....which I guess we expected would happen when you weren't using your PC, so this is kind of a debugging thing.

@cm223a We stopped doing this mainly due to Windows issues (but it also makes our privacy policy a little easier).

Our goal with the map is to show if you've chosen "Paris, Indiana" or "Paris, France" - I understand seeing more detail can help you be more sure that the location is correct, but the main goal is to be "close" but not exact with location. Since we do gradual fades, being within a minute for sunset/sunrise seems fine.

@Kuszkusz yes this is as expected - the changelog is for beta and Hue users who update. We try not to update everyone until things are stable.

@herf Just confirmed reference mode is not on and everything seems to be default in those settings

beta 4 fixes the issue 🎉

hearing that the latest Sonoma fixes this issue, so anyone affected please upgrade macOS.

@herf Sorry to open up this old topic again, but I am still having the same issue. Do you have an update on this?

@janat08 Alt+Shift+Page Up (and Alt+Shift+Page Down).

If this doesn't work, then you can enable this keyboard shortcut in the f.lux Options.

This keyboard shortcut will enable you to adjust the color temperature whenever you want.

@dreptio yes we have done a better job of this on Windows. We will add it to the list for macOS.

@sourdough05 yes it's important to calibrate displays. I can imagine doing some more of it in the future.

The "best" solution for this is to use a hardware calibrator like the i1display or the Spyder. These can account for not just the chromaticity of the whitepoint (like you describe) but the particular changes to render RGB properly also, and also they can make the "gamma curve" correct so that intermediate tones look right as well.

There are some apps that let you do this without the hardware, like QuickGamma: https://quickgamma.de/indexen.html and anything that adjusts ICC/ICM profiles like that tends to work with f.lux

@fluxr0x I would check first that "disable for app" is not turned on for VLC.

Otherwise it may be turning on a discrete GPU in your machine that resets the color settings, and the usual fix for that is to update all the video drivers. You can post f.lux options > driver info if you would like us to look.

@password you could try using our "LAN API" to post to a webserver that controls the keyboard. A simple python script could listen and f.lux would talk to it.

@armanatef which macbook is it?