brettreichart78045
7 discussion posts
If any monitor/TV is off, then any key combination assigned with them in it will not work. It's almost as though the videocard doesn't broadcast to my devices when they either sleep or are off, so displayfusion is unable to work. Everything was fine for years when I had a 1080p 144jz monitor and the tv was set to 1080p 60, but I got a new videocard and primary monitor. Now my monitor is 1440p 165hz and the tv is set to 4k 120hz.
Talked about it a bit here, but it's better to get it's own : https://www.displayfusion.com/Discussions/View/error-failed-to-call-setdisplayconfig-hr-87/?ID=ac310c84-3dde-4c97-a34b-5f0123206053
Sep 29, 2022 (modified Sep 29, 2022)
•
#1
brettreichart78045
7 discussion posts
I have uploaded the three files. I didn't include the TV since I'm having issues with both tv/monitor, but figured we would troubleshoot one device at a time. I hope this helps.
"On" is all 3 of my monitors on and set in Display Fusion.
"Off" is them physically off, and not set to display in Display Fusion. I can leave all three set and just physically turn it off if need be.
• Attachment [protected]: DisplayFusionDebugInfo.zip [30,093 bytes]
• Attachment [protected]: Off.txt [131,354 bytes]
• Attachment [protected]: On.txt [139,209 bytes]
brettreichart78045
7 discussion posts
I just tested another video card and all the same issues occur.
I also tested that if I enable my TV (one of the devices I'm having issues with) at 60 hz, it turns enables just fine (TV is still physically off), but as soon as I try switching it to 120 hz, it screws up my whole profile.
I attached a before (before.png) profile of all 4 devices working (TV at 60) and what occurs after (after.png) I select 120 hz on the TV.
As soon as I walk and physically turn the TV on, then I'm able to set 120 hz and it works just fine. Apparentlly this isn't an issue with DisplayFusion since it reacts the same way in the Windows 10 Display Settings, but hopefully someone knows more than me.
• Attachment [protected]: After.png [48,289 bytes]
• Attachment [protected]: Before.png [135,563 bytes]
Oct 3, 2022 (modified Oct 3, 2022)
•
#4