Red Screen Artifacts When flux is on

odoketa

I'm getting the blue as well. It's an edge case - if you watch the artifacts when you change from nighttime to day, they will (dis)appear as it rotates the colors. The program isn't catching when there's an overflow situation, and so it goes from black to blue (white to red, I assume?). This is a pretty standard bug, should be easy enough to fix.

apreslin

So now based on everyone's responses, it seems like there indeed is a bug in f.lux. Does anyone know the best way to get visibility of the issue to the developers? I don't see a way to submit a bug report or issue within the f.lux application or the website, and have no idea if the developers read this forum with an open ear for bugs and issues. I emailed the support email, so we'll see if that does anything.

If this issue is affecting you, please upvote the original post to this thread, that seems to be what shows up on the main thread page for registered votes of the thread.

Hoping for a bug fix, had to stop using it due to this. Now using the Windows 10 night mode feature, but it really lacks customization options in comparison to f.lux

tinynrad

I just got the Surface pro 7 and have noticed the same weird things popping up on my screen when it’s set to the more orange setting.

Asdf_1234

This post is deleted!

apreslin

@apreslin said in Red Screen Artifacts When flux is on:

So now based on everyone's responses, it seems like there indeed is a bug in f.lux. Does anyone know the best way to get visibility of the issue to the developers? I don't see a way to submit a bug report or issue within the f.lux application or the website, and have no idea if the developers read this forum with an open ear for bugs and issues. I emailed the support email, so we'll see if that does anything.

If this issue is affecting you, please upvote the original post to this thread, that seems to be what shows up on the main thread page for registered votes of the thread.

Hoping for a bug fix, had to stop using it due to this. Now using the Windows 10 night mode feature, but it really lacks customization options in comparison to f.lux

No response from email after about a month, not sure how to contact the developer(s).

apreslin

Tweeted this out to the f.lux Twitter account https://twitter.com/apreslin/status/1220409689835474944

@apreslin said in Red Screen Artifacts When flux is on:

@apreslin said in Red Screen Artifacts When flux is on:

So now based on everyone's responses, it seems like there indeed is a bug in f.lux. Does anyone know the best way to get visibility of the issue to the developers? I don't see a way to submit a bug report or issue within the f.lux application or the website, and have no idea if the developers read this forum with an open ear for bugs and issues. I emailed the support email, so we'll see if that does anything.

If this issue is affecting you, please upvote the original post to this thread, that seems to be what shows up on the main thread page for registered votes of the thread.

Hoping for a bug fix, had to stop using it due to this. Now using the Windows 10 night mode feature, but it really lacks customization options in comparison to f.lux

No response from email after about a month, not sure how to contact the developer(s).

herf

Thank you for the posts - it looks like Intel has released a new driver for Iris Plus with a January 2020 date. Can anyone try it out?

We often see problems in "hybrid" setups when the discrete GPU (e.g., NVIDIA) version gets too far ahead of Intel's driver. Only a guess here, but I do know several things have been changing in Windows color to support HDR.

apreslin

@herf Thanks for the response. I made a 2 minute YouTube video https://www.youtube.com/watch?v=xq0usnYwz80 (listen with sound on of me describing the issue) which shows the problem. I don't have Iris Plus or any discrete GPU enabled, only a PCIE NVIDIA GeForce RTX 2060 with the latest drivers version 26.21.14.4187 dated 12/24/2019. That GPU has quad monitors connected to it, 3 of them on DisplayPort and one on HDMI. This also happened on a different video card in the same system, a NVIDIA GeForce GTX 1660, so it doesn't seem to be something like a defective video card. I also tried swapping out cables, and that didn't make a difference.

Any thoughts on what might be the issue with f.lux in that setup that's causing the cyan colored artifacts in video?

NVIDIA 26.21.14.4187: NVIDIA GeForce RTX 2060 (20191224)

Generic PnP Monitor, 598 x 336mm, built 2016
Chromaticities:
R=0.645508 0.336914
G=0.328125 0.615234
B=0.146484 0.055664
W=0.313477 0.329102
sRGB gamut: 85%, AdobeRGB gamut: 60%

Monitor 1 on NVIDIA GeForce RTX 2060: VCGT=0 gamma=1
Monitor 2 on NVIDIA GeForce RTX 2060: VCGT=0 gamma=1
Monitor 3 on NVIDIA GeForce RTX 2060: VCGT=0 gamma=1
Monitor 4 on NVIDIA GeForce RTX 2060: VCGT=0 gamma=1

Windows Build: 19033.1

herf

@apreslin so this is the insider build? Nice setup :)

I saw artifacts on the top two monitors but not on the bottom two - are you seeing on all?

Also, do they go away if you unplug HDMI and only use DisplayPort?

apreslin

@herf It is an insider build, but I'm pretty sure this issue was happening before I changed over to an insider build. Yeah, go big with quad 27" monitors or go home :)

