giovs
14 discussion posts
Hello guys! I'm having a problem with DisplayFusion regarding Monitor Profiles.
I have two screens mirrored, but since one of them has a higher framerate I have the absolute need to change profiles on the go (the 60hz caps the fps of the 165hz when they're mirrored).
Thing is, I can't seem to ACTIVATE monitors via profile changing.
Whenever I'm going from the mirrored monitor profile to the single monitor it works fine. But when I change from the single monitor to the mirrored it always crashes.
Also, for some reason, when I run DisplayFusion as admin I have no such problem... Thing is, Windows won't auto-boot programs in admin mode. And having to run it manually every time I boot would be more of a hassle than to simply not use DF and just do this via windows cfg.
Manually doing the process (reactivating the display and mirroring it with the main one) works fine.
Debug log and screenshot are attached.
Thank you!
• Attachment [protected]: df error.png [34,388 bytes]
• Attachment [protected]: DisplayFusionDebugInfo.zip [61,508 bytes]
Jan 8, 2022 (modified Jan 8, 2022)
•
#1
That's really strange, does it work if you manually clone the monitors through the DisplayFusion Monitor Configuration window, without it running as administrator, rather than trying to switch through a monitor profile?
Thanks!
Has this only started happening since updating to v9.9?
Thanks!
Okay interesting, let me check in with our devs on this one to see what permissions are needed to make those monitor config changes.
Thanks!
Just an update here, you shouldn't need any admin privileges to set the monitor configuration. Are you running DisplayFusion as the same user account that the desktop is logged in as?
Thanks!
I've attached a link below to one of our older versions, v9.5.0. Could you try it out and re-save your profile, and let me know if the issue persists?
Thanks!
v9.5.0: https://www.binaryfortress.com/Data/Download/?DownloadID=468541db-df1d-4c92-9bde-4087c291f656&Log=0
Legotto
1 discussion post
I see that this didn't necessarily continue, but I wanted to let you guys know that I was having the same issue with the most recent version of Display Fusion. Downgrading to 9.5 fixed the issue entirely.