No color changes under Windows Insider 19H1
-
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?
-
try again
-
@herf Still no effect that I can see.
-
F.lux (and Night Light) stopped working on Insider build 18836.
Hope you can push a workaround soon, my eyes are so used to always having F.lux in the evenings :) -
Ok sorry I missed the note about 18836 not 18336. Pushed two blocks of exclusions just now, agh.
-
@herf Thanks! It's working.
-
Yes, all good again.
Things should get really fun soon, since MS is going to continue pushing out 183xx builds while developing 188xx (two different sets of testers).
-
No real updates in current builds on the general issue beyond statements like:
"While we’ve done some work to improve night light reliability in this build, we’re continuing to investigate issues in this space."
Which I take to mean includes 3rd-party, as f.lux doesn't work in today's 18841.
While I haven't tried the other two builds this week--18342 and 18343--they should be in the same boat.
