Sometimes (~40% of the time) when I change monitor configs, all screens will turn black and become unusable and require a hard shutdown to fix. I usually run a dual monitor setup but once in a while, I change profiles to run triple monitors to watch a video on my TV. That sometimes causes the 2 monitors to go black and the TV doesn't even register that it is connected.
I would attach my log but I just found out that logging is disabled by default (or maybe I disabled it by accident). Is this a known issue or is it just me? I know it's not common to switch between 2 and 3 monitors often.
I am running Windows 10 with a Nvidia 1060, using DisplayFusion Steam version 9.3. I did not notice this problem on previous versions.
When you upgraded to 9.3 did you re-save your monitor profiles? If not, give that a try so that DisplayFusion has the updated information. After this it will hopefully work fine.
When you upgraded to 9.3 did you re-save your monitor profiles? If not, give that a try so that DisplayFusion has the updated information. After this it will hopefully work fine.
I don't know why I didn't think of that. I did it just now. I'll see if it works. Thanks.
When you upgraded to 9.3 did you re-save your monitor profiles? If not, give that a try so that DisplayFusion has the updated information. After this it will hopefully work fine.
Never mind, it didn't work. I had to hard restart just now. I've attached my log.
Ok interesting, so even when the TV is powered off, it still shows as a disabled monitor in the Monitor Configuration window, and you can (usually) load the profile to enable it?
Ok interesting, so even when the TV is powered off, it still shows as a disabled monitor in the Monitor Configuration window, and you can (usually) load the profile to enable it?
Yes. I normally have the TV disabled and I enable it with a profile when I use it. Also, I do run into the same problem as in this thread (https://www.displayfusion.com/Discussions/View/switching-display-refresh-rate-with-profiles/?ID=2cd9747c-ba49-476c-84c0-a5b051b670ea) but fenix1's nircmd workaround does work so it's not too big of an issue. Just a bit janky. Interestingly, since using fenix1's workaround, I haven't run into the black screen but it hasn't been very long.
Ok, interesting! We have an idea on how to fix the issue from the other thread, so we're going to try that out for the next beta. We'll let you know when it's available to test, and maybe we'll get lucky and it will fix both issues
Just a quick heads up to let you know that this should be all fixed up in 9.6.2 Beta 1. Please let us know if you still run into any trouble after updating.
I have this issue. I don't know what triggers it, but I'm required to restart to make it go away. It can take any number of days before it starts happening.
I downloaded and installed the beta and that does not seem to fix the issue.
