@bionix-wallpaper we do have a feature that disables by app name, so when this function is on, we look for the current window, and try to find the owning process and get its name. This should be a no-op if disable by app is not used. If you want to find this crash, I would try to run f.lux with an app disabled and see what happens in your executable?

@herf Awesome. Thanks for the explanation. And I'm glad to hear there are new bells and whistles coming - looking forward to trying them out!

Our new beta (4.119) has a fix for rare X-rite profiles: https://forum.justgetflux.com/topic/6289/to-join-the-f-lux-beta

This is an issue with older Ryzen drivers that did not have support for color changes. You should look for a 2020-era driver. f.lux options > driver info can help debug this.

@herf Argh, I hope that isn't the case! Thanks for the response.

@herf Well, actually, I renamed it like that .... but this is a full-fledged profile created by a calibrator from Xrite .... if a professional calibrator does not "have any adjustments", I do not know with which one is "have" for flux works ... it works ok "without" "any adjustments" even with default windows night mode......

Hi Herf, thank you for explaining this! It sounds like for now the 'darkmode-ing' is still best done app-wise, imperfect as this is in Chrome and Office apps (and suboptimal as it is to have to switch to apps for which no dark mode exists altogether). It would be fantastic if at some point a more upstream, lower-level solution were available, perhaps once GPU makers, Windows devs and other devs have code that is more compatible with others.

@herf Alright, thanks, but I do remember it working using that same driver so that's pretty weird. Are there any plans to get it working on newer drivers? I miss my screen tint...

@NZZN_ Fixed, AMD's driver installer uses a cached version of the display driver (which in my case, f.lux had modified) if it has been installed before, deleting the cached driver made it download and install the correct driver.

I've been having this for quite some time, it's really annoying. Every time after the PC has been in sleep and I wake it, F.lux has shut down, and not every time is it working to start it up again. Driver info NVIDIA 27.21.14.6109: NVIDIA GeForce RTX 3070 (20201231) Generic PnP Monitor, 597 x 336mm, built 2020 Chromaticities: R=0.651367 0.327148 G=0.291992 0.596680 B=0.148438 0.059570 W=0.313477 0.329102 sRGB gamut: 98%, AdobeRGB gamut: 65% ASUS VG27A(DisplayPort), 597 x 336mm, built 2019 Chromaticities: R=0.658203 0.333008 G=0.299805 0.626953 B=0.148438 0.056641 W=0.312500 0.328125 sRGB gamut: 100%, AdobeRGB gamut: 72% Winlimit=0, 0 Monitor 1 on NVIDIA GeForce RTX 3070: VCGT=0 gamma=1 Monitor 2 on NVIDIA GeForce RTX 3070: VCGT=0 gamma=1 Windows Build: 19042.685