I don't know of any reason it should be f.lux.

Things to check: your "DPI" (under "scale and layout") in Settings.
Logout and back in, sometimes it messes up after an update.

@mfeinstein thanks - yes all the notes since the previous version are there - but this readme is intended for normal releases.

We pulled all the May 2020 Windows people into the beta temporarily to get the bug fixes out, but that will be turned off as soon as it's stable. (i.e. as soon as possible)

Detailed notes are here:
https://forum.justgetflux.com/topic/7507/windows-may-2020-update-2004/1

Now everything is working fine, thanks!

@herf said in Windows May 2020 (2004) Dimming no longer works:

Do you have an automatic brightness feature on your machine?

In 4.116, we are adding an advanced option to use the "internal" color controls - previously we were forcing it on, but we're trying to stop doing that. So you can see if that fixes it....but mainly I would like to find out what is conflicting instead.

I do not. It's a desktop machine so f.lux is my only brightness control.

Just updated to 4.116 and flipped that option on, which seems to have fixed it 👍

Version 4.115 reinstated the issue for me, so now I'm having the same problem again. :-(

Thank you - we will need to add a toggle for this - it didn't look that good when I tried it. :)

Just bought a brand-new starter kit, flux does not find my bridge. Was the old www.meethue.com/api/nupnp endpoint updated to https://discovery.meethue.com?

I had the same problem and it took me a while to figure out it was f.lux.

Doesn't happen immediately after powering up, but rather takes a few hours before I notice it (it's on my second monitor, so it sometimes takes a while before I notice) May have something to do with the latest Windows update and/or freesync, both changes took place in the last 2 weeks Disabling f.lux and using the built-in Windows 10 nighttime mode fixes it

@herf
Same problem here - last days Windows 10 Version 1903 came in, and since then f.lux doesn't work on this monitor.

Driver details as requested:

Intel Corporation 10.18.10.4358: Intel(R) HD Graphics (20151221) Fresco Logic 2.1.34054.0: Fresco Logic IDDCX Adapter (20171113) Citrix Systems Inc. 10.50.21.200: Citrix Indirect Display Adapter (20171107) Generic PnP Monitor, 432 x 324mm, built 2009 Chromaticities: R=0.639648 0.330078 G=0.299805 0.599609 B=0.150391 0.059570 W=0.313477 0.329102 sRGB gamut: 100%, AdobeRGB gamut: 64% Generic PnP Monitor, 432 x 324mm, built 2007 Chromaticities: R=0.639648 0.330078 G=0.299805 0.599609 B=0.150391 0.059570 W=0.313477 0.329102 sRGB gamut: 100%, AdobeRGB gamut: 64% Monitor 1 on Intel(R) HD Graphics: VCGT=0 gamma=1 Monitor 2 on Intel(R) HD Graphics: VCGT=0 gamma=1 Monitor 3 on Fresco Logic IDDCX Adapter: VCGT=0 gamma=1 Windows Build: 18362.836

Below is my driver info

Intel Corporation 10.18.10.3540: Intel(R) HD Graphics 4600 (20140330)
NVIDIA 26.21.14.4587: NVIDIA GeForce GTX 860M (20200403)

PnP-Monitor (Standard), 443 x 249mm, built 2010
Chromaticities:
R=0.639648 0.330078
G=0.299805 0.599609
B=0.150391 0.059570
W=0.313477 0.329102
sRGB gamut: 100%, AdobeRGB gamut: 64%

PnP-Monitor (Standard), 531 x 299mm, built 2010
Chromaticities:
R=0.632813 0.350586
G=0.334961 0.608398
B=0.144531 0.057617
W=0.313477 0.329102
sRGB gamut: 76%, AdobeRGB gamut: 54%

PnP-Monitor (Standard), 344 x 193mm, built 2013
Chromaticities:
R=0.565430 0.330078
G=0.323242 0.577148
B=0.160156 0.144531
W=0.313477 0.329102
sRGB gamut: 74%, AdobeRGB gamut: 48%

Monitor 1 on Intel(R) HD Graphics 4600: VCGT=0 gamma=1
Monitor 2 on Intel(R) HD Graphics 4600: VCGT=0 gamma=1

Windows Build: 9600