The artifacts only occur on 2 of the 4 monitors for some reason.

I just tested with different combinations. With only 3 monitors connected, I can't reproduce the artifacts at all.

Tried all 3 on DisplayPort with no artifacts.
Tried 2 on DisplayPort, 1 on HDMI, no artifacts.
Connected all 4 back up, artifacts appear when f.lux is started.

So the only way I seem to have the issue is when it's connected to all 4 at once. The other interesting thing about the issue is that is always affects 2 of the 4 monitors, but not always the same 2. Also, it's not always the HDMI connected monitor being one of the two monitors that have the artifacts.

Armenian Bot

I've been having the exact same issue since I got my laptop late last year. My presumption was that it had something to do with the HDR nature of my display? But that could definitely be wrong from what I am reading here. Let me know if that lines up with anyone else.

markotny97

Same here, MSI GS65 with GTX 1660Ti. Blue artifacts only on external display. For me it seems to happen only if I have one external monitor, if I connect second (different model) I can't reproduce the issue. Happens on both monitors (if only one connected). Neither has HDR so that's not the issue, at least not in this case.

fernandezcojones

Same problem here - two displays connected to GTX 1080Ti, weird artifacts (like in this post: https://forum.justgetflux.com/post/22665) on one screen. If a third screen is connected, the artifacts show on one screen only, but not the same as with two displays connected. No HDR displays.

All of this is instantly remedied by toggling Night Light on and off and then it doesn't appear until a restart.

apreslin

@herf Would you be able to take another look at this thread now that more people are reporting that they are experiencing this bug? Also tweeted at https://twitter.com/apreslin/status/1220409689835474944 at @JustGetFlux

herf

@apreslin Most of these issues (in Insider builds) should be reported to Microsoft also. Usually they are some combination of driver bugs and bugs internal to Windows. It does help if you post "driver info" here so we have a record of when things broke.

Mostly we just forward them on, because they are bugs in the color system. Can you report them through "Feedback hub" from Windows?

fernandezcojones

Reported the bug to MS through Feedback Hub as advised. Available here: https://aka.ms/AA88icf

jcrens8392

Hey I just encountered this issue after calibrating my monitor w a custom profile using i1profiler from X-rite. I'm getting bright red lines showing at any K setting below 5000K. 5000K and above, and there are no red lines. Also, if I switch back to any other ICC profile, I don't get the red lines. This just started happening today after applying this new custom icc profile. Here's a link to the icc profile in case it helps: https://www.dropbox.com/s/zbj9b3zj4bvh88o/LG HDR WQHD_04-05-2020.icc?dl=0

simonr

Red artifacts for me, with the latest Intel driver from April (Surface Laptop 3).
Tried toggling both "use display data for better color" and "use GPU" options, with no effect.

Intel Corporation 27.20.100.8187: Intel(R) Iris(R) Plus Graphics (20200417)

Surface Panel Filter, 285 x 190mm, built 2019
Chromaticities: 
  R=0.639648 0.329102
  G=0.299805 0.599609
  B=0.149414 0.059570
  W=0.312500 0.328125
  sRGB gamut: 99%, AdobeRGB gamut: 64%

Monitor 1 on Intel(R) Iris(R) Plus Graphics: VCGT=0 gamma=1

Windows Build: 18363.778

Interestingly, this problem does not exist on my Surface Book 2:

Intel Corporation 25.20.100.6472: Intel(R) UHD Graphics 620 (20181225)
NVIDIA 26.21.14.3086: NVIDIA GeForce GTX 1050 (20190522)

Surface Display, 750 x 500mm, built 2016
Chromaticities: 
  R=0.639648 0.330078
  G=0.299805 0.599609
  B=0.150391 0.059570
  W=0.312500 0.329102
  sRGB gamut: 100%, AdobeRGB gamut: 64%

Monitor 1 on Intel(R) UHD Graphics 620: VCGT=0 gamma=1

Windows Build: 18363.778

simonr

For me, the artifacts only appear at temps 3250K and below. At 3300K and above, everything is fine.

lamchcl

I'm getting the blue artifacts as well on two different computers with dual-monitor setups. Unsure if it matters, but the artifacts only occur on the monitor on the right side. On one computer, it occurs on the primary monitor, and on another computer, it appears on the secondary monitor. It seems to occur on normal mode (without any effects) if and only if the red value of the pixel is 129, and it looks like the red value becomes 0, or maybe 1 or some other small value (it's hard to measure because obviously the computer thinks it's 129).

Interestingly enough, the artifacts do disappear after a while (maybe after sleeping and waking? will need to do some more experimentation) but they consistently come back after a restart.

Hope this information helps to get this bug fixed ASAP, it's been an annoyance for a while and I didn't realize that f.lux was causing it until now.