f.lux f.lux forum
    • Recent
    • Popular
    • Register
    • Login

    MacOS Mojave Beta [fixed in beta 5]

    macOS
    10
    26
    8.2k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • herfH
      herf
      last edited by

      Are you on beta 3 or beta 2?
      If beta 3 is still broken please email support@justgetflux.com

      P 1 Reply Last reply Reply Quote 0
      • P
        pjb493 @herf
        last edited by

        @herf I've installed beta 3 today and come across this issue, so can confirm beta 3 is still broken

        1 Reply Last reply Reply Quote 0
        • C
          cassianoleal
          last edited by cassianoleal

          I've just found out that whenever I have iTerm2 open using the Metal renderer the artefacts go away.

          For the moment I'm starting iTerm at login to work around the issue but wanted to let the dev team know.

          For reference: https://gitlab.com/gnachman/iterm2/wikis/Metal-Renderer

          herfH 1 Reply Last reply Reply Quote 0
          • herfH
            herf @cassianoleal
            last edited by

            @cassianoleal maybe this means using the discrete GPU vs Intel one? Http://gfx.io can say which is running

            1 Reply Last reply Reply Quote 0
            • C
              cassianoleal
              last edited by

              @herf Yes, I suspected it might have to do with that.

              Using gxfCardStatus.app to switch between the GPUs I can reproduce the issue. When using the internal, I get artefacts. When using the discrete, the artefacts go away.

              1 Reply Last reply Reply Quote 0
              • M
                MojaveBook
                last edited by

                I've got a Macbook with newest Mojave beta (18A336e) and I also have this problem. Macbooks only have internal Intel GPU so this must be a iGPU problem. The question is is this because of the Mojave GPU driver or a bug in F.lux? Should we send bug reports to Apple instead or does the F.lux team need to rewrite parts of the F.lux rendering code?

                Anyway, this might be a tough bug to fix...

                1 Reply Last reply Reply Quote 0
                • B
                  beaugalbraith
                  last edited by beaugalbraith

                  Mojave beta 4 (18A336e). I experience the problem only when there are NO external monitors connected to my laptop and flux is set to Sunset or Bedtime mode. If I have an external monitor plugged in then those modes appears fine on my Macbook screen and the external monitors.

                  Hope that info is helpful in some way.
                  -Beau

                  MacBook Pro (15-inch, 2017)
                  Radeon Pro 560 4096 MB
                  Intel HD Graphics 630 1536 MB

                  A 1 Reply Last reply Reply Quote 0
                  • herfH
                    herf
                    last edited by

                    Is anyone using an older Mac (from 2015 or earlier) that has the problem?

                    1 Reply Last reply Reply Quote 0
                    • A
                      aimingforangels @beaugalbraith
                      last edited by

                      @beaugalbraith said in MacOS Mojave Beta:

                      Mojave beta 4 (18A336e). I experience the problem only when there are NO external monitors connected to my laptop and flux is set to Sunset or Bedtime mode. If I have an external monitor plugged in then those modes appears fine on my Macbook screen and the external monitors.

                      Hope that info is helpful in some way.
                      -Beau

                      MacBook Pro (15-inch, 2017)
                      Radeon Pro 560 4096 MB
                      Intel HD Graphics 630 1536 MB

                      Can confirm this is still an issue for me as well. I suspect that those with only the integrated Intel GPU's are going to have a long wait for a fix. Really a shame because as others have pointed out, Night Shift does indeed suck by comparison.

                      Macbook Pro w/ TouchBar (13-inch, 2017)
                      Intel Iris Plus 650

                      1 Reply Last reply Reply Quote 0
                      • N
                        nyoung1230
                        last edited by nyoung1230

                        I have the same ongoing issue as well. The problem goes away while connected to my LG Ultrafine 4K while my MacBook is closed. I have a 2017 13’ MacBook Pro with Intel Iris Plus 640 integrated GPU

                        1 Reply Last reply Reply Quote 0
                        • O
                          oryowen
                          last edited by

                          The current public beta build (18A347e) fixed the issue for me on my 13-inch 2017 MacBook Pro. So happy to have flux back!

                          C 1 Reply Last reply Reply Quote 0
                          • C
                            cassianoleal @oryowen
                            last edited by

                            Yup, all good on my side as well, using either GPU.

                            1 Reply Last reply Reply Quote 0
                            • A
                              aimingforangels
                              last edited by

                              Confirmed fix for me as well

                              1 Reply Last reply Reply Quote 0
                              • T
                                timwis
                                last edited by

                                I just bought a brand new macbook pro 2018 (8th edition, came out a few weeks ago) and once I enabled flux I got the blue neon text. Here's a photo of my screen since screenshots don't capture it. Where do I find the beta?

                                herfH A 2 Replies Last reply Reply Quote 0
                                • herfH
                                  herf @timwis
                                  last edited by

                                  @timwis is this Mojave or High Sierra? All we know so far is Mojave's public beta fixes it.

                                  A 1 Reply Last reply Reply Quote 0
                                  • A
                                    aimingforangels
                                    last edited by

                                    So this is odd, and may need to be posted elsewhere, but I have now switched to a brand new Macbook which does not have the Mojave beta and the same issues I had been experiencing before the latest Mojave patch, I am now experiencing in High Sierra.
                                    If I install the Mojave beta on this new Macbook, the issue is resolved but I was not planning on using a Beta OS on this device. Reverting back to High Sierra seems to bring back this same issue.

                                    Any ideas?

                                    1 Reply Last reply Reply Quote 0
                                    • A
                                      aimingforangels @timwis
                                      last edited by

                                      @timwis said in MacOS Mojave Beta [fixed in beta 5]:

                                      I just bought a brand new macbook pro 2018 (8th edition, came out a few weeks ago) and once I enabled flux I got the blue neon text. Here's a photo of my screen since screenshots don't capture it. Where do I find the beta?

                                      Same here.

                                      1 Reply Last reply Reply Quote 0
                                      • A
                                        aimingforangels @herf
                                        last edited by

                                        @herf any updates on this?

                                        1 Reply Last reply Reply Quote 0
                                        • herfH
                                          herf
                                          last edited by

                                          The High Sierra bug has been reported to Apple. Mojave has a fix already. There is a f.lux build posted with a temporary workaround.

                                          1 Reply Last reply Reply Quote 0
                                          • First post
                                            Last post
                                          Copyright © 2014 NodeBB Forums | Contributors