Hi,

because you are updating f.lux very often and the reg key is still not implemented, I made my own tool to customize the shortcuts.

If you are interested, you can find sources here http://dl.free.fr/oBZnx22Ln (c#) as well as binaries (needs dot net 4.5, could be downgraded if it is a problem).

I will update this tool for myself, but if another users wants changes, please just ask

Regards

Thanks this is super helpful - will update the FAQ.

oh, thank you!

Can you try the latest version on the website and see if it helps? There are some fixes there.

I think this is it: f.lux keeps the "hue" preference turned on even when pairing fails, and so each time you restart it like this, it will try to make an account. It will tell you in a notifier that it's doing that...but of course you might not jump right up and hit the hue button right then.

We probably should not do this on startup, and instead turn the feature off if it fails... this is broken in the code because we allow you to pair with multiple bridges, and so if you wanted f.lux to control one and not another one, it is hard to show that in the UI.

Then, I think Hue is persisting those attempts forever, even if the pairing is unsuccessful. (The "old" protocol did not do this, so I have an excuse....)

Will take another look at it.

The "classic f.lux" setting has doesn't seem to have the same gentle transition.
0_1515610664767_upload-e057e53b-cfec-4075-9672-64ca9f9ff323

We pushed a small update to the main page that may have helped too - it fixed one problem with fullscreen disable.

The new beta has crash dumps so you can send the information about why f.lux crashed to us. Please run this one:

https://justgetflux.com/flux-setup4.exe

@herf said in Suggestions: Hue optimisations:

Does it work if you restart f.lux instead of turning the feature off and on?

Yes, it works. If f.lux is just faster then the network, maybe there should be a delay you can set, and maybe a number of retries before it gives up.

@herf said in Suggestions: Hue optimisations:

but for me, it was way too much with overhead (ceiling) lights, so that's why it's doing that.

That's the problem, I think. Every user has a different setup, so more configurable options are needed to suit everyone.

Would it be possible to add a hue toggle in the notification area's menu? The way it is now, there are quite a few clicks to disable it temporarily. Sometimes, I just want other software to control my lights.

No. I am talking about the response time. The refresh rate is separate and completely different and unrelated to the response time. That's why I am talking about values like "1ms" and "2ms". If I were talking about the refresh rate, then I would've been talking about values measured in Hz.

Changing the refresh rate is not going to make any difference - or at least it shouldn't.

So again, find out how to adjust the response time (if it's even possible) of your 60 Hz monitor. You are probably using the highest possible response time right now. I am speaking from experience here.

I put a note at the end, will fix the version thanks.

Because you asked: antivirus programs pull our EXE our of the installer but don't run the installer so all the UI resources are missing. This was crashing, and we had like 15 of them submit the crash log to us. (Almost no other crashes, so I fixed that one.)

Here is my driver info.

Intel Corporation 20.19.15.4531: Intel(R) HD Graphics Family (20160929)

Many people with this problem have USB-connected displays, and if you are running Windows 10 Anniversary or Creators this should work:

https://forum.justgetflux.com/topic/3629/displaylink

This usually means that f.lux is using its emulated mode, and instructions are here to fix it:

https://forum.justgetflux.com/topic/4653/tinted-screenshots-or-games-missing-f-lux

If you're trying to access it through the start menu, try the tray icon instead.

Also, the newest beta (4.60) fixes this bug: https://justgetflux.com/flux-setup4.exe so you can access it through the start menu too.