Colour changed

  • Hi, I have been using f.lux on Win 10 for something like a year now and I had it set to just a mild red effect in the evening and at night which I like, and is similar to what I use on my phone using a different app.

    In the last few days I guess it auto-updated, because now I'm getting a really strong yellowish colour instead of the red I am used to. I have played with the settings and I just cannot get it to give me what I had before.

    There are settings claiming I can set the "color" but I can't find a way of having red instead of this weird yellow which I find really uncomfortable.

    I just cannot use it like this. Is there a way to revert to the old version or to make the new one do red?


  • f.lux team

    The major change in color is

    [x] Options > Use Display Data for better color accuracy

    If you turn that off the colors should match v3 pretty well.

  • Thanks for the reply. That has made it less weird but it is still a yellow hue, no matter what settings I seem to try. All the "color" settings are really "warmth" settings, I cannot set the color at all.

    I can't remember what settings I used before, because f.lux has "just worked" for so long without me touching it until now.

  • Hi, I'm having the same problem only mine looks purple instead of red like I'm used to. The default setting I'm seeing after sunset is Candle but it just doesn't look right. I tried bumping it down to Ember and it just looks more purple. Turning it up to Dim Incandescent is too bright to be useful for blue light reduction at night, though it gets rid of the purple glare. The slider bar just makes it brighter or dimmer, unless I'm using it wrong. The Use Display data option isn't doing anything for me either.

    I'm also having issues with the mouse cursor. It's either a bright white that turns to blue when you move it over a text box (not good for bedtime) or behaving really strangely when I check the box next to "Software mouse cursor when needed". That setting does effectively dim the cursor to the correct level, but when I move it over a text box it completely disappears instead of turning black so I can see it.

    I kind of just want it to go back to normal like the OP but I can't figure it out either. Please help us.

  • f.lux team

    @Rykah84 Can you check this post about NVIDIA to see if it applies?

    Should never be purple unless it's a driver bug.

  • No, it's not like that but thanks for trying. It's more of a faint purple glare if I'm not sitting directly in front of the screen. Even then I get a purple edge near the top of the screen unless I tilt it down to the point of being uncomfortable. I'm almost wondering if it's a backlight setting now. Just to clarify, my laptop screen and backlight were working perfectly day and night with the old version of flux yesterday. It worked fine today after the forced update, and then tonight when the bedtime settings kicked in it just started looking weird. It's hard to describe.

    I was able to fix the mouse cursor just now though. I clicked on something to expand the colors and it rebooted my computer, though I guess a simple reboot probably would have done the same thing. Sorry I didn't try that first. I would still like to get rid of this purple haze situation though.

  • f.lux team

    Did you also try the option to not use the monitor color settings?

    The new version has more extreme colors at night, but otherwise it is very similar, apart from that setting.

    If turning that off helps please let me know.

  • Is that the "Use display data for better color accuracy" setting? It looks exactly the same to me with it off or on. It's currently off.

  • f.lux team

    It may be that there is blue-colored backlight bleed at the edges of your monitor.

    You could try the "eyestrain" or "color fidelity" presets (or even "classic f.lux") - because it sounds like our most extreme setting doesn't look very good on your display.

  • Hi,

    I have updated my nVidia drivers just to make sure, and that didn't seem to help.

    With the box "Use display data for better colour accuracy" ticked, I get a yellow hue that I don't like.

    With it unticked, I think I'm getting no colour or effect at all. F.lux doesn't seem to work without it ticked.

    Is this the expected behaviour? What colour am I meant to be seeing, and is there a way to get red?


  • f.lux team

    There is a very small change to the color transfer function also - we could possibly make a registry option to use the old one instead. So far, we are getting a lot closer to "blackbody" (planckian locus) on every panel we have tested.

    But what you're saying is important - if we have to be "wrong" (and on Windows calibrations often aren't so good) almost everyone prefers "below" the blackbody curve (more red) rather than "above" it (green/yellow, which looks awful).

    Which display (panel model if you can find it) are you using? Does it have any built-in calibration settings?

  • @herf - Why change it? It was perfect! I'm not going to use it like this. This is a mess.

  • f.lux team

    @saritasarita what are you seeing?

    Again, there should not be a visible change for most people if you're using the same kelvin value as before. The change is mostly designed to work better with wide-gamut displays.

    If you're unhappy with the setting, we also changed the preset before bed, and you can move the slider or choose a different preset.

  • Having reverted back to v3, I am not 100% sure any more whether I am seeing a difference between v3 and v4 in "classic" mode.

    Of course in default v4 mode, there is an obvious different during night time, when v4 has a much more intense setting, and I often work very late so I will have noticed that straight away.

    With v4 in classic mode, avoiding the new night time settings, I'm not so sure I'm seeing any difference, although I can't seem to get comfortable with it.

    I will try it a few more days and see if I get used to it.

Log in to reply

Looks like your connection to f.lux forum was lost, please wait while we try to reconnect.