The power saves feature on your computer automatically switches off the monitor when the computer hasn't been used for a set period of time, saving energy bills and preventing a condition known as "screen burn" that can permanently damage the monitor display.

@TwoCables said in Flickers daily for a bit at 9pm sharp:

The actual fix is, disable Microsoft's Night Light feature in Windows 10. The flickering is caused by a conflict between Night Light and f.lux. Turning off Night Light is the solution. Anything else that solves it is just "a Band-Aid solution", and is therefore incorrect.

Hey all, reviving this thread for future f.lux users. I tried TwoCable's fix and it worked perfectly. Turn off Microsoft's Night Light feature in Windows 10/11. The night light feature effectively does a similar thing to flux (reduces blue light), and it turns on at a certain time every day. This is causing Flux to flicker at X:00pm sharp.

https://support.microsoft.com/en-us/windows/set-your-display-for-night-time-in-windows-18fe903a-e0a1-8326-4c68-fd23d7aaf136

"Select Start, then enter settings in the search box. Select Settings > System > Display > Night light", then turn off Night light.

done and done.

Found the issue, f.lux had turned off Windows' dark mode but didn't turn it back on again when un-checking the option. Bug fix?

@herf NVIDIA 30.0.14.7298: NVIDIA GeForce GTX 660 (20220105)

ViewSonic VA2248 SERIES, 477 x 268mm, built 2011
Chromaticities:
R=0.643555 0.337891
G=0.309570 0.619141
B=0.153320 0.061523
W=0.313477 0.329102
sRGB gamut: 91%, AdobeRGB gamut: 64%

Unlimited gamma ramp=1, Internal ramp=1
Monitor 1 on NVIDIA GeForce GTX 660
Has VCGT profile=0, Gamma Ramp works=1
Monitor 2 on NVIDIA GeForce GTX 660
Has VCGT profile=0, Gamma Ramp works=1

Windows Build: 19043.1526

second monitor is samsung syncmaster 2223nw
windows 10

@clarkdang12

Install Autohotkey and use this code and run the script.

Scroll the mouse wheel up/down at the very top of your screen only to adjust brightness.
If you don't know how to use Autohotkey then msg me and I'll send you the .exe file

#NoEnv SetWorkingDir %A_ScriptDir% CoordMode, Mouse, Screen #SingleInstance, Force #If MouseIsOvertop() $~WheelDown:: send, !{PGDN} return $~WheelUp:: send, !{PGUP} return #If MouseIsOvertop() { MouseGetPos,,y Return y < A_ScreenHeight - 1070 }

thank you so much!!

Yes it is using the "desktop bridge" to appear in the store. We usually update it somewhat later than the main build.

It will be changing in the future to be even more alike.

Hi, this is still an open issue and it would be really cool if this is fixed in the next version :)

@herf I see thank you. That would explain the problem. I do have an original bridge and an emulated bridge. Thanks for that config option.

Is there currently a manual way to override the IP and can UPnP be prioritized in the future as that is what is shown in the Philips Hue API documentation as well?