Windows 10 May update (1903)
@highwayrob We think the "fast startup" bug is fixed now (this is Windows update, not drivers). If you are having trouble, please post f.lux options > driver info in this thread (using the latest build of f.lux).
thanks for the speedy reply, here's requested info
I think ill leave fast startup turned off anyways, as i leave pc running for a week preferably.( i realize windows caused the issue, but if a workaround cannot be found from flux, i mean then windows wont ever fix their bugs- rarely)
Advanced Micro Devices, Inc. 26.20.13001.25001: Radeon RX 580 Series (20190730)
Generic PnP Monitor, 820 x 460mm, built 2010
sRGB gamut: 100%, AdobeRGB gamut: 96%
Windows Build: 18362
@highwayrob got it - okay we do know that the Radeons are giving problems, and the 19.x driver series is the issue. For some people, downgrading to 18.x is working better.
@herf hmm, worth a shot, ill look into that this weekend. ty for the suggestion!
Dont see my RX 580 there, only "vega" series, and their tool only seems to want to install newest drivers. i cant roll back as these are the drivers the pc came with, so nothing to roll back to (pc is only a few weeks old).I sifted through their drivers and found nothing allowing specific version, or confirming that mine was version 19. (as hardware advises version 26.20.13001.25001)
do you know where i could get the suggested drivers? or do you have any other suggestions?
note: when i came home form work the monitor was still in candle light ( i turn off my tv/monitor and dont have an screen saver), but when i moved my mouse full colour came back although f.lux setting said it was still set to candle light. will require a reboot to work again.
@highwayrob Sorry but your reply didnt make sense. I am not on version 20, i am version 26, there is not ability to downgrade to ver 18 as no version 18 is available for download.
DO you think you guys will fix this issue for Radeons or am I stuck rebooting every day or do i move to lightbulb, iris mini, redshift, sunset screen, shady, night tone, lumen, brilliance, iris, or one of the alternatives? shame windows stopped support for win 7 else i'd still be running that, as i had no issues with f.lux then.
@highwayrob sorry we don't yet have the hardware here to test. We have confirmation that the 2018-era drivers do work, but it's possible that some of the 2019 ones do too.
Here is a list of "previous" drivers - are you able to try a couple and see?
@herf Thanks for the link, i dont know why i couldnt find these before. I installed the newest one at the top of that list. Rebooted my pc and worked (as reboot always fixes the issue) but i noticed my streamlabs wasn't working properly and i'd get black flashes where my game capture is supposed to go, they suggested, updating to the newest drivers. So I rolled back (forward in my case) drivers to what it previously had via my system restore ( as I dont know/coudlnt find the original drivers).
I don't particularly want to try each driver individually due to the amount of time, and the number of other programs that could go awry as streamlabs did). I think I'll hope you guys get the newest cards/drivers working - any idea on ETA for something like that? - i know you guys are prob busy with a thousand other drivers/bugs that are constantly rolling out/affecting the software as new updates for other 3rd party are created)
@href @highwayrob Some good news for Radeon Vega owners, the issue seems to be fixed, at least for me, in the newest drivers "Adrenalin 2019 Edition 19.9.1" (release date 2019/09/10).
Details, per Flux:
Advanced Micro Devices, Inc. 26.20.13001.50005: AMD Radeon(TM) Vega 8 Graphics (20190903)
Windows Build: 18362
@xafeb23 thank you -adding to FAQ
This post is deleted!
Still having this problem - is there anywhere a solution? Just found this thread here.
I don´t have DisplayLink, only HDMI...
Including images here doesn´t seem to work :(
@A-Former-User said in Windows 10 May update (1903):
As a followup, the following made my DisplayLink external monitor work with f.lux again:
(1) Upgrade the DisplayLink drivers to the latest stable.
I figured it would be a good feedback to back up that post, and also to update the links.
So if you have TINTED SCREENSHOTS with DISPLAYLINK adapters (like my Dell D6000) using ShareX or other snipping tool... try the following steps to resolve the issue:
(1) Upgrade you DisplayLink adapter to the latest version (10.1.2875.0 as of today): https://www.synaptics.com/products/displaylink-graphics/downloads/windows
(2) Enable nigh light with registry setting: https://support.displaylink.com/knowledgebase/articles/1886413-how-to-enable-night-light-or-f-lux-on-displaylink
For point (2), there is actually an alternative that doesn't require messing up with the registry by enabling Night Light using the UI of the DisplayLink Manager: https://www.microsoft.com/en-us/p/displaylink-manager/9n09f8v8fs02
My drive info's:
DisplayLink 10.1.2875.0: DisplayLink USB Device (20210811) Intel Corporation 22.214.171.12426: Intel(R) UHD Graphics 620 (20201223) DisplayLink 10.1.2875.0: DisplayLink USB Device (20210811) Generic PnP Monitor, 344 x 194mm, built 2019 Chromaticities: R=0.584961 0.363281 G=0.349609 0.567383 B=0.162109 0.123047 W=0.312500 0.328125 sRGB gamut: 61%, AdobeRGB gamut: 39% Generic PnP Monitor, 708 x 399mm, built 2019 Chromaticities: R=0.678711 0.313477 G=0.200195 0.721680 B=0.151367 0.045898 W=0.298828 0.317383 sRGB gamut: 102%, AdobeRGB gamut: 100% Unlimited gamma ramp=1, Internal ramp=0 Monitor 1 on Intel(R) UHD Graphics 620 Has VCGT profile=0, Gamma Ramp works=1 Monitor 2 on DisplayLink USB Device Has VCGT profile=0, Gamma Ramp works=1 Windows Build: 19042.1237
Thanks for the forum that helped me resolve my issue.
The dimming functionnality is still not working.