@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.

@Rouxbourbon f.lux has an options to "Always use Windows internal color table" which emulates Night Light, so this might be a workaround.

Changing screen colors is unfortunately not a very good place to run multiple apps at the same time, as the order of what should go first is not defined.

@Quincel yeah they are becoming upsettingly rare on modern laptop keyboards. A few thoughts:

Since most laptops have "brightness" keys already, we did not work very hard at finding an alternative for laptops. The trouble with hotkeys generally is that it is very hard to find one that doesn't conflict with another app.

We do support "surface keys" which allows Alt+F11 and Alt+F12 to do the same thing - you have to turn it on in f.lux options.

In a pinch, you might be able to get an app like AutoHotKey to alias those keys that we register

@spaceowl I think you are right here - the code used to look at window titles for this, but it doesn't do this anymore. The behavior you're seeing was for better matching of apps that put their name in the title (with the name of a document or something alongside), but it looks like we stopped doing this some time ago.

I will make a change in the next beta and we'll see if anything breaks. thanks!

+1 for this issue. I applied the registry flag mentioned above and while the Windows setting does change properly, the UI doesn't. 1855444f-4235-4530-8a96-00c33959110c-image.png

A workaround is to use the open source app "AutoDarkMode" to handle theme switching and disable the option in f.lux. It would be nice to have this work properly in f.lux to reduce the need for extra apps.

@f-lummoxed good memory, there was an easter egg and it needs two things:

the Preference in the registry* for "candle" has to be turned on you have to hit the 'c' key while the f.lux UI is up

It got turned off during one of our "don't do things that the user can't figure out how to undo" cleanups... but the pref is still there.

HKCU\Software\Michael Herf\flux\Preferences\candle = REG_DWORD(1)

@cxuj6464 It really depends on what the GPU manufacturer is doing (sometimes things break in driver updates since Win7 was EOL in 2020) - I would try a few different drivers (maybe older ones) to see if Win 7 support still works using those.

@Alfal yes this is a known issue and reported to Microsoft - we usually see it happen once per f.lux session.

@guillaume1978 this is because the dock does not provide traditional color controls, so f.lux has to emulate them using the GPU.

If the dock happens to be a DisplayLink one, you can sometimes add these controls back using the registry: https://support.displaylink.com/knowledgebase/articles/1886413-how-to-enable-night-light-or-f-lux-on-displaylink

Probably this is legitimate - we have shipped a "root-only" version in the past that doesn't ask for permissions, but root is a different level of privilege.

Hi Nick - you could try our "working late" preset, which turns off the solar cycle, and only bases the color on wake time. It should fade then about 9 hours before your wake time.

@lskang your question is about the arm GPU, not the processor itself like the rest of this thread.

What we know is that the Adreno GPU (on Snapdragon X) does not support external monitor color changes at all and so we have a workaround in the works that uses a shader instead. It's not ideal...

@ned_arb got it, yes we have some fixes coming for these machines, but at least some of the Adreno/Qualcomm devices have no working support for external monitors

@bluepenguin It works and it's so much better now!
Thank you.