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.

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 :)

@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!

@herf thanks for the quick reply Herf, it seems location access for my laptop was set to "off", but I still had to update location manually in F.lux (on the bottom right) and it's working now, thanks for the help!location.PNG

@lech7 yes, it is a brightness backoff, so f.lux will not override other controllers' brightness settings.

However, f.lux will use its color settings all the time. There are some adjustments for how we map screen colors to hue colors, however.

@herf Backoff doesn't seem to be working for me at all. I'm in 4.131, I have Backoff checked, and when I use my hue app to change the color, the color changes right back to the f.lux controlled color a minute later. Pausing f.lux also doesn't pause the hue lights control.

@herf I'm having the same issue, with this driver info:

DisplayLink 11.2.3146.0: DisplayLink USB Device (20230926)
DisplayLink 11.2.3146.0: DisplayLink USB Device (20230926)
DisplayLink 11.2.3146.0: DisplayLink USB Device (20230926)
DisplayLink 11.2.3146.0: DisplayLink USB Device (20230926)
Advanced Micro Devices, Inc. 31.0.21024.5: AMD Radeon (TM) Graphics (20230718)

Generic PnP Monitor, 527 x 296mm, built 2022
Chromaticities:
R=0.652344 0.335938
G=0.321289 0.610352
B=0.153320 0.060547
W=0.313477 0.329102
sRGB gamut: 86%, AdobeRGB gamut: 60%

Generic PnP Monitor, 345 x 215mm, built 2021
Chromaticities:
R=0.594727 0.370117
G=0.363281 0.552734
B=0.155273 0.102539
W=0.313477 0.329102
sRGB gamut: 51%, AdobeRGB gamut: 34%

Generic PnP Monitor, 527 x 296mm, built 2022
Chromaticities:
R=0.652344 0.335938
G=0.321289 0.610352
B=0.153320 0.060547
W=0.313477 0.329102
sRGB gamut: 86%, AdobeRGB gamut: 60%

Unlimited gamma ramp=1, Internal ramp=0
Monitor 1 on AMD Radeon (TM) Graphics
Has VCGT profile=0, Gamma Ramp works=1
Monitor 2 on DisplayLink USB Device
Has VCGT profile=0, Gamma Ramp works=0
Monitor 3 on DisplayLink USB Device
Has VCGT profile=0, Gamma Ramp works=0

Windows Build: 19045.3930

On my laptop's built-in display, the extra effects work, but not on the external monitors.

@GoldenRelik you can post "f.lux options > driver info" and maybe email us a video from your phone? (support at justgetflux.com)

hi sorry, about half the posts here are spam so we had to do the manual filter. it's mainly me - will try to keep up to date.

@fluxie can you email us your profile (ICM)? support at justgetflux.com

@fluxie it is the main download now, we are slowly rolling the update.