@Yemafu the big reason to like TUV certification is that it ensures a low-flicker display, which is really helpful.

For blue light, this standard is not very effective, as it's a super tiny change in blue light, usually below 10%. You'd be better off with something that dims to a comfortable level, or adjusting your desk and the glare around it.

@Holoubek You might want to set Backwards Alarm Clock a bit earlier. For example you want to stop working at 9pm, you should set the wake up time to 6am.
46a732ae-c090-47e8-9707-307e58c63b2b-image.png
It should notify you around that time.

@bitzie I would first expect the NVIDIA driver, since these drivers over the last few years have had modes that turn off color controls ("reference mode" and other things), though recently one of them was very hard to turn off once you turn it on.

I can only recommend looking some more into color settings in the NVIDIA control panel ("Current color accuracy mode" under "Adjust desktop color settings"?)

Hi everyone - yes it is still one click to turn it off. However, without it, people do not set their wake time, and so f.lux cannot customize lighting based on this information. These two features work together, and I hope it isn't too hard to turn off the notifications if they aren't helpful - but we will leave it on for this reason.

@karahbit yes we have been saying this since a few years before Iris existed, though it sounds like our marketing isn't as good!

With a majority of LED backlights today showing essentially no flicker when they dim (see https://www.notebookcheck.net/PWM-Ranking-Notebooks-Smartphones-and-Tablets-with-PWM.163979.0.html), we don't think this is for everyone, as it has an impact on contrast and power usage. But with a display with bad flicker, it's absolutely a good way to do it.

Now the version of flux-setup.exe that is linked to from the website has a Last-Modified header of "Wed, 21 Feb 2024 23:39:51 GMT" and when installed indicates "Exit f.lux (v4.134)".

Thanks for updating, and thank you for the program.

(This can now be closed. Thank you.)

@karahbit it is not an overlay - only our vignette mode does that.

So, after some trial and error, I found a workaround. It's not the most elegant solution, but it works for me. I manually adjust Flux settings before firing up the game. I tinker with the color temperature so it's not too harsh during gaming sessions. Not a perfect fix, but it beats the constant back-and-forth disabling dance.

@SwaggerBagpipe Which version are you running? Our June 2023 update did address this somewhat: https://justgetflux.com/news/pages/mac/

@scraja4u which version of f.lux, and which version of Sonoma? Also how is the second screen connected? We likely do not support USB connected monitors.

Had this issue also. Didn't even cross my mind that f.lux could be behind it, but now that you mention it, it's worth looking into.

@Juschi the skip button skips the version, and it should not prompt again. We have done several updates recently, which have critical fixes for Windows updates, so you will be prompted for them one by one.

The trouble with maintaining f.lux is that we do feature updates sometimes, but we do compatibility updates often as we're glued between the operating system and a bunch of third party drivers. If we had to explain to each person why they should update we would be having millions of conversations about it all the time.

@herf well, i feel a bit silly. i didnt realize i could actually change my location in the app. i have it set properly now, thanks :)

@Filip yes we have implemented it many times over the years and the main issue is interacting with the half-dozen other systems that do similar things in Windows. Someday we will have something simple and useful enough to ship. ;)

@Nikipe is f.lux working on sidecar with this pause, or is it just using the iPad settings? I guess fast transitions is the best that could be done though we might be able to ignore the sidecar device if needed.

@Night-Prowler usually this means it is using the "basic" driver and you should update to the actual Intel driver. This is the configuration we used to develop f.lux ten years ago so it absolutely should work with the right driver!

@fluxr0x
Open VLC
Click the flux icon in your menu bar (top right of the screen)
Go to "Disable"
Click "for vlc" to uncheck it (or it might say "for current app")
Quit and restart VLC

Worked for me, I never manually disabled flux for VLC so not sure if that's a default setting or what.