I have already posted about this dealbreaker issue 2 years ago, un-installed Flux when nobody seemed to come up with a fix, tried it again today, and find that even after over a year, the bug is still there. It's surprising because 2 years is quite a long time for deciding to ignore such a problematic issue.
I will explain again :
Any time Flux is in the process of transitioning from one Kelvin setting to another, the mouse movement becomes erratic, jumping around across the screen as you move it.
I don't know what to say, of course this renders the entire app un-usable.
This is happening on a MacBook Pro Retina 15'' i7 with Intel Iris Pro and NVIDIA GeForce GT 750M graphics, which I believe is a model that has been built in more than one unit across the world.
Is this ever going to be fixed, or otherwise can anyone recommend another app that does the same thing as Flux ?
Thank you ! :horse_racing_tone3:
lorna last edited by
@CapybaraGold What version of the Mac operating system are you using? And to double check, what version of f.lux?
Thanks for your reply Lorna,
My OS is Yosemite 10.10.1, Flux version is 39.987
Hope this helps :)
P.S. I understand this may be driver related, and not really Flux's fault. On the other hand, my OS is 10.10.1, I am very satisfied with it and not compromising stability and speed of my entire configuration just to have my screen yellower. This should still work, come on !
lorna last edited by
@CapybaraGold Unfortunately, this is definitely an issue in the older version of the Mac OS. There's not a fix we can give you, the issue is not on our end.
I can understand your worries about the update, though 10.10.5 fixed some major security issues in the Mac OS so it could be worth your time to update at least that far: https://www.macobserver.com/news/product-news/apple-patches-2-critical-security-flaws-os-x-yosemite-el-capitan/
Thanks for the information. It's great to be able to pin down the culprit at last, and to know the issue is not on your side. I'm sorry for implying it most likely was.
Do you know if 10.10.5 would indeed fix this Flux issue ? :astonished: