@Jokester2101 You have the "hotkeys" checkbox off, so it should not affect the Windows key.

The only place we register a hotkey is related to this, and if f.lux is relaunched it does not even call the windows code to ask for the hotkey. It's specifically registering Windows+End.

@hehee we will look into it - this means that f.lux saw two different states in the hub, and to avoid a "race condition" where we fight another app, we are waiting for it to be stable before making changes. But as you say it would be annoying if it is always doing that.

Hi!

This is exactly what I am looking for too. Making everything monochrome red is great. But why does it inverts everything at the same time? That should be a separate thing. All my icons look odd, all shadows are wrong, photos are useless, faces cannot be recognised, basically everything looks bad. So instinctively I've tried to use MacOS built in inversion feature to "fix" it, but unfortunately macOS inverts the image after it is tinted red by f.lux, so in inversion mode it becomes cyan. (My brain froze when I switched. I didn't expect the amount of blue light into my face.)

I'd assume it could be very hard or almost impossible to make f.lux filters come after OS level filters, so it'll never play nicely with macOS built in inversion feature I think.

But that should not mean that the red filter should only be available with inverted luminance. Can we gat a mode / option to use red filter without flipping dark and light parts of the screen please?

@herf

I am getting this too with Sharex

July032024_23h10m20.png

I had the "glowing cursor" issue on a (Samsung widescreen) external monitor in Mac OS X. The solution turned out to be turning off the "High Dynamic Range" setting for the external monitor (after which the picture in general seemed better too).

work! ty

@herf I did that and also updated my GPU drivers. Same issue only when using f.lux and rebooting. Perhaps it only affects certain hardware. I have a Surface Laptop Studio 2. Are there any logs I can provide you?

I have made a pretty big jump from Windows 7 to Windows 11 in last few months. On Windows 11 I am experiencing the same thing and it's killing my eyes. In my case, f.lux gets disabled once the system receives a notification which usually comes from Outlook in my case (new mail). After few seconds, the colors are back to yellow automatically, but this quick moment is enough to receive a deadly dose of the blue light in the evening, I have never experienced it working on Windows Vista & 7 for 15+ years.

@Burgerkrieg I think I figured it out, at least in my case. Checking "Always use Windows internal color table" fixed it for the misbehaving monitor, which was otherwise doing exactly what yours was.

@herf Yes, they support HDR. To be specific they are both an Acer Nitro 27".

Additionally, I am using Windows 11's Auto HDR setting. Which, to my understanding, changes a display to SDR if the content (or just games? That is all I see it with at least) does not support HDR.

@Chikins the ones we read say "VCGT profile=1" so it is not a full profile in this case.

@tyealia yes the DisplayLink device is forcing them all to use the same settings because the USB adapter has disabled color settings. See if this post helps: https://forum.justgetflux.com/topic/3629/displaylink

@jeffb the main thing to check is that the "correct" color profile is used for the mac monitor (it should say "Color LCD" the System Preferences > Displays > color)

Also, we did make an update a few years ago to support DCI-P3 displays (like the new Macbooks), so make sure your f.lux build is up to date also.