Nothing on this?

We are sorting results by population - for now can you use "City of Worcester"?

We stopped using Google Maps with their 15x price increase so we aren't as good as we used to be with figuring out "which" name is meant when someone types a query.

@shenmue-is-life said in Max luminosity very low since F.lux update:

Restarting the OS fixed the issue, thanks.
Needed some time to save all my works before reboot so I was looking for a faster solution.

Oh! Ok.

How exactly are you accessing f.lux? Take me through it step-by-step.

Are you able to update your video drivers? there has been a lot changed in Windows since 2016.

Also, windows has a section called "Color Filters" that might help you do this.

Sadly vers. 4.100 didn't do anything either ;-(

I installed 4.99 and it seems to have settled down and is working as expected...

whilst playing i found a temp fix by pressing the windows key than clicking back on apex legends on the task bar. You might have to do it a few times but eventually f.lux will work on fullscreen.

Yes some of the insider builds disabled color correction so we are working around it. Update to latest for better results.

Turn off Windows Night Light.

Hi, I'll re-install the latest version and let you know; for the time being I reverted to 4.78 that doesn't use the Win+End hotkey which I already bind to my media player's play/pause function. Would be nice if we had rebindable keys even if just in an .ini file or something of the sort.

It seems 4.97 isn't quite as bad as 4.84 in terms of looking so washed out. It's just less washed out. It's nice to have the setting enabled called "Use GPU for better quality with warm colors" because it makes things visible and easy to see that are otherwise next to impossible to see. So, I don't know. Maybe I like it!

Welp, managed to fix it last night. For those that get the same error I'll post my solution.

I ran "dism.exe /online /cleanup-image /restorehealth" in Command Prompt, then "sfc/scannow"

Seemed to do the trick!

@chaxha Of course I find a workaround as soon as I finally post this. I disabled flux for the app I had open on my second monitor as well - and now it works correctly (i.e. it doesn't turn my brightness down).

Hope this helps anyone with the same issue.

I have this precise problem as well - and have gone through the troubleshooting steps provided in other threads on this same topic, to no success. I would love to find a solution to this, as I also use screenshots all the time! Any insight welcome.

Thanks for the note. We did try in our beta to do this for "most" notifications but we wound up messing up the notification center pretty badly, so we stopped.

The interaction between "native" apps and the "modern" APIs is still a little difficult on Windows. For instance, we never had much luck handling notification clicks and other cases like that, especially if someone clicked a notifier after we updated.

We made the notifiers as they are to support Windows 7, and to handle the notifiers we make that animate over time (which isn't possible that I know of with the system). Then we wound up using them for everything due to the notification center problems.

Also we used every API we could to see if Windows is in "do not disturb" mode (presentation mode, fullscreen, etc.), and tried to suppress notifications -- there are like three different things we check there. I would assume that the "modern" side of Windows is not talking to the native side again there -- possibly even the "do not disturb" feature is quite new, since we shipped this version of f.lux.

Will look into it more.