f.lux beta discussion
-
@Neobond I am pushing 4.19 which resets the pref to "slow" because that's what we meant to do. You can change it if you like.
-
[Suggestion] f.lux beta (4.18) - Change "Recommended Colors" file location
f.lux beta (4.18)
OS: Windows 7 64-bit.f.lux program files install to:
%LOCALAPPDATA%\FluxSoftware\FluxThe "Recommended Colors" profiles install to:
%LOCALAPPDATA%\flux\*
%LOCALAPPDATA%\flux\media\offer.json
%LOCALAPPDATA%\flux\media\preset.jsonCould you install the "Recommended Colors" profiles underneath the f.lux installation folder? e.g.:
%LOCALAPPDATA%\FluxSoftware\Flux\media\offer.json
%LOCALAPPDATA%\FluxSoftware\Flux\media\preset.json...and not even create:
%LOCALAPPDATA%\flux\It just reduces the amount of clutter in the %LOCALAPPDATA% folder.
-
@pizzaguy Yes I had just fixed this in 4.19, so you can delete the extra "flux" folder at the top level.
-
[Suggestion] f.lux beta (4.19) - Display color temperate along with the preset name if you select a value that currently just has a preset name displaying.
When you adjust the sliders on the "Adjust all colors at once" page the current behavior is to display just the preset name (e.g., Daylight, Sunlight, Fluorescent...) if you happen to slide to it's corresponding value. Could you have it to where it would also show the color temperature with the preset name.
CURRENT:
It's daytime ----------------------o Daylight
Sunset ------o---------------- Halogen
Bedtime o---------------------- CandlePREFERED CHANGE:
It's daytime ----------------------o 6500K (Daylight)
Sunset ------o---------------- 3400K (Halogen)
Bedtime o---------------------- 1900K (Candle)or
It's daytime ----------------------o 6500K: Daylight
Sunset ------o---------------- 3400K: Halogen
Bedtime o---------------------- 1900K: Candle -
@herf Yes, that was the problem. Firewall was blocking f.lux and now everything is fine. Thanks!
-
I've tested the f.lux LAN API with Node-RED, and it works! Now... to figure out what I want it to control...
-
Seems like there is a bug and the mouse pointer does not change temperature. This is after my having just updated to the new Windows 10 15063, so not sure what was happening before that.
-
Can you add an option to install to C:\Program Files? Binaries have no place in %appdata%, and this breaks application whitelisting.
Previous versions could handle being moved to Program Files, but this version doesn't.
-
Is it possible to make the transitions between colors more smooth like in the previous version of flux, where you could set them to slowly occur over like an hour or two instead of being so jarring? I really liked that and miss it here, but I don't know if I just can't find the right settings options for it.
-
@dreadnaut said in f.lux beta discussion:
@herf said in f.lux beta discussion:
@John-Smith123 the graph is your sensitivity to light over time
With a double line, and lacking a vertical scale and an explanation, the graph is quite confusing. And how should this inform the choice of settings of the user?
Other questions:
- If I add my own preset to
preset.json, will it be overwritten when they update from the server? - I would like to disable dimming completely, is there a configuration setting for that?
Dimming? Or color temperature changing?
- If I add my own preset to
-
@wigster said in f.lux beta discussion:
Seems like there is a bug and the mouse pointer does not change temperature. This is after my having just updated to the new Windows 10 15063, so not sure what was happening before that.
This isn't a bug with f.lux, it's a limitation with Windows. You are probably just now noticing it because the new version is making you pay much closer attention to everything. No previous version of f.lux that I am aware of can render the mouse pointer so that it is colored too.
To get the mouse cursor to be rendered as well (so that its color is changed), you can do one of the following 2 things:
- Open Windows Magnifier
- Make a simple change in the Registry (you will have to log out or restart Windows to see the change take effect)
If you wish to make the change in the Registry, then open Registry Editor (regedit.exe) and nagivate to this key: HKEY_CURRENT_USER\Control Panel\Mouse
In the right-hand pane, just double-click the sub-key named "MouseTrails" and change the value to either 99 or -1. Both should do exactly the same thing, but on rare occasions one is better than the other in some way. So if you choose and find any problems at all, then try the other and it will work better.
Again, log out or restart Windows to see the change take effect.
Note: when you force Windows to render the mouse cursor like this, some video games will have an invisible mouse pointer.
-
@kelpplankton said in f.lux beta discussion:
Is it possible to make the transitions between colors more smooth like in the previous version of flux, where you could set them to slowly occur over like an hour or two instead of being so jarring? I really liked that and miss it here, but I don't know if I just can't find the right settings options for it.
It was 60 minutes or 20 seconds before. Now we have 3 options: Slow, Medium and Fast.
- Open the f.lux menu
- Choose "Options (and Smart Lighting)..."
- Look for the drop-down menu under "How fast should transitions happen?"
If you're referring to a very smooth transition and not one that's bumpy and glitchy, well, Michael is working on it. All 3 speeds should be butter-smooth, but it seems to me that Medium and Fast are kinda choppy.
-
@kelpplankton the default now (4.19 - updating for you in the next day) should be slow always, but I missed an update case, and people who had v3 before were getting fast transitions instead. Meanwhile, you can change the speed in "Options".
-
Auto-update has never worked for me.
Installed the beta a few days ago, just noticed today a webpage "your f.lux build is updating" had opened with Change Notes for v4.19, but my running version is still v4.18.
I'm running Windows 10 x64 Fast Ring build (currently Version 1703 build 15063.14)
-
Why f.lux doesn´t automatically start in W10?
The icon is in the tray but doesn´t start and i have to do it manually and that almost kills my eyes... -
Transitions still need to be smoother, but I have a feeling you're fully aware of it and are working on it. For some reason, it's not consistent: sometimes transitions are butter-smooth and other times they can be kinda choppy. It seems the more often I make a transition happen, the choppier it becomes. I especially notice this for the feature of disabling for the current program. Going back and forth between the program f.lux is disabled for the first time or two is smooth, but then it gets worse and worse.
Setting my location no longer lets me be quite as precise as before (which was fun). In f.lux v3, I could type numbers after the decimal and it would change as I typed. Now it seems to only allow 1 decimal. I kinda miss the extra precision. It was fun.
I think it would be nice if I could prevent Darkroom Mode from being enabled by pressing Alt+Page Down all the way to the bottom, so to speak. It's not really a problem, but I guess it's just a preference because I'm not used to it.
I'd like a way to make the main single-slider adjust all 3 colors at the same time.
If I disable the wider slider range while I have any color selected that's outside the normal range of 1900K - 6500K, like let's say even 6550K or 1850K (so, even just 1 increment outside), that temperature remains selected until I touch the slider button. Of course, there's always 1 or 2 sliders on the 3-slider side of the UI that don't change when I move the main single-slider, depending on the current mode that f.lux is in.
I think the increments for changing the color with the keyboard shortcut should be changed to 50 or 100 so that going from 800K to 6500K is possible. Right now, it can only go up to 6300K or 6550K.
It might be nice to have an easier way to toggle between the single slider and the 3 sliders. It seems a little on the clunky side to have to go into the menu to go to the 3-sliders but then to just have convenient button to press to go back.
I think enabling Movie Mode should force Movie Mode on no matter what. Right now, it seems it will only work fully if I have a color temperature selected that's warmer than 4400K.
It might be nice to be able to choose how long it takes for the f.lux window to hide, similar to how we can choose how long an OSD menu stays up for in a monitor's options.
I think I would enjoy more precision for when the sunrise or sunset will be or was, meaning I think it should also include the minutes. For example, right now on my computer, it just says "Sunset: 4 hours ago". It was actually 4 hours and 3 minutes ago, so I think it would be nice if it said that. Or like when I noticed this, it was actually 3 hours and 53 minutes ago instead of 4 hours ago. I know that simplicity is better, but still. Maybe this could be an option. I'm also referring to what we see when hovering the mouse over the Notification Area icon.
-
@sitayi2308 said in f.lux beta discussion:
Why f.lux doesn´t automatically start in W10?
The icon is in the tray but doesn´t start and i have to do it manually and that almost kills my eyes...The only things I can think of is, you still have to set your location. Or you have to configure f.lux to your preferred color temperature and also your wake-up time.
So, the real problem is that f.lux is starting with Windows 10 for you, but it's not changing the color temperature at night. Is that right?
-
YES! thats exactly that problem! While the older version worked fine, since yesterday that i have to click in the icon and then it gets working...
-
@sitayi2308 said in f.lux beta discussion:
YES! thats exactly that problem! While the older version worked fine, since yesterday that i have to click in the icon and then it gets working...
When you say "the older version", do you mean f.lux v3, the one that we've had for a few years now? If so, then it would be best to uninstall f.lux, then verify that f.lux.exe is actually gone (using Task Manager), reboot, and then install the Beta fresh. You will have to reconfigure everything and reset your location, but this should make it work.
-
@TwoCables I just did that, erased everything about f.lux in the computer and fresh installed the beta versiorn, then rebooted and still the same problem. I must click in the icon to f.lux start working....
