@amerykanin Emailed you again

also one additional piece of info - it could be amd specific compatibility.

i asked someone on the internet and they're using windows 10, nvidia's 1060 and 3080 and apparently those doesn't have the same lag issue as mine.

Thanks, enabling "Always use Windows internal color table" fixed the problem. I have not otherwise noticed a difference. Are there disadvantages to enabling that setting? Also, do you know if Microsoft is aware of the problem?

Hi - we have only noticed the issue on window create. That is, they should only steal focus one time.

There are a few reasons we draw our own right now:

We support Windows 7 (though this is less an issue over time) We draw animated results in the notifiers (for instance, while dimming) The interaction with native code and windows "modern" notifiers was a bit difficult when we wrote this (they live in two separate universes, or did at the time). For instance, at one point we were registered as a new "app" on every launch, and we filled up the SQL database Windows uses for managing notifiers with thousands of entries, all named "f.lux" - that was pretty upsetting for our beta testers.

#3 was the immediate reason we took this out but it is probably easier to make it work right now.

Thank you. I will have to try the driver updates by submitting a service ticket. I can't even end those processes without administrative access.

Can you try changing your wake time to an earlier one?

We assume if you wake up early that you still want to "rest" even if you're not asleep.

Usually this is due to a USB-connected monitor that doesn't support color transforms, so f.lux is emulating them using the GPU. If you would like to post f.lux options > driver info, we may be able to help.

If they are all DisplayLink adapters, this article should help: https://support.displaylink.com/knowledgebase/articles/1886413-how-to-enable-night-light-or-f-lux-on-displaylink

Thanks - we will fix. This was only supposed to update when you pull down the menu (otherwise it can cache because it's not changing).

For reference, I've observed this issue on HollowKnight, and on MTG Arena. But I suspect that it'll apply in any game which overrides the default mouse cursor, and then resets it on close?