dooniem
8 discussion posts
An error has occurred while applying your new Monitor configuration.
Please check your settings and try again.
Error: Failed to call SetDisplayConfig. [HR: 31]
[System.Exception]
Hi. This worked well for a week, then I got this error on profile change.
Now I can't set splits manually through the monitor settings or through saved profiles.
I was running 9.7 when this error occured, updated to beta 10 and got same error.
attached debug info.
• Attachment [protected]: DisplayFusionDebugInfo.zip [35,749 bytes]
dooniem
8 discussion posts
I was able to get passed the error by configuring my profile/splits from scratch and overwrite the saved profiles. So it's working at the moment, but maybe you'll find something in my debug info?
dooniem
8 discussion posts
Hi, just got the same error message again.
I had the beta 10 when I got the error, I updated to the newest 9.7.1, no change.
It will probably work again if I set up the monitor profiles a third time, but maybe something's off here?
• Attachment [protected]: DisplayFusionDebugInfo.zip [30,437 bytes]
Ok, strange! Does anything specific seem to make it stop working? (system reboot, driver update, etc?)
Ah, yep, that would probably do it! Unfortunately there isn't a way to save a profile that works with both ports, but you could have two profiles saved, then just load whichever one you need.
dooniem
8 discussion posts
Not sure if it's allright to expand this thread further. Let me know if I should start a new one.
Since I have 3 profiles allready hotkeyed, I would need 3 new hotkeys, unless I change the hotkeys to run functions instead.
I browsed and seached through your help page about script functions, but couldn't find anything about error trapping. Could you lend me a hand on how to structure an IF sentence that checks if the profile change returned an error, THEN apply the correct "rescue profile"?
Or would it be easier to identify both ports, then check which port is active and activate the relevant profile?
I'm pretty OK with Visual Basic, so writing in VB would be preferable.
Jan 1, 2021 (modified Jan 1, 2021)
•
#8
I don't believe there actually is a way to trap the error, the script just blindly calls the function to load a profile. I will see if there's a way we could add some error handling in there.
There actually might be a way to do this actually. Can you send me the names of the two monitor profiles? (the main profile and the backup profile that was created for the other port?)
dooniem
8 discussion posts
I overwrote all the existing profiles when updating from 9.7.1(?) to beta 10. I have named my profiles 0 - 3. So If you compare ie. the one named "3" in my first diagnostic upload with my latest?
Those 3 profiles only work on one of the ports though, right? Do you have another 3 profiles that were saved while the dock was connected to the other port?
dooniem
8 discussion posts
What I was trying to say in my last post was:
I believe the upload in this thread's first post contains "port 1". While the second upload in this thread contains the same profile names, but configured on "port 2". I'm writing this out of office from mobile, so maybe what I allready have uploaded has the data you need?
But maybe it falls short since created in the previous version, but log was extracted from beta 10?
Jan 12, 2021 (modified Jan 12, 2021)
•
#13