@efedezeta said in Feature request / improvemente request:

@TwoCables Yea you are right. It would be cool to simply disable

I think the reason why we can't just permanently disable it is, herf (Michael Herf, the main programmer/developer) worries that some people might disable it and then forget that they disabled it and then complain that it's possible to disable it and forget. I think he's right, especially with what I've seen on this forum.

So if anything, disabling it "permanently" should be something that's harder to do than disabling for an hour or until sunrise or for an application.

Update: Went back and checked each setting in nvidia control panel and the settings for each game. Didnt see anything out of the ordinary. I have been running f.lux beta without much trouble. As @TwoCables mentioned the setting called "disable for full screen apps" was disabled but I went ahead and enabled then disabled it. This might have done the trick but I did notice that when I launch mass effect or league of legends, flux will sometimes turn off (full screen and windowed borderless), I'll alt-tab and flux will turn back on, sometimes theres a few seconds delay but once I get back into game it will still be on. On rare occasion I'll have to alt-tab a couple of times.

Only issue I have is league of legends is still capped at 134fps. Not a big deal and I dont think this is a flux issue.

I think the problem is caused entirely by the Creator's Update, not the beta version of f.lux.

What I do is, I just delete the f.lux entry in the Registry that makes it start with Windows. This way, I simply launch f.lux when I want f.lux. I'd like to tell you where the key is, but I'm sure that's best kept to private messages.

I keep all 3 f.lux modes set to 800K so that I get 800K regardless of when I launch f.lux. I require a melatonin supplement (3mg) to sleep properly, and so this works perfectly.

So, when I know I will want to be sleeping in 2-3 hours, I lower my monitor's brightness all the way and then I launch f.lux (or I launch f.lux first, it doesn't matter). I also change all my indoor lighting to blue-free light (red and orange/amber). Then, about 10-15 minutes before going to bed, I take my melatonin and then I'm all set.

With the way I do it, I don't need a scheduler or anything like that.

So yeah, I bypass all of f.lux's automatic operations completely.

@lorna I've only noticed this one bug so far, except that vignette mode only seems to affect the primary monitor not my other monitors

@herf Thanks for taking the time to answer, it wasn't my intention to start a long debate!
I understand how finding a short sentence that is both informative and punchy can be hard work, especially in a complex subject such as this. Don't delay your cycle over it! ;)

Ok, 4.32, fixed issue with wondow apps, with disable fullscreen apps.

4.31 has this option now, "disable for full screen app" could you post when and what features this has, changelog says something about multi-monitor support.
I thought it might work for games with one monitor, but I am noticing weird issue.
I have my daytime use setting at 5800k, when I start any application, even small window utilities the value changes to like 6200 and then goes down back to 5800.

I have to test at night if games stay at right values and not go down to 3xxx night values.

thanks - am fixing this.

@herf

-------- again, fwiw, i went to task mgr. f.lux was disabled. i enabled it.

Yes - I think the fade timing is wrong, which would mostly fix this.
People don't close programs that much so we would probably avoid doing this exactly.

5,31 GB free disk space available.

this one:
https://justgetflux.com/flux-setup4-29.exe
https://justgetflux.com/news/pages/v4/readme/

try this one:
https://justgetflux.com/flux-setup4-29.exe
https://justgetflux.com/news/pages/v4/readme/

@Pegart I think our new schedule should work just fine for this - set your wake time and try the "working late" preset to get started.

I have not tried it but people say good things about QuickGamma:
https://quickgamma.de/indexen.html

I know we can detect "all" fullscreen apps (may be good enough), but I am not sure if we can detect all D3D fullscreen apps that might need the cursor.

Probably not another list of things to avoid though, needs to be automatic.

Will think about this.