No color changes under Windows Insider 19H1
-
F.lux starts as expected, but none of the expected color change is working in the latest Windows Insider builds.
Driver info
The information below is already on the clipboard. Paste to the f.lux forum or email us for help.
MirrorOp 1.1.110.31: MirrorOp Virtual Graphics Adaptor (20180619)
Intel Corporation 25.20.100.6471: Intel(R) HD Graphics 630 (20181210)
NVIDIA 25.21.14.1678: NVIDIA Quadro M1200 (20181101)Generic PnP Monitor, 346 x 194mm, built 2016
Chromaticities:
R=0.639648 0.329102
G=0.209961 0.709961
B=0.149414 0.059570
W=0.312500 0.328125sRGB gamut: 100%, AdobeRGB gamut: 100%
Windows Build: 18312
-
Same here. Have let M$ know..
-
I am in the same boat.
NVIDIA 25.21.14.1735: NVIDIA GeForce 940MX (20181211)
Intel Corporation 23.20.16.4849: Intel(R) HD Graphics 520 (20171027)Generic PnP Monitor, 381 x 214mm, built 2015
Chromaticities:
R=0.646484 0.337891
G=0.316406 0.614258
B=0.157227 0.043945
W=0.313477 0.329102sRGB gamut: 87%, AdobeRGB gamut: 61%
Windows Build: 18312
-
temporary fix here:
https://justgetflux.com/flux-setup4-91.exeWe are waiting on MSFT for the real fix.
-
Thank you, that got f.lux working again!
-
Thank you, I've been at a loss without f.lux!
-
Interesting side-effect of using the beta (at least with 4.94) on 19H1 (at least with 18317) is that when you're making a screenshot (the program doesn't seem to matter, but Snipping Tool is handy), at the moment when you're selecting the part of the screen that you want to capture, the color temperature of the screen drops way down until the capture is complete. And the captured image takes on that hue! I've never seen that before, and it doesn't happen with f.lux disabled.
NVIDIA 25.21.14.1681: NVIDIA GeForce GT 730 (20181102)
Dell U2415(HDMI1), 518 x 324mm, built 2017
Chromaticities:
R=0.660156 0.332031
G=0.301758 0.613281
B=0.150391 0.063477
W=0.313477 0.329102sRGB gamut: 100%, AdobeRGB gamut: 69%
Windows Build: 18317
-
That problem went away, but with 18323, I think we're back to the original problem, at least with 4.96.
MS hinted at it in the release notes:
"While night light functionality is back up and running, you may still find issues with other blue light reduction software not working." -
We just pushed up compatibility bits for 18323.
Restarting f.lux should keep the workaround going.Looking into what's new in this build.
-
@rseiler also yes this screenshot thing is expected - we are using the GPU for this mode (not ideal), but we're waiting for the normal windows color plumbing to stabilize before doing anything else. seems like they're making a lot of changes.
-
Hi All,
using the 18323 and 4.96 version, it works perfectly except for brightness. I was using this feature a lot and now I have to set it manually by going into my screen's settings (Physical buttons).
Any way to get it working soon ?
Regards
-
Looks like 18329 has done its thing, and it wasn't even because of a change relating to fixing the 3rd-party compatibility problem, since they haven't gotten to that yet.
-
ok, restart f.lux - I pushed our compatibility bits for that one too.
-
As if by magic, thanks.
BTW, I think they broke Night Light again with this build, so everything is very much in flux right now.
-
Reporting in with 18334, same thing. Whenever you get a chance, thanks.
-
pushed - hope they fix it soon.
-
Only getting 4.66 through the Microsoft Store for some reason. Tried 4.91 and it isn't working. Only when I went to 4.96 did it work.
NVIDIA 25.21.14.1881: NVIDIA GeForce GTX 980 Ti (20190130)
LG HDR 4K(HDMI), 600 x 340mm, built 2018
Chromaticities:
R=0.679688 0.315430
G=0.280273 0.673828
B=0.152344 0.049805
W=0.312500 0.329102sRGB gamut: 100%, AdobeRGB gamut: 79%
Windows Build: 18334
-
They're up to old tricks in 18836, the Skip Ahead jump build.
-
@rseiler thanks - included 18336. hope these workarounds are not delaying a "real" fix somehow!
-
@herf It might be just me, but after restarting it doesn't look like it had an effect.
When I first saw the build #, I read it as 18336 and not 18836, which is what they made it for some reason. Is that possibly the reason?
