Closed FormelLMS closed 2 years ago
Ah, I understand now. Looking at the error provided it's in the new TaskBar so it's a different little bug to squash. I've just squashed the bug, so can you please run the exact same tests using this NVIDIAInfo v1.5.1?
Thanks Terry
Also @FormelLMS @sk666,
After you have both completed testing NVIDIAInfo v1.5.1 using the instructions above, can you please both try this new version of DisplayMagician I put together as well.
This new test version of DisplayMagician v2.2.0.112 has a lot of new functionality:
Please test it out, and tell me if there are any bugs. NOTE: There are quite a few changes in v2.2.0.112 compared to v2.1.5.5, so you will be asked to recreate new display profiles again. Please make sure you do this so that everything will work ok. DisplayMagicianSetup-v2.2.0.112.zip
Thanks Terry
So we now are steps ahead :)
Tests with NvidiaInfo 1.5.1: After Applying the regular.cfg I got those error Message:
Attempting to apply NVIDIA display config from regular.cfg ERROR - NVIDIAInfo Windows CCD settings were not applied correctly.
Equality checks then of surround and regular.cfg are NOT equal after that Taskbar was on the left monitor instead of the middle
After changing back to surround profile, the surround.cfg was equal NvidiaInfo 1.5.1 Test.zip
Tests with the new Display Magician: Now it seems fine withour Custom DSR Resolutions. I can delete them and its working to switch between surround and not surround.
What is nor Working: I have now three Configs Surround 1440p Normal 1440p Normal 1080p (I only have 1080p Monitors)
Changing from Surround an Normal 1440p and vice versa is working Changing from Surround to Normal 1080p does switch to 1440p resolution, but surround off Changing from Normal 1440p to Normal 1080p doesn't switch the text resolution (for 1440p it's on 125 percent and for 1080p it's 100 percent)
Hi @FormelLMS
I don't think DisplayMagician stores the text sizing at all. I'd have to double-check to confirm, but I think that may be in the GetDisplayConfig function, and we don't currently get that information.
I've tried making a C# function to access GetDisplayConfig and SetDisplayConfig in the past, but I could never get it to work. I'm a lot more comfortable writing Process Invoke fictions now, so I might revisit that.
I guess what I'm saying is I may not be able to get the text size working. I'll take a look at it, but I'll have to judge how tricky it will be and how much it will affect the rest of the DisplayMagician codebase.
Thanks Terry
On Sun, 30 Jan 2022, 00:03 FormelLMS, @.***> wrote:
So we now are steps ahead :)
Tests with NvidiaInfo 1.5.1: After Applying the regular.cfg I got those error Message:
Attempting to apply NVIDIA display config from regular.cfg ERROR - NVIDIAInfo Windows CCD settings were not applied correctly.
Equality checks then of surround and regular.cfg are NOT equal after that Taskbar was on the left monitor instead of the middle
After changing back to surround profile, the surround.cfg was equal NvidiaInfo 1.5.1 Test.zip https://github.com/terrymacdonald/DisplayMagician/files/7963530/NvidiaInfo.1.5.1.Test.zip
Tests with the new Display Magician: Now it seems fine withour Custom DSR Resolutions. I can delete them and its working to switch between surround and not surround.
What is nor Working: I have now three Configs Surround 1440p Normal 1440p Normal 1080p (I only have 1080p Monitors)
Changing from Surround an Normal 1440p and vice versa is working Changing from Surround to Normal 1080p does switch to 1440p resolution, but surround off Changing from Normal 1440p to Normal 1080p doesn't switch the text resolution (for 1440p it's on 125 percent and for 1080p it's 100 percent)
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1024889628, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LGM23TH2KYDKOJUMYLUYPCRRANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
@FormelLMS, can you please send me a DisplayMagician support zip, and a screenshot showing where you set the text sizing in the NVIDIA Control panel? This will help me find where the information is in the NVAPI.
Thanks Terry
On Sun, 30 Jan 2022, 07:42 Terry MacDonald, @.***> wrote:
Hi @FormelLMS
I don't think DisplayMagician stores the text sizing at all. I'd have to double-check to confirm, but I think that may be in the GetDisplayConfig function, and we don't currently get that information.
I've tried making a C# function to access GetDisplayConfig and SetDisplayConfig in the past, but I could never get it to work. I'm a lot more comfortable writing Process Invoke fictions now, so I might revisit that.
I guess what I'm saying is I may not be able to get the text size working. I'll take a look at it, but I'll have to judge how tricky it will be and how much it will affect the rest of the DisplayMagician codebase.
Thanks Terry
On Sun, 30 Jan 2022, 00:03 FormelLMS, @.***> wrote:
So we now are steps ahead :)
Tests with NvidiaInfo 1.5.1: After Applying the regular.cfg I got those error Message:
Attempting to apply NVIDIA display config from regular.cfg ERROR - NVIDIAInfo Windows CCD settings were not applied correctly.
Equality checks then of surround and regular.cfg are NOT equal after that Taskbar was on the left monitor instead of the middle
After changing back to surround profile, the surround.cfg was equal NvidiaInfo 1.5.1 Test.zip https://github.com/terrymacdonald/DisplayMagician/files/7963530/NvidiaInfo.1.5.1.Test.zip
Tests with the new Display Magician: Now it seems fine withour Custom DSR Resolutions. I can delete them and its working to switch between surround and not surround.
What is nor Working: I have now three Configs Surround 1440p Normal 1440p Normal 1080p (I only have 1080p Monitors)
Changing from Surround an Normal 1440p and vice versa is working Changing from Surround to Normal 1080p does switch to 1440p resolution, but surround off Changing from Normal 1440p to Normal 1080p doesn't switch the text resolution (for 1440p it's on 125 percent and for 1080p it's 100 percent)
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1024889628, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LGM23TH2KYDKOJUMYLUYPCRRANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
Gah! I'll have to hold off on the Get/SetDisplayConfig work as I've found a bug in the way that Windows handles taskbar position changes on daisy-chained DisplayPort screens. Windows Settings doesn't update registry for the 2nd connected display (the one daisy-chained from the first one), meaning that I can't just record the taskbar settings as they could be wrong :(. So I now have to do some changes to store the actual intent of the user, and then make my code brute force those details into reality.
Windows does get frustrating at times :(.
Hi Terry,
sorry for the delay. I've got an error in powershell but thanks to @FormelLMS the error was because I did not used the .\ before the command line.
I've got my result from nvidiainfo 1.51, see atached files. I will try later today with DM 2.2.0.112
Thank you Results sk666.zip
Thanks sk666.
On Mon, 31 Jan 2022, 02:35 sk666, @.***> wrote:
Hi Terry,
sorry for the delay. I've got an error in powershell but thanks to @FormelLMS https://github.com/FormelLMS the error was because I did not used the .\ before the command line.
I've got my result from nvidiainfo 1.51, see atached files. I will try later today with DM 2.2.0.112
Thank you Results sk666.zip https://github.com/terrymacdonald/DisplayMagician/files/7965988/Results.sk666.zip
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1025145188, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LB2S6E2D2AUVCXN7FDUYU5CFANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
hi Terry,
v2.2.0.112 od DM is totally unusable on my computer, it faild at the opening and DM can not bypass this error so I can not create a log zip file. I need to kill it by the task manager after the error spawn.
The error is in french but I think in english is something like: "The value can not be null. Paramter name: first".
Did you ever seen that before?
Thank you
Hi @sk666,
Can you please delete the existing DisplayProfile_2.2.json file you having in your DisplayMagician app folder? The updating process assumes you don't have a DisplayProfile_2.2.json file, but as you've been helping me you already have that file
If you delete the existing DisplayProfile_2.2.json file from your DisplayMagician appdata folder then it should start up properly.
Thanks Terry
On Mon, 31 Jan 2022, 14:07 sk666, @.***> wrote:
hi Terry,
v2.2.0.112 od DM is totally unusable on my computer, it faild at the opening and DM can not bypass this error so I can not create a log zip file. I need to kill it by the task manager after the error spawn.
The error is in french but I think in english is something like: "The value can not be null. Paramter name: first".
Did you ever seen that before?
Thank you
[image: fatal error at openning] https://user-images.githubusercontent.com/29050341/151726073-d09d8cfa-37fe-4078-bbe5-81194ea4e5a7.PNG
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1025286961, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LEZKMVS55QYJH2C72LUYXOGRANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
Hey Terry, here you can find the support zip. Text Scaling isn't in nvidia driver, it's in the display options. DisplayMagician-Support-20220131-2019.zip
Hi Terry,
I found the 2.2.json file, I deleted it, and started agian DM. It recreate it and then crash with the same error :(
Thank you
Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg
From: terrymacdonald @.> Sent: Sunday, January 30, 2022 11:47:25 PM To: terrymacdonald/DisplayMagician @.> Cc: sk666 @.>; Mention @.> Subject: Re: [terrymacdonald/DisplayMagician] Switching Nvidia Surround OFF doesn't work (Issue #76)
Hi @sk666,
Can you please delete the existing DisplayProfile_2.2.json file you having in your DisplayMagician app folder? The updating process assumes you don't have a DisplayProfile_2.2.json file, but as you've been helping me you already have that file
If you delete the existing DisplayProfile_2.2.json file from your DisplayMagician appdata folder then it should start up properly.
Thanks Terry
On Mon, 31 Jan 2022, 14:07 sk666, @.***> wrote:
hi Terry,
v2.2.0.112 od DM is totally unusable on my computer, it faild at the opening and DM can not bypass this error so I can not create a log zip file. I need to kill it by the task manager after the error spawn.
The error is in french but I think in english is something like: "The value can not be null. Paramter name: first".
Did you ever seen that before?
Thank you
[image: fatal error at openning] https://user-images.githubusercontent.com/29050341/151726073-d09d8cfa-37fe-4078-bbe5-81194ea4e5a7.PNG
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1025286961, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LEZKMVS55QYJH2C72LUYXOGRANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHubhttps://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1025377912, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG5ULZMT5R2YHGJWRGM6GF3UYYH53ANCNFSM5LQYQTWA. Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: @.***>
Oh shoot. That's not good. I think it's indicating that there is a config
element that is null that is not supposed to be null. Can you please upload
the DisplayMagician.log file, and any other DisplayMagician1.log -
DisplayMagician4.log log files you find in the
C:\Users\
Thanks
Terry MacDonald | Principal Security Consultant | Chief Operating Officer
M: +64 211 918 814 <+64+211+918+814> E: @.*** W: www.cosive.com
On Tue, 1 Feb 2022 at 13:55, sk666 @.***> wrote:
Hi Terry,
I found the 2.2.json file, I deleted it, and started agian DM. It recreate it and then crash with the same error :(
Thank you
Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg
From: terrymacdonald @.> Sent: Sunday, January 30, 2022 11:47:25 PM To: terrymacdonald/DisplayMagician @.> Cc: sk666 @.>; Mention @.> Subject: Re: [terrymacdonald/DisplayMagician] Switching Nvidia Surround OFF doesn't work (Issue #76)
Hi @sk666,
Can you please delete the existing DisplayProfile_2.2.json file you having in your DisplayMagician app folder? The updating process assumes you don't have a DisplayProfile_2.2.json file, but as you've been helping me you already have that file
If you delete the existing DisplayProfile_2.2.json file from your DisplayMagician appdata folder then it should start up properly.
Thanks Terry
On Mon, 31 Jan 2022, 14:07 sk666, @.***> wrote:
hi Terry,
v2.2.0.112 od DM is totally unusable on my computer, it faild at the opening and DM can not bypass this error so I can not create a log zip file. I need to kill it by the task manager after the error spawn.
The error is in french but I think in english is something like: "The value can not be null. Paramter name: first".
Did you ever seen that before?
Thank you
[image: fatal error at openning] < https://user-images.githubusercontent.com/29050341/151726073-d09d8cfa-37fe-4078-bbe5-81194ea4e5a7.PNG
— Reply to this email directly, view it on GitHub < https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1025286961 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABLU5LEZKMVS55QYJH2C72LUYXOGRANCNFSM5LQYQTWA
. Triage notifications on the go with GitHub Mobile for iOS < https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub< https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1025377912>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AG5ULZMT5R2YHGJWRGM6GF3UYYH53ANCNFSM5LQYQTWA
. Triage notifications on the go with GitHub Mobile for iOS< https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android< https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub . You are receiving this because you were mentioned.Message ID: @.***>
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1026364300, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LBVCNPKHFRMGIZUXGTUY4VPTANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
Weird. This is complaining about missing colour information from your screens in your configuration. That shouldn't happen.
2022-01-31 19:53:43.0618|ERROR|DisplayMagician.Program|Program/StartUpApplication top level exception: La valeur ne peut pas 괲e null.
Nom du param贲e : first: ࠓystem.Linq.Enumerable.SequenceEqual[TSource](IEnumerable`1 first, IEnumerable`1 second, IEqualityComparer`1 comparer)
ࠄisplayMagicianShared.NVIDIA.NVIDIA_COLOR_CONFIG.Equals(NVIDIA_COLOR_CONFIG other)
ࠄisplayMagicianShared.NVIDIA.NVIDIA_DISPLAY_CONFIG.Equals(NVIDIA_DISPLAY_CONFIG other)
ࠄisplayMagicianShared.ProfileItem.Equals(ProfileItem other)
ࠄisplayMagicianShared.ProfileRepository.UpdateActiveProfile()
ࠄisplayMagicianShared.ProfileRepository.get_CurrentProfile()
ࠄisplayMagicianShared.ProfileItem.get_IsActive()
ࠄisplayMagician.UIForms.MainForm.RefreshNotifyIconMenus()
ࠄisplayMagician.UIForms.MainForm..ctor(Form formToOpen)
ࠄisplayMagician.Program.StartUpApplication() -
The problem is with the Dell 2208WFP screen with UID4356 connected via DVI:
WINAPI|\\?\PCI#VEN_10DE&DEV_13C2&SUBSYS_85081043&REV_A1#4&80e7924&0&0008#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DVI|44048|16444|\\?\DISPLAY#DEL403C#5&28d4f9e&1&UID4356#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|DELL 2208WFP
I believe that this is because DVI doesn't support accessing the colour information through it. I think this may be the source of part of your past problems, and definitely a bug with NVIDIALibrary, AMDLibrary and WinLibrary! This is a great find!
I will see what I can do to not grab colour settings with some of the older style screens. This might help avoid some of the issues with older hardware until the newer hardware becomes the norm.
Thanks Terry
Hi Terry,
don't loose your precious time on that, I can live with the 1.1.4 version od DM. I will change my 2 old monitor eventually, so I will not use DVi with my new screens. If it's possible to stay with 1.1.4 with nvidia and w10, it will do the job for me. My computer could not have w11 so I will need to change it too in the next 3 years.
Thank you
No no, it's something fairly easy to add, and I want everyone to be able to use the new faster DM. It's just a little more work, and it will mean I avoid so many other future issues.
Thanks Terry
On Thu, 3 Feb 2022, 03:22 sk666, @.***> wrote:
Hi Terry,
don't loose your precious time on that, I can live with the 1.1.4 version od DM. I will change my 2 old monitor eventually, so I will not use DVi with my new screens. If it's possible to stay with 1.1.4 with nvidia and w10, it will do the job for me. My computer could not have w11 so I will need to change it too in the next 3 years.
Thank you
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1027989243, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LEHNIOHAWFTTABF7CDUZE42TANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
@sk666 and @FormelLMS - some more tests to perform please! I've just finished getting taskbar settings to record and I'm pretty happy with how they turned out :). I've also configured DisplayMagician to ignore getting HDR/Colour settings from the following types of connections: VGA, COMPONENT, SVIDEO, DVI, COMPOSITE.
@sk666 that should stop you getting errors (hopefully), so it would be cool if you could both install DisplayMagician v2.2.0.179 (yes this is build number 179!) that I've attached here.
IMPORTANT: YOU WILL NEED TO DELETE YOUR DisplayProfiles_2.2.json file AND CREATE NEW PROFILES FROM SCRATCH.
This version includes changed DisplayProfile format again in order to track all the new features we've been working on recently. It will require new display profiles.
DisplayMagicianSetup-v2.2.0.179.zip
Please test this out and see if there are any broken bits. If there are, please upload a Support ZIP File with a description of what's wrong.
I think we're getting really close to a new release!
Thanks Terry
Hi Terry,
wow build 179. It was a lot of work, but I'm glad to say that this build fix the switching profile bug, and it resolve my bog with DVI when I start DM :) I hope that it will fix the issue too for @FormelLMS
Issue 75 still persist for me, even if the app is minimized to system tray or not. But at least, DM works again, thank you very much :)
@sk666 @FormelLMS I fixed yet more issues, so now please test DisplayMagician v2.2.0.223 (attached). This new version shows the taskbars in the DM UI, and also lets you easily change your taskbar layout using the new 'Profile Tools' button on the Display Profiles page :).
Can I please trouble you to do some testing for me again? I think I have fixed the issues you mentioned , but I really need confirmation from you that it is now working.
IMPORTANT: Just to be sure, can you delete all your C:\Users
Then please download DisplayMagician v2.2.0.223 and install it. Then set up new Display Profiles, and then use those profiles in the Game Shortcuts. DisplayMagicianSetup-v2.2.0.223.zip
Please test the following:
And then please report back with what you've found.
Thanks Terry
Hi Terry,
everything seems to be working fine for me with build .223 including taskbar..except for what I said previously in my last reply on issue #75.
thank you
Hi @sk666,
Can you please create a new Support Zip file in 223 and upload it under issue #75? It's like to double check to see what the final issue is now we've solved the others.
Thanks Terry
On Thu, 10 Feb 2022, 01:56 sk666, @.***> wrote:
Hi Terry,
everything seems to be working fine for me with build .223 including taskbar..except for what I said previously in my last reply on issue #75 https://github.com/terrymacdonald/DisplayMagician/issues/75.
thank you
— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1033732984, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LES2XIEOT6BBN2DMWDU2JQBXANCNFSM5LQYQTWA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>
Hey Terry, I'm sorry, I was away a few days. Tried now the new version and everything is working well. This is fantastic. Changed taskbar to the top in normal mode. In Surround mode it's not working, but I think this is normal. Taskbar is a bit strange in behaviour of surround :) Changing the profiles is very fast now.
Thank you very much!
Ok, I'm going to close this issue as it is fixed in the codebase. I'll concentrate on getting the taskbar location sorted.
Describe the bug I have made the update to 2.1.5.5 and Switching from Surround to normal mode is not working here
To Reproduce Steps to reproduce the behaviour: Saved two new Display Profiles. One with Surround and One without. Switching from normal to surround is flawlessly working, but back to normal not.
Expected behaviour :)
Screenshots If applicable, add screenshots to help explain your problem.
Reporting Logs If DisplayMagician starts:
Enviroment (please complete the following information):
DisplayMagician-Support-20220108-1707.zip