Issues with f.lux not going below 3400K/Going grayscale
Caledorn last edited by Caledorn
Yesterday I tested out a new monitor on my computer, and before connecting that monitor, f.lux was working perfectly. I couldn't use the new monitor, so that will be returned, and I'm back on my regular setup - but f.lux is having some very weird issues now.
Moving the temperature slider up and down will make the tint and brightness of the colours change. However, at maximum, instead of making my display very bright as it used to, it turns it blue-ish. Whereas I see very little-to-no difference going below 3400K - with the exception of the nearer it gets to 1200K, the more grayscale my colours become instead of red.
I thought that perhaps the issue was an update to another eye application I use (eyeblink) that has a built in colour temperature thing as well, but I have disabled that feature of that program - and I even disabled eyeblink from starting altogether in the Startup section of Task Manager, and the problem did not go away.
I also reinstalled my Nvidia drivers - and uninstalled and reinstalled f.lux. But I can't seem to fix this issue. I have a type of dry eye condition that makes looking at bright colours uncomfortable, and I have to hydrate my eyes with artificial tears multiple times per day (thus the combination of eyeblink that reminds me to blink, and f.lux to get warmer colours), so this problem is something I really would like to get fixed.
NVIDIA 184.108.40.20614: NVIDIA GeForce GTX 1070 (20200515)
BenQ XL2420T (DisplayPort), 531 x 298mm, built 2012
sRGB gamut: 92%, AdobeRGB gamut: 64%
ROG PG279Q, 598 x 336mm, built 2018
sRGB gamut: 100%, AdobeRGB gamut: 64%
Monitor 1 on NVIDIA GeForce GTX 1070: VCGT=0 gamma=1
Monitor 2 on NVIDIA GeForce GTX 1070: VCGT=0 gamma=1
Windows Build: 19041.329
Thank you for your help!
Caledorn last edited by
Update: Uninstalled f.lux, did a "Clean Install" of the Nvidia drivers in the custom part of the driver installation process, reinstalled f.lux. All working again now. Just in case someone else has similar issues and reads this!
corbe last edited by
Good that you found a solution. This is happening to me as well and this solution didn't work Ever since the 2004 update for windows 10 2 days ago. Any help out there?
pratnala last edited by
@corbe Get the latest update for f.lux. Maybe it fixes your issues?
Caledorn last edited by
Version 4.115 reinstated the issue for me, so now I'm having the same problem again. :-(