@herf, Hello Herf and especially thank you for your link. I dug up the topic, because I did the procedure and unfortunately the DisplayLink folder doesn't seem to exist in my registry.
See the screenshots in on the link page:
https://forum.justgetflux.com/topic/3629/displaylink/11

Thank you in advance for your answer.

@tjerino yes I agree - we definitely have it planned for the website!

The original issue with the interface is that it is very hard to pick a whitepoint if there is not much white stuff on screen, so we have tried dark mode UIs a few times and not been able to sort it out. I will think again if we can do something better here.

@CTS_AE please post f.lux options > driver info here. Usually f.lux uses its "fallback" mode due to a lack of driver support, such as with a USB adapter.

I have two monitors. One is on DVI mode - one is on DisplayPort mode. My monitors go to sleep after 1 minute of idle time. But when I use the mouse to wake it back up, the DVI mode doesn't always go back into Flux mode, instead hitting full blast blue light and all those melatonin-shattering shenanigans.

@Kosake see our thread on displaylink adapters here, you may be able to fix it:
https://forum.justgetflux.com/topic/3629/displaylink?_=1647018111184

@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

@manuelallgaier we will probably do a more programmable thing like this in the future.

We decided not to do it as a one-click option because I found it extremely limiting for some kinds of work. And the main thing is that we don't have a good interface to do a fine-grained disable (like "give me some color back but don't disable f.lux entirely" is hard to do in a simple way). I will think about ways to simplify the interface so we can have this and have a way to turn it off sometimes too.

If your laptop display isn't working, but you can see it on an external monitor, the problem is with your laptop's screen and not its connection. If this is the case, then start to diagnose why there might be a disconnection between your computer and its screen

@Pelimotion
Here is a way to scroll the mouse wheel up/down at the very (top of your screen only) to adjust brightness.
NOTE* you must have Autohotkey installed and run the script. If you don't have Autohotkey, then message me and I'll give you the .exe file.
I have mapped scroll wheel to F.lux default shortcuts Alt 'PGEUP/DOWN' so the default keys will still work but the scroll wheel is better and faster.

#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 }