Build 37.7 for El Capitan
-
@herf thanks . So I don't need to update, but if I do there are some small fixes that would work/help EVEN on older OS X versions as well?
-
Hello, I updated to 37.5 today. Did anything get added that checks the color profile every once in a while? I'm having an issue with my video card drivers where every time the color profile is changed my cursor jumps a little. It's not so much of a problem with flux since I can just enable fast transitions. But if I don't my cursor will be jumping around the screen like crazy during a transition. But I noticed that after this update my mouse jumps a little every 10 minutes or so. Is this correct or could it be caused by another application?
-
@Jespertheend Yes that would be the new build. Which GPU and Mac are you using?
Previously: El Capitan's automatic brightness has been restoring old f.lux profiles and not letting us know, so we made this build to try to actually make the screen come back to daytime mode. We can do a little bit less though.
-
@herf I'm using a nvidia gtx 980 ti on a hackintosh. So it's a bit of a special case. But I remember having the same issue on my old iMac as well. An option to disable the checks would be nice, but I understand that you don't want to clutter the UI. Is it possible to check if the system has the wrong color profile and only change it when it actually does have the wrong profile?
-
@Jespertheend actually this is what we have always done. The bug that has been breaking us on El Capitan is when the OS reports that nothing has changed, but it actually has. Will make an option to do a little less.
-
@herf ah I see, thank you that would be nice. It's not impossible to work with but every once in a while your cursor just ends up where you didn't intend to put it.
-
@Jespertheend Ok I pushed a build that makes the behavior slower and adds a pref to disable it.
https://justgetflux.com/mac/Flux37.6.zip
And then if you want to disable the time-based behavior:
defaults write org.herf.Flux flushSeconds 0
-
@herf ah, I hadn't thought about that. This way the UI is still clean, nice!
Thank you very much :) -
@herf hmm it seems like I'm still having the issue. But I believe it only happens after 5pm or so.
-
F.lux 37.5 and 37.6 ignore the "Disable for" any of my apps; though it sometimes works on the initial start of the app, but as soon as I switch to another app and back it stops working. Even the "Disable for an hour" doesn't work anymore. In both cases a notification is displayed, saying that it's deactivated, unfortunately it's not. Reinstalling F.lux, restarting of Mac didn't help. Furthermore, the change between active and disabled state of these versions is abrupt. Previous versions had a smooth transition in both directions, activating and inactivating F.lux, now its instantaneous.
System information:
iMac 20" Mid 2007, Mac OS "El Capitan" 10.11.6, ATI Radeon HD 2400 XT 128 MB -
Hey everyone - we posted this build which fixes the disable bug - let us know if it helps?
https://justgetflux.com/mac/Flux37.7.zip
Michael
-
@herf Seems to be working fine. Thanks a lot.
-
@herf just found this forum after having all sorts of issues in 37.2 / osx 10.11.6. (flux enabled after quitting app; turning night mode on and off randomly, etc.)
Only been using the 37.7 patch for about 10 minutes but night mode has turned on then back off once already.
Love the app even with the current problems, just wanted to provide more feedback.
-
@herf Hey, I'm running 37.7 on macOS Sierra with auto brightness adjustment still enabled, and I'm still seeing the weird behavior where when brightness adjustment is triggered, the flux color profile kicks in even when it's daytime..
-
@malorkus which machine is it?
-
@herf 13" retina Macbook Pro (early 2013).
-
Hey I have a Macbook pro 13 inch (16 gb ram, i7) and there is an issue with the lighter colors namely when watching youtube videos.
If I move the mouse to make the screen react, the colors will go back to the right tones, however when the time marking and stuff goes away the color goes stupid, for clear tones.
My software is up to date
All of that bluea is poorly rendered white.
https://goo.gl/photos/myLZk2RWV7Y1jQMw7 -
Here's a new thread for this topic:
https://forum.justgetflux.com/topic/3040/fullscreen-video-artifacts -
I'm having this issue still. El Capitan, 37.7, automatic brightness enabled. It keeps flipping back to a late evening one all morning, even after I quit flux.
It didn't seem to have made a flux color profile, just standard LCD.
https://www.dropbox.com/s/nfrsc2asli2fphj/Screenshot 2016-10-09 09.56.20.png?dl=0 for my system details.
I think another contributing factor is I always have the monitor not on full brightness, normally just a couple up from the bottom. 4 blocks up from the bottom.
-
Had a crash this morning. Machine was up, I could SSH to it, but the screen was dark and flickering. Rebooted and checked the system.log. This may be a GPU failure issue, but I figured I would throw this in for those with similar errors and a LOT of Flux messages, but the more I dug the more it seemed like the issue was my GPU and not Flux.
Oct 25 08:04:05 max kernel[0]: IOVendorGLContext::ReportGPURestart Oct 25 11:49:04 max watchdogd[402]: [watchdog_daemon] @(_wd_daemon_service_thread) - service (com.apple.WindowServer) reported as unresponsive Oct 25 11:49:05 max watchdogd[402]: [watchdog_daemon] @(__wd_service_report_unresponsive_block_invoke) - failed to gather a spindump for (com.apple.WindowServer) Oct 25 11:05:10 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:05:35 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:21 --- last message repeated 1 time --- Oct 25 11:06:21 max kernel[0]: NVDA(OpenGL): Channel timeout! Oct 25 11:06:41 max kernel[0]: NVDA(OpenGL): Channel timeout! [... above repeated several times, then ... ] Oct 25 11:49:05 max Dock[360]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Google Chrome[333]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0xfffffecc: (ipc/mig) server died Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max GPGSuite_Updater[1355]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max CalNCService[383]: Set a breakpoint at CGSLogError to catch errors as they are logged. Oct 25 11:49:05 max Upwork[341]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination port Oct 25 11:49:05 max SystemUIServer[362]: HIToolbox: received notification of WindowServer event port death. [... later, Flux repeating every few seconds ...] Oct 25 11:51:04 max Flux[951]: Empty gamma size Oct 25 11:51:04 max Flux[951]: void CGSGetDisplaySystemState(uint64_t, CGSDisplaySystemState **): MIG error 0x10000003: (ipc/send) invalid destination portEarly 2008 Mac Pro, 18GB RAM
OS X 10.11.6
NVIDIA GeForce 8800 GT 512 MB
F.lux 37.7I've now updated my NVIDIA card with their drivers, maybe it is a GPU issue and not a Flux issue. Wait and see FTW!
