I haven't disabled it from the flux app, if that is what you're asking. As I mentioned, it works well when the cursor is hovering above a link. When it is not above a link, then it instantly becomes brighter and harsher - however, not as bright as when it is turned completely off. This happens whether or not I am in fullscreen mode, but if the window is not fullscreen, it is only the Chrome window that has this problem - the rest of the screen stays nicely reddish. I also just noticed that the problem doesn't seem to happen in tablet mode. When it is in tablet mode (ie rotated vertically), f.lux seems to work fine and there is no flickering at all, with Chrome or anything else.

EDIT: The chrome window also seems to flicker when I disconnect the surface type cover.

Is it going into the hidden icons area? They are doing things a little differently with their icon and perhaps it's slow to update the location of the icon when it moves to the area for hidden icons. So perhaps its disappearance can only show now if the mouse cursor touches where it once was.

Yes, I have been working on this for three years (including adjusting the backlight), and pulled it out at the last minute because it wasn't working quite right.

It works a lot better with light sensors built into a screen....but so few PCs have them still that we may have to do it!

You're welcome. Did this work for you? I've seen this before and sometimes it doesn't.

@RaphaelB thanks - have sent you an email with a test app that will help us debug this. Thanks!

It's working now. Thanks for quick fix.

All of the transitions. Any of them. It's not just some of them or most. It's all of them.

I have a GTX 780 and changing driver versions makes no difference, but I prefer using 376.33 right now.

@hsiktas thanks we will take a look at extended characters

Installed 4.37 and did a quick test: all issues seem to be fixed, thanks for the quick update.

If I stumble across anything else, I will report back. Keep up the good work!

the disable for fullscreen works for me in BF1, it disables flux when I run it, but I don't see message saying it does as I do in some full screen app, like fullscreen you-tube vids.

I am on 4.35beta

I have this issue too, but it only seems to occur when I either "duplicate" the displays, or when I connect my laptop to an external monitor, and then disable the laptop monitor.

It's fine under all other use cases, e.g no external monitor connected, or "extending" the displays rather than disabling the laptop monitor.

There is a "disable by app" feature in this version. Can you check that you haven't checked it by accident?
See the disable menu from the f.lux icon when you're running the affected app.

I use a laptop that has switchable graphics AMD Radeon HD 6620G and AMD Radeon HD 6750M

Windows 10

100%. It even disrupts you from viewing videos full screen. Should be option to disable it.

@disqQ we fix problems we can reproduce, and we haven't reproduced the NVIDIA issue yet. Can you keep us up to date with NVIDIA issues in another thread? Driver versions, and if any driver versions have worked previously?

@TwoCables said in UWP f.lux:

Also, as you can see from the update page, it says "These pages are popping up too early for Windows App Store users. Sorry, we’re working on a fix!"

Sorry, I totally missed that! It's good information to know! I will probably just stick to Windows App in this case since developers know about the issue :-)

Thank you for the very quick reply!

Yes, the scheduling is more complicated - there are several "ok" schedules but most people do not achieve them. Avoiding daylight is a bigger concern than displays from a circadian perspective.

General advice: set your wake time in f.lux, but set it a few hours earlier than you actually wake up.