@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

@ManualControl I have also been wanting this for years. I am really getting annoyed by being blinded at random times in the morning. It should be easier to give manual control than to set up an automated system. It makes no sense.

It is only a text readout in the main interface. We are working on more things around it.

But for now, you just look at the solar time, and look at your normal clock, and think a bit about how they're different. :)

@herf I have prerolled the version of Nvidia but it seems to be the issue aswell. It seems like this happend of a update of WIndows and I am not able to reroll a windows version :( But it should be a bug that f.lux should be checking pretty soon because I guess lots of people do have this bug?

@mrelarsen said in Flickering at specific times:

Hi, f.lux starts to make my screen flicker every day at 21:00 and 7:00, Not sure why... the color goes from around 1936K to 1935K at that time if that helps in any way, it happens on both my laptop screen and my external monitor.
I usually just have to disconnect and reconnect my external monitor for it to work again.
If I do not have my external monitor connected it does not really flicker instead it switches to needing to be in focus, f.lux only works when focused on in the taskbar and the tint is removed when not focused.
I tried an experiment with an external monitor connected where I set the time to 20:59, f.lux then disappeared at 21:00 as expected and 3 minutes later at 21:03 the tint reappeared... 1931K

Turn off Windows Night Light.

Thanks for the hint !
Updated the NVidia drivers and that fixed the problem, along with many other odd flickering problems.

I thought I had updated my drivers recently by asking GeForce Experience to do it, but turns out it just triggered the driver download, waiting for a second confirmation to do the installation.

the Lenovo team kindly provided a work-around that stops the problem here.

so if anyone else struggles with this problem, give it a try.

OK so I've learnt the terminology I should have used was transitions, and I've figured out that it's only broken when they're set to Slow. When they're set to Medium they appear to work 100% of the time.

We do open each process one time (and close it) to find its filename for "disable by app". Do you happen to use that feature? We should not keep these handles open, but it's always possible that things get messed up.

If you're inclined, you could use Process Explorer to see what f.lux is doing:
https://docs.microsoft.com/en-us/sysinternals/downloads/process-explorer