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

    No color changes under Windows Insider 19H1

    Windows v4
    12
    52
    13.5k
    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 @rseiler
      last edited by

      @rseiler thanks again - have updated for these versions also.

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

        Build 18343 not working with f.lux. My eyes are on fire 🔥_🔥

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

          @charsy89 Can you use our beta?
          https://forum.justgetflux.com/topic/6289/to-join-the-f-lux-beta

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

            Works perfectly. Thx!
            I hope Microsoft fixes this soon D:

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

              Third message about the brightness still not working and still no answer (little up this thread and here) ....

              Do you plan to fix it ? (details in the link below)

              Regards

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

                @clem0338 we are still in "workaround" mode since the color controls are not working. Hopefully some fixes soon.

                R 1 Reply Last reply Reply Quote 0
                • R
                  rseiler @herf
                  last edited by

                  @herf Soon, but not with today's 18845 and (likely) yesterday's 18346.

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

                    @rseiler okay I put 18845 under our compatibility just now.

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

                      Thankfully I found this thread - my F.lux wasn't working with build 18342 and my eyes were burning out staring at my BLUE screen after dark! I just manually closed F.lux and reopened it and it turned on (PHEW)! So glad to have it back. Hope it's fixed in a new build soon.

                      -Gina

                      Intel Corporation 26.20.100.6572: Intel(R) HD Graphics 630 (20190129)

                      Generic PnP Monitor, 16 x 9mm, built 2016
                      Chromaticities:
                      R=0.636719 0.330078
                      G=0.272461 0.592773
                      B=0.143555 0.066406
                      W=0.276367 0.278320

                      sRGB gamut: 91%, AdobeRGB gamut: 64%

                      Windows Build: 18342

                      1 Reply Last reply Reply Quote 0
                      • R
                        rseiler
                        last edited by

                        Does it make any sense that the workaround mode could possibly cause some black video blotching/tearing in some apps some of the time (Outlook seems to be the main one seeing this)? The black "blocks" randomly flash in a portion of the window and then disappear.

                        It took me forever to realize that f.lux was doing it, since it's not a constant thing at all, though only since the workaround has been needed.

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

                          Well I am not aware that blacks should be affected by it.

                          I know about some flashing like this in 1803/1809, due to the way the profiles are loaded/reset from Windows. Generally the bug we are working around in the shipping versions is that the system treats any device change (like a bluetooth headset or USB insert) as a "reset" to the color system, and so we have to race around trying to fix it. I don't know what is going on in this new version yet, but I am watching - guess we have another potential release later today.

                          R 1 Reply Last reply Reply Quote 0
                          • R
                            rseiler @herf
                            last edited by

                            @herf That's right, 18348 is out.

                            Just to explain it a little better in case it matters, it's not that blacks are affected exactly, but black artifacts appear randomly over non-black areas. In this sense, you might say that it's whites being affected, or at least anything not black.

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

                              @rseiler Downloading, will see what's going on in a couple hours...

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

                                @rseiler pushed another compatibility update.

                                1 Reply Last reply Reply Quote 0
                                • R
                                  rseiler
                                  last edited by

                                  The problem MAY be fixed.

                                  I hadn't noticed that 18348 (Mar 1) had this in the release notes:

                                  "If you use third party apps to adjust the color of your screen, we’ve made a fix with this build to address feedback that certain apps were no longer working. We’re continuing to investigate feedback in this space."

                                  And today's 18850 has the same note.

                                  Did you find 18348 still needed the workaround? I'm about to try 18850, so I don't know about it yet, but it should be in the same boat as 18348/18351.

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

                                    Updating our test machine now! 18348 did not work but I am hoping for a fix in the '50s somewhere. :)

                                    1 Reply Last reply Reply Quote 0
                                    • R
                                      rseiler
                                      last edited by

                                      18850 doesn't work, either, so maybe they're working their way through third party apps (I'm not aware of any others, though they must exist).

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

                                        18851 is working. Looking at what is new there.

                                        1 Reply Last reply Reply Quote 0
                                        • R
                                          rseiler
                                          last edited by

                                          That's surprising, since the release notes for 18351 didn't mention anything about this other than the usual note that they're still looking at issues.

                                          But based on that trajectory (the build after when they said they fixed it actually does), I'd expect next week's 20H1 (post 18850) build to also have the fix.

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

                                            Pushed 4.97 beta with full compatibility under 18351. Looks like everything is working a lot better now.

                                            The main (release) build will work also, but this one should be more efficient.

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