Me too. I get it set up with the colors the way I want them. I close the app, the standard colors come back. I hover over a link on a webpage, the flux colors come back. I move the mouse away, the standard colors come back. I'm going to downgrade to v3 until this gets fixed.

Intel Corporation 21.20.16.4550: Intel(R) HD Graphics 520 (20161111)
DisplayLink 8.2.1952.0: DisplayLink USB Device (20170522)
DisplayLink 8.2.1952.0: DisplayLink USB Device (20170522)

2 monitors

Generic PnP Monitor
Dimensions: 607 x 345
Year: 2016
Chroma:
R=0.633789 0.340820
G=0.311523 0.635742
B=0.158203 0.061523
W=0.312500 0.329102
sRGB gamut: 91%, AdobeRGB gamut: 64%

Generic PnP Monitor
Dimensions: 308 x 173
Year: 2014
Chroma:
R=0.573242 0.334961
G=0.323242 0.579102
B=0.158203 0.142578
W=0.313477 0.329102
sRGB gamut: 78%, AdobeRGB gamut: 50%

hmm sometimes it can get lost when explorer.exe crashes, but it sounds unusual - let me know if this happens again?

Yeah, usually drivers.

f.lux removes blue light from your computer display at night. f.lux isn't intended to prevent or heal vision loss. It's a good thing to pay attention to though, an eye doctor could probably help you with some good suggestions.

@herf thank you for finding this. Much appreciated.

Hi,

because you are updating f.lux very often and the reg key is still not implemented, I made my own tool to customize the shortcuts.

If you are interested, you can find sources here http://dl.free.fr/oBZnx22Ln (c#) as well as binaries (needs dot net 4.5, could be downgraded if it is a problem).

I will update this tool for myself, but if another users wants changes, please just ask

Regards

Thanks this is super helpful - will update the FAQ.

oh, thank you!

Can you try the latest version on the website and see if it helps? There are some fixes there.

I think this is it: f.lux keeps the "hue" preference turned on even when pairing fails, and so each time you restart it like this, it will try to make an account. It will tell you in a notifier that it's doing that...but of course you might not jump right up and hit the hue button right then.

We probably should not do this on startup, and instead turn the feature off if it fails... this is broken in the code because we allow you to pair with multiple bridges, and so if you wanted f.lux to control one and not another one, it is hard to show that in the UI.

Then, I think Hue is persisting those attempts forever, even if the pairing is unsuccessful. (The "old" protocol did not do this, so I have an excuse....)

Will take another look at it.

The "classic f.lux" setting has doesn't seem to have the same gentle transition.
0_1515610664767_upload-e057e53b-cfec-4075-9672-64ca9f9ff323

We pushed a small update to the main page that may have helped too - it fixed one problem with fullscreen disable.

The new beta has crash dumps so you can send the information about why f.lux crashed to us. Please run this one:

https://justgetflux.com/flux-setup4.exe

@herf said in Suggestions: Hue optimisations:

Does it work if you restart f.lux instead of turning the feature off and on?

Yes, it works. If f.lux is just faster then the network, maybe there should be a delay you can set, and maybe a number of retries before it gives up.

@herf said in Suggestions: Hue optimisations:

but for me, it was way too much with overhead (ceiling) lights, so that's why it's doing that.

That's the problem, I think. Every user has a different setup, so more configurable options are needed to suit everyone.

Would it be possible to add a hue toggle in the notification area's menu? The way it is now, there are quite a few clicks to disable it temporarily. Sometimes, I just want other software to control my lights.