@herf that didn't work. I don't use usb but thunderbolt.
However, an hour ago, I updated f.lux to version 4.131 (Jan 2024) and the issue is gone! I cross my fingers.

@RVogt222 if the location is right, you should check your timezone/system clock here:
https://justgetflux.com/timesync.html

Sometimes the timezone gets set to the wrong one, and so the displayed time "looks" right but it isn't really.

@Artsem-K

this can be done by setting the "late" slider all the way to the right, or by choosing the "classic f.lux" preset. only about 10-15% of Windows machines have a light sensor... if you mean to network the smartphone so it can be used as a "nearby" light sensor? then not really, it is too difficult to do things in the background on most of them

@xilef11 thanks for this, we found it could happen on certain kinds of HTTP/server errors. Instead f.lux will now poll 10 times over 10 seconds, and then stop. This will be in v4.131

@Girofox123 thank you - it looks like the Windows API (called "SHQueryUserNotificationState") which tells us if it is a good time to notify someone actually writes to the registry, so we have stopped doing it so much (v4.131 should have the fix). There may still be a way to trigger this in the future, but it will be rare.

@anon_a_mouse Are you running the installer each time? f.lux should not do this more than one time.

I just tested with different combinations. With only 3 monitors connected, I can't reproduce the artifacts at all.

@fckflux Lol, happened to see your reply a little late perhaps. I see your username and that's hilarious, why bother using f.lux anyways man you have a laptop with brightness hotkeys to change your brightness so no need! Also just use Windows night mode or use LightBulb instead for christ sike. Dude's probably still complaining about his washed out color's, sheeeeeeit if necessary reinstall darn Windows! Then simple don't ever reinstall f.lux on that laptop. Not hard.

I stand by F.lux and have been using it for years no problem with AMD & Nvidia GPU's, all kinds of different hardware. But hopefully by now you've already fixed your issue...

What really gets me is when you say "7 years later this issue still persists." I'm uncertain as to what to think about that. Do you mean you've been dealing with this same issue after installing F.lux from 7 years ago? If so dude, maybe you should get a new laptop. LMAO. But If I think what you really meant is that you've seen other threads from people 7 years ago with this same problem then that would obviously make more sense.

@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