@GODzilla I mean just for performance reasons we leave the hardware one on during the "day" or when you won't notice the change, so a manual way would be a lot worse. But people can't be losing a cursor during a game, so we should fix that soon.

Yeah we are slowly rolling v3 to v4 - it is a big update and we want to get all the details right for people who are very used to the way it has been. So only some v3 people have gotten the new version.

Also just mentioning: the v3 "gaming mode" which disabled all polling but had tons of bugs got taken out of v4, because the new version does it all the time. We are not polling at the GPU level, and instead use some tricks to know when it is a good time to "fix" the screen.

@herf That did it! I had seen that post before when I was looking around for a solution but it never occurred to me to try that out since my ghosting was of a different color. Thanks for the help!

@TwoCables said in Color effects/Reduce Eyestrain:

F.lux v4 has a range of 800K to 100,000K. Use Alt+Shit+Page Down and Up.

Whoa, I knew about the shortcut, and going down more orange, but hadn't considered how blue I could go! Thanks for that, I'm now at 50,000K very nice tint.

@f-lux-team Bug or limitation, I have two GPUs (one low power and another higher speed) with each a monitor connected. When I use the shortcut, it doesn't seem to be affecting the other GPU or the other monitor, however you'd like to think about it. Is this a difficult configuration to work with? I understand the program changes the color tables for A GPU, but what about more than one?

I'm completely mistaken, it is pushed to both monitors, whoops. The blue is just not very pronounced as I thought it would be, maybe I'll kick up the saturation.

Yes I mean we are making changes the monitor can "see" so in that sense it is due to f.lux - it is just not a bug we made. :)

I am working on a change that might make the timing a little bit longer.

The goal in these newer versions is to replicate the natural sunset timing a bit better. Not just the "moment" of sunset but the actual timing. But there are still a lot of ways to do that!

@Marko-Krištof said in movie mode shortcut, button or place on the icon menu:

@TwoCables true, it is not an extra click, but that takes even longer

Yeah, and it's also annoying when falling off the menu and having to start over. (I admit that it's hard to fall off this menu though, but still, it can happen)

@jwsl1200mk2 you could try procmon too - it is not that hard to do... :)

I was not using alt+pgdn, however they have been fixed all the same. Thanks!

It seems to be a problem with dell premier color software... if I uninstall that the problem goes away. unfortunately I need that software to make my screen not look over saturated during the day... any ideas?

Thanks
JB

You can try opening Windows Magnifier and set it to 100%.

Or you can make a change to the Registry, but let me know what you think of using the Windows Magnifier first.

I have the exact same issue running v4.43, Win7 64bit and nVidia Quadro 410 on 21.21.13.7684 drivers.

The computer is locked overnight at work, and the night (or transition, unsure) color sticks when I come in next morning, long after my "earliest wake" time. If I close and start Flux again, the color temperature will properly be set to its day value.

Looks like AM is "?W??", and PM is "?U??".
Also it is always show :30 at the end whatever the time is.

I've installed the latest version from the link provided above and can confirm that f.lux no longer continually asks for the location every time it starts up! Thank you for this.

I have however noticed that in the main flux window, when I click the lower-right link saying "Location: 5#.#°N, 0.0°E (Click to set)" the "Where am I" window which pops up still shows the "default" location and the search box is empty (instead of the location I've entered before). I'm pretty certain however that it's actually using my correct location and this is just an presentation issue --- possibly the longitude check occurs here as well?

@jshap confirmed. Works for me now. Thanks all.