Found the temporary fix to the bug on another thread. Go to System Preferences > Display > disable Auto adjust brightness.

Do you have a window in the room where you use your devices the most? If not, consider using them in places where there are windows during the daytime.

I like the first link, this is great. I'd like to make a suggestion (or for it to be more specific in the following

" For large screens this setting is probably not strong enough to remove all alerting light."

How about For large screens this setting is not strong enough to remove all alerting light. Just to really make it clear.

ah cool thank you

Wow, I didn't even know that was a thing now, ha. Whew.

Can we have a beta to try, PLEASE? 😇

Please refer to: https://justgetflux.com/forum/topic/213/fullscreen-youtube-colour-artefacting

@herf Thanks!!! I totally understand, but meanwhile could the a workaround. :)

@diogenes I don't understand... if you want to have the dark menu all time, just disable the flux one and that's it...

Yes this is in all versions. Check for the Disable menu (which is "for an hour" but you can of course toggle it back earlier).

On Windows you can use alt-end too.

Sorry there have been several requests to use a REALLY low orange in the daytime--but your post isn't this.

If you want a bit of orange glow maybe just slide the daytime slider around the 4700K mark. That may be near what you are looking for.

I meant to run at 6500K (or I actually recommend 5800K as that is direct sunlight on a white object at noon) in the daytime.

@seekingbuddha It is a one man operation--and it's also a one wonan operation! It's an awesome husband and wife team, and they are really cool people!

I fixed it.

You can do this at Terminal and relaunch after:

defaults delete org.herf.Flux SULastCheckTime

We have a button in the next version. :)

We kinda designed this for Photoshop users, who don't want a 30 second delay when they activate.

Probably we should do automatic movie triggers where more gradual changes are what you want anyway!

Found the issue - AWS is not serving files that can be installed on 10.11.1 basically. Fixing now. You should have the update soon.