Absolutely! This is one of the biggest things I've wished would be integrated with the app.

We are tracking this bug on m5 pro and max (with built-in displays) - you can read more here:

https://developer.apple.com/forums/thread/819331

We hope there will be a fix in upcoming macOS builds.

We believe that all M4-era MBPs and Neo are working. It is the "pro" M5s with a retina XDR that are not.

@Gunther3613 hi gunther - the app store version sometimes uses a "virtualized" registry, which is a separate hive, basically a separate registry file.

You may be able to open up registry.dat within the app folder from regedit, but I am not sure how it is protected. We probably should do this at the app level rather than make you do this kind of thing.

@gen123456 yes this has been a windows issue for some time, you can use the "internal color table" in Windows under f.lux options if you it bugs you.

@Alfal first thing is check your clock using http://justgetflux.com/timesync.html

After that, the lat, long (and the pin on the map) should match your location.

@Lumbis you may want to try our new beta v4.141 - the previous version was over-eager at matching names and this one is more careful

@herf said in flux unloading - win10:

@terryd fnaf hi terry - this could be a lot of things, but the simple possibility is that f.lux could be crashing for some reason.

We made a major effort to remove our (rare) crash bugs in the latest beta, which I would recommend joining to see if it helps:

https://forum.justgetflux.com/topic/6289/to-join-the-f-lux-beta

If this doesn't help, post back with f.lux options > driver info

The issue is completely resolved in this beta version.

@ForwardVision thanks we haven't been tracking this closely from version to version, but we're grateful they're doing it. Is it when you switch desktops or just any window?

@Simon144 no did nothing wrong, we never finished this on the Mac, mainly because it requires a machine to stay on 24/7 and our macbooks were too good at sleeping. Maybe in the future...

@pooparse thank you for the encouragement.

We did not have much luck getting a supported API (no root) working with f.lux, so we let it expire - the intention was to have it be a demo on the way to having a supported app.

@rice_goblin since it's happening during a game, it sounds like the NVIDIA display settings may be the thing to check. If you have an "NVIDIA control panel" can you see any color settings there, and try to reset to defaults?

f.lux does not leave any state that's permanent in the system, so usually a problem like this lives in the driver, somehow or another.