Nope. I need to sleep the same way and the only thing you can do is adjust f.lux manually.

What I do is, I keep the Registry subkey deleted named "f.lux" from here: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

Each update to f.lux puts this subkey back. By deleting it, f.lux doesn't start with Windows.

You see, I keep f.lux set to "Classic f.lux" so that I only have a Day and Night color temperature and I keep both set to 800K. This way, when I'm ready for 800K, I just launch f.lux.

The next time I wake up, I turn my computer on and f.lux doesn't launch. It's nice.

OK, I spoke too soon. It stopped working again tonight. Not sure why. The only relevant piece of information is that I restarted my computer earlier, but why would that make f.lux not work? The settings say it's working, but the color hasn't actually changed on my screen.

I quit the app and restarted, and no difference.

Anyway, here's the driver info:

Intel Corporation 27.20.100.8935: Intel(R) UHD Graphics (20201028)
NVIDIA 27.21.14.6280: NVIDIA GeForce GTX 1650 Ti (20210609)
Fresco Logic 2.1.34054.0: Fresco Logic IDDCX Adapter (20171113)

AOC 2343, 509 x 286mm, built 2012
Chromaticities:
R=0.648438 0.338867
G=0.282227 0.602539
B=0.142578 0.070313
W=0.313477 0.329102
sRGB gamut: 92%, AdobeRGB gamut: 64%

Generic PnP Monitor, 344 x 194mm, built 2018
Chromaticities:
R=0.648438 0.344727
G=0.333984 0.616211
B=0.150391 0.057617
W=0.312500 0.328125
sRGB gamut: 83%, AdobeRGB gamut: 58%

Unlimited gamma ramp=1, Internal ramp=0
Monitor 1 on Fresco Logic IDDCX Adapter
Has VCGT profile=0, Gamma Ramp works=1

Windows Build: 19042.1237

@amerykanin Emailed you again

also one additional piece of info - it could be amd specific compatibility.

i asked someone on the internet and they're using windows 10, nvidia's 1060 and 3080 and apparently those doesn't have the same lag issue as mine.

Thanks, enabling "Always use Windows internal color table" fixed the problem. I have not otherwise noticed a difference. Are there disadvantages to enabling that setting? Also, do you know if Microsoft is aware of the problem?

Hi - we have only noticed the issue on window create. That is, they should only steal focus one time.

There are a few reasons we draw our own right now:

We support Windows 7 (though this is less an issue over time) We draw animated results in the notifiers (for instance, while dimming) The interaction with native code and windows "modern" notifiers was a bit difficult when we wrote this (they live in two separate universes, or did at the time). For instance, at one point we were registered as a new "app" on every launch, and we filled up the SQL database Windows uses for managing notifiers with thousands of entries, all named "f.lux" - that was pretty upsetting for our beta testers.

#3 was the immediate reason we took this out but it is probably easier to make it work right now.

Thank you. I will have to try the driver updates by submitting a service ticket. I can't even end those processes without administrative access.

Can you try changing your wake time to an earlier one?

We assume if you wake up early that you still want to "rest" even if you're not asleep.

Usually this is due to a USB-connected monitor that doesn't support color transforms, so f.lux is emulating them using the GPU. If you would like to post f.lux options > driver info, we may be able to help.

If they are all DisplayLink adapters, this article should help: https://support.displaylink.com/knowledgebase/articles/1886413-how-to-enable-night-light-or-f-lux-on-displaylink

Thanks - we will fix. This was only supposed to update when you pull down the menu (otherwise it can cache because it's not changing).