Hi,

I very much want this option, too. The biggest problem with the notifications is that they sometimes steal focus. This is especially annoying if f.lux is disabled for applications that prompt for a password on startup. You start typing the password and suddenly the focus is on the notification. So either fix the focus problem or allow to disable them at all.

Thanks

I solved it. The problem was not the f.lux itself, but in so called Pixel dot-inversion. I can't say i understood right how it works, but briefly all LCD monitors are flickering on some brightness\contrast values. For example my IIYAMA flickers like mad at 79 and 81 brightness but goes smooth at 80. When i acitvate f.lux i get flickering at 3450, and 3350, but 3400 is perfect. There are also some monitor settings that make your screen flicker.

There's a visual test for that http://www.techmind.org/lcd/dotinvrgb2lb.html and an article that explains all this. I finaly understood why i had everything back to shape when i did windows restore.

Took me some time to google all this out. Maybe this will help someone having the same problem.

@n8abx9 said in I am getting Windows 10 soon. How should I install f.lux?:

I would strongly caution against installing f.lux on Windows 10 at all. There are huge problems, dimming only ever kicks in AFTER log in, which makes it almost useless.

It’s been that way since the very beginning. It’s not specific to Windows 10.

It’s impossible to have f.lux start up before login. This is a limitation that has always existed in Windows, long before Windows 10.

@uiser356262 @kpoviv
It really does defeat the purpose of using F.lux in the first place, to keep your circadian rhythm in sync. But to answer the original question, you would just set the daytime, nighttime and bedtime sliders to the same level.

Click on the Flux icon in the taskbar

In the window that opens, click on little orange dot (or the three bars menu icon in the top left and choose Adjust day and night together)

In the 3 sliders that appear, set them all to the same level of your preference

@herf said in f.lux unwanted dimming of display on desktop PC, and leaving it dimmed when disabled, and even when quit.:

First question is: do you have HDR turned on in Windows?

We are investigating the new HDR support on NVIDIA in the latest drivers, but it does seem to behave quite differently than the normal color controls.

@herf, did you get the private message I sent last week that the brightness seems to have resolved itself? I asked if you had done something to F-lux that might have corrected the brightness issue, but got no reply.

At this time it seems to be behaving itself again, with the <alt><pgdwn> and <pgup> working properly in HDR mode. I am going to try doing an dimming and then suspending the program and see what happens.

Results of that testing:
Disabling for an hour worked, and the brightness and color came back up.
Exiting f-lux also worked properly, with the brightness and color being reset to default values immediately.
restarting f-lux went properly as well, with the slow color change and the <alt><pgdwn> and <pgup> working properly again.

I have not installed any new drivers since I reported the incident last week, nor any windows updates. Have you folks updated something?

Please advise,

Philip

Latest drivers and still nothing.

DisplayLink 9.2.2420.0: DisplayLink USB Device (20191023)
DisplayLink 9.2.2420.0: DisplayLink USB Device (20191023)
Intel Corporation 26.20.100.6888: Intel(R) HD Graphics 520 (20190516)

Generic PnP Monitor, 308 x 173mm, built 2015
Chromaticities:
R=0.617188 0.334961
G=0.325195 0.573242
B=0.161133 0.070313
W=0.313477 0.329102

sRGB gamut: 82%, AdobeRGB gamut: 53%

ViewSonic VG2453 Series, 527 x 296mm, built 2018
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%

ViewSonic VG2453 Series, 527 x 296mm, built 2018
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%

Windows Build: 18362

The same thing happen to me
Latest nvidia drivers, 1080 Ti