Auto Movie Mode is driving me crazy
I haven't changed any settings so all I can assume is f.lux has updated itself because this is the first time I have noticed this behaviour. I'm running version 4.55 and I have multiple monitors. I frequently watch youtube on one screen and continue with other activities on the other monitor. For ages this has worked fine, everything is nice and dim and red.
At the moment when youtube is fullscreened, f.lux disables and goes to movie mode, only on that monitor (but not if I turn on another effect such as vignette mode). I have turned software cursor on and if I take my cursor to the movie screen, movie mode turns off. If I mouse over certain links, movie mode turns off. I don't want it to be on at all unless I turn it on! I can see why auto movie mode on one screen only would be useful in some situations but I would like it to be optional and I don't think some of the behaviours I'm seeing are working as intended.
Hi there is no auto movie mode.
More likely: there is a fullscreen disable (so make sure you have that unchecked) and also a case where some fullscreen apps lose f.lux if you have not expanded color range and rebooted after installing.
Fullscreen disable sounds like what is happening (I guess thats kind of equivalent to some sort of "auto movie mode"), but I do not have that option checked. It does seem exactly like that kind of thing so maybe its happening for the second reason? I thought I had rebooted recently but I will do it again, as I do run f.lux with the expanded colour range and it might be that the update has installed after my most recent reboot. I'll update as to whether rebooting helps. Thanks for getting back to me with good and relevant info in a timely manner, I love the software and I love when good software is backed by good support.
Okay I'm back after a reboot and I'm seeing the same behaviour - athough right now, its pre-sundown and I'm finding if I mouse over the fullscreen video (watching youtube in chrome) I'm seeing vignette mode, dimmed orange colours, and mouse back on this second monitor and it goes back to blueish daytime colours. It is CLOSE to sundown so some orangeness should have kicked in.
Another point of note, I do have a usb samsung monitor plugged in too (a small one) and having seen to update those drivers on another thread, I tried that but it turned out I already have the latest version of drivers for that monitor. For interest's sake I've just unplugged that monitor and now I am not seeing these weird colour effects on my fullscreen video monitor. Plugged it back in, and I get blue/orange depending on which screen my mouse is on. This is happening on the monitor that is set to be my primary monitor.
So I think there is still some weirdness going on with the USB monitor. That monitor actually is displaying f.lux colours correctly as far as I can tell.
Another experiment - I'm going to drag my fullscreen video to different monitors to see if the effect follows the video or if it stays on the primary monitor.
OK when the video is on the USB monitor or the second monitor, I do not see the blue/orange colour change.
As a different experiment, I have changed my #2 monitor to be the primary monitor and put the video back on monitor 1, and now I am not seeing the issue either.
And as a final step I have made my #1 monitor be the primary monitor again, put the video back on that monitor as fullscreen, and now the blue/orange issue seems to have stopped happening.
Very interesting! I might reboot and see if the issue comes back from a fresh reboot.
Okay the issue DOES come back after a reboot. My primary #1 monitor, when given a fullscreen video, is blueish while the cursor is not on that screen, orangish while the cursor is on that screen. It doesn't do it straight away, takes about 5 seconds for it to start happening. Checking the timeline in f.lux, it does not look like it is close enough to sundown for orange night colours to kick in yet, the marker is not on the ramp down, but my other screens are definitely a little more orange than full day blue colour.
Removing USB monitor makes it stop, plugging back in makes it come back. I have the latest drivers installed.
This time I tested it a bit longer since it takes a few seconds for the effect to kick in, with USB monitor plugged in, setting the #2 monitor as the primary display DOES make the problem occur but now only on monitor #2.
So I will edit my previous post to reflect this updated information. (oops took too long, can't edit - just be aware that the problem seems to move and affect the primary display).
One last thing to check I suppose would be to make my USB monitor the primary display. Yes - this seems to also replicate the issue although its not as obvious as it is on my brighter IPS LED display. For now to minimise this issue I will leave the little USB monitor as my primary display.
Wonder if any of this helps work out what's going on?
The USB monitors have been a continual challenge - in this version we put in a workaround that emulates the effect on the GPU.
But the best option is to enable the DisplayLink/USB device to use f.lux color settings using instructions found here (the drivers have been updated to newer versions):
Hi, thanks for this info.
I followed the instructions and ended up with my USB displaylink monitor no longer displaying f.lux colours at all! I had some idea that maybe the displaylink beta drivers hadn't installed properly since the driver version was displaying as 8.0x not 8.2 so I uninstalled the drivers and then tried again. Next I kept getting a message to say the driver was already up to date (which I had earlier when I tried to install the drivers and at that time I believed it, but I think it might have been just not installing properly and telling me fibs). Tried uninstalling the displaylink core (which was from 2016 and saying it was version 6) in case this was disallowing the new driver installs, and then I had to restart, but I ended up having a windows update install at the same time as this reboot. As far as I can tell right now the USB monitor is running on Microsoft generic drivers and this seems to be working fine with f.lux so for right now I'm going to leave well enough alone. Looks like I'm on windows 1709 now so maybe this has changed something.
Thanks for helping me out!