DisplayLink has no support for color calibration, so f.lux can't make changes to DisplayLink monitors. Unfortunately, you can only use f.lux today on displays that are directly connected to your computer. (e.g., it usually won't work over remote desktop either.)
Yeah, I would love to be able to choose any color temperature regardless of what time it is. I don't have a consistent day/night sleep schedule either, and there are times where I will be going to bed right in the middle of the day. I first block all incoming light from outside, dim my room lights, dim my monitor all the way, and then I choose 2700K and then I dim f.lux so that it can go warmer than 2700K. Then I continue doing what it was I was doing on my computer for an hour or two and then go to bed.
Right now, f.lux is very limited because if I want anything warmer than 2700K, then I'm forced to choose either 2300K, 1900K, or 1200K.
By the way: the Lighting at Night menu has lower-case k's. They should be capitals.
So new update: Checked in at the Intel and Toshiba websites, apparently the driver is a custom manufacturer driver (which I should have picked up on when I saw that in the Intel Driver Update, need to stop doing this so late at night) and there is no new version of the driver available. All other drivers up to date as well.
Hi ghatokacha, thanks for your question. What's your goal? Our numbers say that if you want to use a higher kelvin value in f.lux, you'll need to dim your screen to keep the alerting light down. For keeping the screen's brightness higher, we use 2300K for a bedtime setting (f.lux's Mac defaults are 1900K before bed).
Yep those drivers can really **** stuff up.
Here's a nice story.
I installed a new CPU. Put my own well third party thermal paste on (you can NOT run any CPU without this.
I started up a game called Dirt 2. Well it ran fine for about 4 minutes of playing and would crash and that was very new.
So I thought "what could cause this--well what did I change: CPU".
So I took it out and reapplied thermal paste.
No change. I kept getting some strange error about "Graphics driver crash" but i'd just updated the video drivers after i'd installed this 775 socket quad core CPU I'd paid $125 for.
I kept reapplying thermal paste five or six times and eventually put too much and killed the CPU. It never did overheat.
I kept thinking it was something I had changed.
Put back in luckily still working dual core CPU and got the SAME ERROR.
Yeah that sucks so it wasn't the cpu. It was that damn buggy new driveri thought I wanted. And lots of people complained about crashing.
Itwas Nvidia famous 320. Something drivers. They were really bad.
Pay close attention to driver updates and don't rule them out. Sometimes they cause major issues that aren't your fault.
I since upgraded CPU + motherboard to support the new processor, to Intel Xeon 1230v3 that idles at 20 watts which is probably close to mobile CPUs. The old one used over 50 watts at idle.