search

terrymacdonald / DisplayMagician

DisplayMagician is an open source tool for automatically configuring your displays and sound for a game or application from a single Windows Shortcut.
https://displaymagician.littlebitbig.com
GNU General Public License v3.0
443 stars 18 forks source link

Switching Nvidia Surround OFF doesn't work #76

Closed FormelLMS closed 2 years ago

FormelLMS commented 2 years ago

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):

terrymacdonald commented 2 years ago

@FormelLMS What version of DisplayMagician were you running before you upgraded? That will let me see what differences there are between the versions.

Are you able to please install this test version I just created and see if it has the same problem? If this does still have the same problems then we'll need to troubleshoot further with NVIDIAInfo. DisplayMagicianSetup-v2.2.0.4.zip

Thanks Terry

terrymacdonald commented 2 years ago

Unfortunately I couldn't see any problems in the DisplayMagician.log file because DisplayMagician starts a brand new log file each time it starts. In versions 2.1.5.5 and earlier you would need to start DisplayMagician change to your "Surround 1440p" profile then back again to your "Normal 1440p" profile, and then go straight to the 'Create Support ZIP file' button and save the zip file in order to save the log file with information about the profile swap in it.

In the test version 2.2.0.4 I gave you, I've now made DisplayMagician automatically keep copies of the last 4 log files, and include them in the Support ZIP file, so you won't need to worry about that from now on at least :). Constant improvement....

So yeah, please swap from your "Surround 1440p" profile then back again to your "Normal 1440p" profile, and then create a support ZIP file for me and upload it again. One of the DisplayMagician.log files in the support ZIP file should give me more information about the issue.

I do think we'll need to do some testing with NVIDIAInfo though based on your description of the issue. We'll wait until I get to see the DisplayMagician log file before we'll do any NVIDIAInfo testing though.

Thanks Terry

sk666 commented 2 years ago

Hi Terry,

if this can help, I have this issue too with 2.2.0.4. I need to quit surround by nvidia control panel. As you can see in this picture, DM start to roll back to 1920x1080 profile but it keep surround instead. This picture was taken after I selected 1920x1080 and then clicked on the Apply button.

Capture

FormelLMS commented 2 years ago

Hey Terry, thanks for helping out. I've tried some things now. Installed the new version. This does the same. Then uninstalled driver via DDU und renewed that all, but that didn't do the trick, too. Did the log file and dropped it here. It's exactly as sk666 said (Thank You :) ) DisplayMagician-Support-20220109-1410.zip

What I have to say is that driver installing, forcing my 1080p displays to 1440p was a pain in the ass. When switching Surround off in the nvidia driver, the mark remains even after pressing apply. I have to that twice: Uncheck, apply, wait - uncheck, apply. Then the mark is unchecked in driver. (At second: After rebooting, surround is enabled again. Something seems to be very wrong on the driver and/or Windows 11 here. UPDATE: THIS IS OKAY NOW. Reboot and normal profile remains active) @sk666 you using Win11, too?

sk666 commented 2 years ago

@FormelLMS no I have W10 21H2. I used DDU myself 2 days ago to fix another issue with DM and this bug happening too so uninstall and reinstall nvidia driver dosen't work for this issue like you said :(

FormelLMS commented 2 years ago

@FormelLMS no I have W10 21H2. I used DDU myself 2 days ago to fix another issue with DM and this bug happening too so uninstall and reinstall nvidia driver dosen't work for this issue like you said :(

Good news that it seems to be not an Win 11 issue. In my inner eyes I saw me weeks of fiddling with a new windows installation

terrymacdonald commented 2 years ago

Hmmmm. I wonder if this is related to the switch to a multithreaded process too? TBH I've lost track of which version has what, so I'll have to look into it deeper over the next few days.

I'm currently taking some time to map out the flow of logic and calling logic for the new multithreaded model we've moved to, and I'll be going through each statement to figure out where any issues may be. As mentioned above this could be related to that.

This could take a little while to sort out ☹️.

@FormelLMS, could you please do some testing for me with NVIDIAInfo? I'd like to see if the NVIDIALibrary I made still works, and NVIDIAInfo allows us to test that.

I've reused some instructions below. Please run through them exactly as shown. Note: where it says 'Racing', it means your surround display layout....

So, can you please download the latest NVIDIAInfo zip from https://github.com/terrymacdonald/NVIDIAInfo/releases and unzip it to a test folder. Then open a command line/powershell to that same folder and run through the following commands. Make sure you do every step in order, and record the results:

At this stage we have the two basic configs set. Next step is to see if it works changing between them:

Once you've got to this point, please come back here and tell me the results, and upload all the log files, and the .cfg files you created. That will all give me enough information to tell you the next steps.

Thanks Terry

On Mon, 10 Jan 2022, 02:27 FormelLMS, @.***> wrote:

@FormelLMS https://github.com/FormelLMS no I have W10 21H2. I used DDU myself 2 days ago to fix another issue with DM and this bug happening too so uninstall and reinstall nvidia driver dosen't work for this issue like you said :(

Gods news that it seems to be not an Win 11 issue. In my inner eyes I saw me weeks of fiddling with a new windows installation

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1008298234, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LGLEPJT6UO7EZITAVDUVGEMFANCNFSM5LQYQTWA . 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 assigned.Message ID: @.***>

FormelLMS commented 2 years ago

Hey Terry, thanks for looking up here :) I did my very best and followed your instructions. I've understood everything you wrote so here are the results:

Saved the regular cfg und it was equal to the actual one. Them switched to my surround mode an made the surround cfg. This was then equal to the profile loaded. But switching back to the regular one doesn't work here, too. I've renamed the logfiles and put everything to the attached zip file.

Hoping, there is something in for you :) DisplayMagician Issue76 FormelLMS.zip

No poblem if it takes a bit longer. Fortunately the switchback to surround is working here. This is the worser part to do manually. Switching back to regular is much easier manually ;)

terrymacdonald commented 2 years ago

I think I might know what's happening but I'll need to figure it out tonight. It looks from the logs in my testing that the NVIDIALibrary is running in parallel (at the same time) as the WinLibrary functions. This is not supposed to happen - they must run after each other in sequence - so I definitely think it's something that changing to the multithreaded model has caused to happen.

Because each thread is independent, that potentially explains why people are having different problems for each other. Each computer has different hardware that runs at different speeds. This difference in hardware means that each computer gets to different parts of the code at different times, meaning they may clash in different ways. For example in my testing I cannot apply a surround profile properly, but heading back to a non surround profile works fine. @FormelLMS cannot from a surround profile to a non-surround one.

This may not be the only problem, but it is definitely a contributor to the issues we're seeing. I'll need to map out the thread data flows, and figure out how I'm going to stop this from happening. I need to make the child processes wait for each other.

I'll let you both know when I find the actual root cause.

Thanks Terry

terrymacdonald commented 2 years ago

OK @FormelLMS - I think I finally cracked this last night. I had to transition from the original toast notification library I was using to the newer Microsoft one. I think this will work better in the long run, as it will be updated by Microsoft to support their windows Toast improvements as Windows dev continues.

In any case, can you please install this test v2.2.0.41 please? And see if all your errors have disappeared? Please report back with any errors you find (screenshots too please if possible) and of course upload the support ZIP file if you have any errors too.

DisplayMagicianSetup-v2.2.0.41.zip

Thanks Terry

terrymacdonald commented 2 years ago

@FormelLMS I've finally had a chance to look at your NVIDIAInfo logs. There is indeed a problem that NVIDIALibrary complains about: 

2022-01-09 18:52:18.7318|WARN|DisplayMagicianShared.SharedLogger|NVIDIALibrary/SetActiveConfig: There was an error disabling the display mode. NvAPI_Mosaic_EnableCurrentTopo() returned error code NVAPI_MODE_CHANGE_FAILED

This is the NVIDIA Driver complaining when we try to turn off the NVIDIA Surround (Mosaic). It's saying it can't turn it off! I have NO idea why, as the config that we are currently using has mosaic enabled, and the one we want to use does not have mosaic enabled, so we should be able to turn off the mosaic mode! This should work (it WAS working) - I can only believe it is a NVIDIA driver error or something. I'll do some more research over the next few days to see if I can add some additional tests in there somehow(?).

Did you install a cut-down version of NVIDIA driver using a custom installer? Or did you install the stock NVIDIA game ready driver from NVIDIA itself?

What version of NVIDIA video card are you running? NVIDIA GTX3070? 3080 Ti? Which manufacturer and model is it? Is it the same one that @sk666 has?

I have just noticed that there is a new NVIDIA Game ready driver 511.23. an you please try and install the stock version of that using the NVIDIA installer and see if that works?

I need one more cfg file from you as well. I need to compare the NVIDIAInfo configuration that we want to apply with the setup that actually results, so can you please run the following commands for me (in the exact order shown)?

Open a powershell terminal window in the same folder as the NVIDIAInfo program, then:

Next, create a zip archive containing the following files, and upload it here:

With that info, I should be able to see what has changed (or not changed) between the different profile changes. It will give me a good idea on what bits I need to look at.

Thanks Terry

terrymacdonald commented 2 years ago

Ah I just looked up the top of the list for the video card. Its a Gigabyte 3080 Ti. No need to include that info in the last response any more :)

terrymacdonald commented 2 years ago

@FormelLMS Can you please try those tests I listed above with the new test version of NVIDIAInfo (v1.3.9) which I've linked in this comment? It has an extra step where I try to doublecheck that the mosaic is enabled before I try turning it off. I'm doubtful this will fix anything, but I thought I'd add in the check just in case.

NVIDIAInfo-v1.3.9.zip

Everything still works on my system (but it was working before too!). I've never had the issues you've experienced yet, which makes it really hard to troubleshoot.

Thanks Terry

FormelLMS commented 2 years ago

Hey Terry, hope, your doing well. Heard of that volcano and thought of you there.

I've updated now to the driver you say and the new display magician. This alone doesn't work unfortunately. I always install the nvidia drivers without any exceptions (express install)

So here are the next stepstaken with 1.3.9 of NVIDIAInfo. Hopefully it will help you to try to sort it out :) Hopefully didn't forgot a file. Desktop.zip

terrymacdonald commented 2 years ago

@FormelLMS Thanks for that. It unfortunately shows that the extra layer of protection I added doesn't help. That tells me that The NVIDIA driver knows that Mosaic is enabled, which makes it so more confusing that it won't let us turn Mosaic off :(. 

2022-01-15 12:56:54.9091|ERROR|DisplayMagicianShared.SharedLogger|NVIDIALibrary/SetActiveConfig: There was an error disabling the display mode. NvAPI_Mosaic_EnableCurrentTopo() returned error code NVAPI_MODE_CHANGE_FAILED

Ok - so time for my next theory. My hypothesis is that maybe the Mosaic function has now been updated to doublecheck that the mode it is changing to is a valid mode for windows. If this is the case, then maybe it's best to turn off the Mosaic mode as the first thing we do. At the moment we turn off any NVIDIA custom HDR/Colour settings before we change the Mosaic. NVIDIAInfo v1.3.9b tests that theory, and I've attached it below. We'll see if the that makes the NvAPI_Mosaic_EnableCurrentTopo(false) function call work.

NVIDIAInfo-v1.3.9b.zip

Please note that as I've disabled the NVIDIA custom HDR/Colour change code, the equality tests won't work (as the colour will always be wrong).

Can you please run through these set of tests again please? We'll name these the 'surround off NVIDIAInfo tests' so that I can just tell you to run the 'surround off NVIDIAInfo tests' and you'll know what I mean :)

Open a powershell terminal window in the same folder as the NVIDIAInfo program, then:

Next, create a zip archive containing the following files, and upload it here:

Let's see if this is the thing causing the issue. I might need to raise a helpdesk ticket with NVIDIA if this doesn't work.

Thanks Terry

FormelLMS commented 2 years ago

Hey Terry,

thanks again for helping here. Unfortunately the problem still exists at the same stop. Loading the regular.cfg doesn't apply here. I've put the zip file together. Hoing you can find something :)

surround off NVIDIAInfo tests.zip

terrymacdonald commented 2 years ago

Hi,

I hope so too! I know where the problem is, but I'm not sure how to work around it without help from NVIDIA themselves. The difficulty is that the error occurs on the only 'turn off surround' function they have. I can't find another way to disable surround, which means we have to try and figure out why it is happening.

Thanks Terry

On Mon, 17 Jan 2022, 01:10 FormelLMS, @.***> wrote:

Hey Terry,

thanks again for helping here. Unfortunately the problem still exists at the same stop. Loading the regular.cfg doesn't apply here. I've put the zip file together. Hoing you can find something :)

surround off NVIDIAInfo tests.zip https://github.com/terrymacdonald/DisplayMagician/files/7876898/surround.off.NVIDIAInfo.tests.zip

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1013864239, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LB3F4JBF2VPF55EQXDUWKYTLANCNFSM5LQYQTWA . 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 assigned.Message ID: @.***>

FormelLMS commented 2 years ago

Do you think it could be a problem here on my setup in any way? I don’t want to take your time if it’s not on programs side. Bit if I can help in any way, I will do 😊

terrymacdonald commented 2 years ago

Maybe? There appears to be subset of people with this issue so far, so trying to figure out what the common feature is.

I just had a thought. If I remember correctly your surround set up uses bezel adjustment. Are you able to create a non-bezel adjusted surround layout and save it as a new NVIDIAInfo cfg? Then try swapping to regular.cfg and see if that works?

Thanks Terry

FormelLMS commented 2 years ago

Terry - unfortunately it's the same.

terrymacdonald commented 2 years ago

@FormelLMS Thanks to @erbkaiser I've been doing some other tests in the background, and I've got a hunch that the EnableMosaicTopo error we were getting may be a residual error left over from some of our earlier bugs. So I'd like you to perform the following tests for me:

I'm hoping that all of the other fixes we have come up with recently will mean that the two newly created profiles will work. I think that the other profiles were created when I still had some multithreading issues, and that may have introduced errors to the display profiles we made then. That of course means that were broken when they were made, which means they will never work (there isn't a way to fix them).

Hopefully, recreating them both again new will mean that they have the correct data in them, and hopefully they will just start working again! Your tests will help say if that's right.

Also - this test version has the 'Send to Clipboard' menu item you wanted in it ;).

Thanks Terry

FormelLMS commented 2 years ago

Hey Terry. At first many thanks for the copy to clipboard. This is working very well. My Backup has included the files already :)

But I have to say that the new version can't change the Surround to normal, too unfortunately. I really has the biggest hopes after your last notification. DisplayMagician-Support-20220119-2003.zip

terrymacdonald commented 2 years ago

Hi @FormelLMS.

Yeah, I figured that would happen, based on @sk666 similar finding. Its that same error with disabling Mosaic/Surround mode. Looks like we need to wait for NVIDIA to get back to us.

I've logged a question on their forum, but the person I need to speak with is apparently on holiday, so it could be a little while.

I also had a look at how Souosh Falahati (original dev of Helios Display Management) handled disabling surround mode, and he did it the exact same way that I do it. I was hoping he'd found an alternative way to do it ☹️.

So now we're a bit stuck, and we need to wait for guidance from NVIDIA. My gut feel is some kind of NVIDIA or windows bug affecting some users. The bulk of people seem to have everything working fine.

One extra question. I'd you apply the surround profile a second time straight after it fails, does it still fail a second time?

Oh, and there is one more thing you could try? I read somewhere that Guru3dcs Display Driver Uninstaller ( https://www.guru3d.com/files-details/display-driver-uninstaller-download.html) will completely remove all traces of NVIDIA driver, and then that would let you reinstall it as new. This would confirm that the problem wasn't caused by a previous NVIDIA upgrade, and would ensure that you have the latest NVIDIA settings as if you just installed a brand new video card.

I've never used DDU, so please only use DDU if you are comfortable with fixing any issues it may cause.

Good luck, and I'll keep seeing what I can find.

Thanks Terry

On Thu, 20 Jan 2022, 08:05 FormelLMS, @.***> wrote:

Hey Terry. At first many thanks for the copy to clipboard. This is working very well. My Backup has included the files already :)

But I have to say that the new version can't change the Surround to normal, too unfortunately. I really has the biggest hopes after your last notification. DisplayMagician-Support-20220119-2003.zip https://github.com/terrymacdonald/DisplayMagician/files/7899942/DisplayMagician-Support-20220119-2003.zip

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1016778320, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LBOBGXT6QLIGCVD43TUW4DQJANCNFSM5LQYQTWA . 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 assigned.Message ID: @.***>

terrymacdonald commented 2 years ago

@FormelLMS can you please uninstall 2.2.0.52, and then try 2.1.5.37 again please? I want to know if you still get this NvAPI_Mosaic_EnableCurrentTopo(0) error changing between the regular and surround display profiles with the older 2.1.5 software. If that's the case, then I know it's nothing to do with the multithreaded singleinstance code I've added since 2.1.5.37 (which is now part of 2.2.0.52).

Should be able to use the config you have now.

Please generate a Support ZIP, and then you can upgrade to the 2.2.0.52 test version I gave you before.

Thanks Terry

FormelLMS commented 2 years ago

Yes, can you send me the 2.1.5? I only find the 2.1.5.5 Sorry :(

terrymacdonald commented 2 years ago

@FormelLMS sorry I meant 2.1.5.5. But scratch that idea....

Instead, can you download and try the last version of DisplayMagician that you know was successfully swapping display layouts for you? I would like to see if an old version that was working ok before still is working for you now.

The idea is to see if the NVIDIA driver has changed and stopped DisplayMagician from working for you. If the older version that was working properly in the past no longer works for you now, then we know that it is the NVIDIA driver, or something on windows that has changed to do it working.

If the older version that was working properly in the past still works for you now, then we know that it's something in the latter versions of DisplayMagician that is the cause.

Can you please give that test a go and see what you find?

Note: you don't need to delete your current Configs, just rename the c:\Users\\AppData\Local\DisplayMagician folder to something like c:\Users\\AppData\Local\DisplayMagicianBackup, and then install and run the version of DisplayMagician you want to test. You can then rename the folder back when you want the old Configs back again.

Thanks Terry

versedi commented 2 years ago

The idea is to see if the NVIDIA driver has changed and stopped DisplayMagician from working for you. If the older version that was working properly in the past no longer works for you now, then we know that it is the NVIDIA driver, or something on windows that has changed to do it working.

I think this is what happened to me, I had the whole PC crashing while swapping from surround to single screen.

Today I've made even more mess by unplugging a monitor in Surround, and replugging via other cable source. I'm stucked with Display Magician being uninstalled still doing something wonky with Windows Apps and resetting my two monitors that remained plugged. I've tried DDU - it worked until I've started AC again.

At this point I'm going to reinstall my Windows setup cause I'm out of ideas, Even CCleaner restarts my two monitors.

sk666 commented 2 years ago

@versedi did you tried to roll back a system restore point?

versedi commented 2 years ago

I didn't had one setup and from what I've tried it might have been something with broken installation of 1.x.6 that I couldn't even remove (It appeared like I had two instances installed but one was unremovable after one of the updates).

Windows reinstall obviously fixed the issue, though I highly recommend everyone to avoid unplugging a monitor on one cable source while in Surround and plugging it back with other.

It was just domino effect of bugs after that. Which also might have started with the driver update couple of days ago - since then I've had to hard restart my PC when switching back from Surround to 1 or 2 monitor setup.

I'm gonna create a separate issue with steps to possibly reproduce the bug.

terrymacdonald commented 2 years ago

Do you think it was the unplugging of the surround that caused your problem?

On Sun, 23 Jan 2022, 17:24 Tadeusz Stępnikowski, @.***> wrote:

I didn't had one setup and from what I've tried it might have been something with broken installation of 1.x.6 that I couldn't even removed.

Windows reinstall obviously fixed the issue, though I highly recommend everyone to avoid unplugging a monitor on one cable source while in Surround and plugging it back with other.

It was just domino effect of bugs after that.

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019411493, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LC3U2M4OLXWVBI7KMDUXN7IJANCNFSM5LQYQTWA . 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 assigned.Message ID: @.***>

versedi commented 2 years ago

Do you think it was the unplugging of the surround that caused your problem?

@terrymacdonald #81

As for this issue I'm going to see in upcoming days if it still requires hard restart when switching from surround to single (sometimes, it's not consistent). If it does it's related either to the new Nvidia driver or something with Windows changing its UI (the new installation has completely different explorer notifications on Version 10.0.19044 Build 19044 compared to what I had)

It didn't happened before the driver update I did couple of days ago.

I'm on fresh OS install so we can scratch anything else messing up with this like my stucked 1.xx install in the programs list.

terrymacdonald commented 2 years ago

If you could look to see if there is an error in the DisplayMagician.log file that has "NvAPI_mosaic_enabletopo(0)" when you run the tests? If its got the same issue then it should have the same error message.

Thanks Terry

On Sun, 23 Jan 2022, 17:48 Tadeusz Stępnikowski, @.***> wrote:

Do you think it was the unplugging of the surround that caused your

@terrymacdonald https://github.com/terrymacdonald #81 https://github.com/terrymacdonald/DisplayMagician/issues/81

As for this issue I'm going to see in upcoming days if it still requires hard restart when switching from surround to single (sometimes, it's not consistent).

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019413407, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LBZ3T43TRBLSTHSZ3LUXOCARANCNFSM5LQYQTWA . 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 commented 2 years ago

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

terrymacdonald commented 2 years ago

Ok cool! So we know that it is something in the way that the NVIDIALibrary interacts with the Mosaic functions that isn't quite right now. It was ok (because it was working), but now it isn't working.

The strange thing is that it is only affecting a small percentage of users. The majority are completely fine. This makes it difficult to troubleshoot, as we don't have enough samples to know where the problem may lie.

Do you remember exactly when you started having issues with DisplayMagician? If you can it might give us an idea when this started happening.

The next question is how do we troubleshoot what is broken? Well I think I have a strategy that will work, though it will take a bit of time.

I think we should cut out as much from the configurations as possible, and then see if the mosaic can be turned off and turned on. Then if that works we keep adding in sections of coffee until we find the one that is causing the issues. If I make up a sequence of versions of NVIDIAInfo with minimal config and then more config, then we will get more of an answer out of it.

@sk666 and @FormelLMS, are you both happy to try out some more tests when the code is ready?

Thanks Terry

On Mon, 24 Jan 2022, 01:51 FormelLMS, @.***> wrote:

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019478907, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LB72NVXSN6DL776GR3UXP2VFANCNFSM5LQYQTWA . 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 commented 2 years ago

Hi terry,

My trouble with surround began when I started to use DM 2.x version, with your fjrst version if I remember correctly.

I will happy to help you more with that but it can take a couple of days during each test because I'm starting to be a little bit busy for a couple of week. But I will do it when I will have the time for sure :)

Thank you

Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg

From: terrymacdonald @.> Sent: Sunday, January 23, 2022 2:47:10 PM To: terrymacdonald/DisplayMagician @.> Cc: sk666 @.>; Mention @.> Subject: Re: [terrymacdonald/DisplayMagician] Switching Nvidia Surround OFF doesn't work (Issue #76)

Ok cool! So we know that it is something in the way that the NVIDIALibrary interacts with the Mosaic functions that isn't quite right now. It was ok (because it was working), but now it isn't working.

The strange thing is that it is only affecting a small percentage of users. The majority are completely fine. This makes it difficult to troubleshoot, as we don't have enough samples to know where the problem may lie.

Do you remember exactly when you started having issues with DisplayMagician? If you can it might give us an idea when this started happening.

The next question is how do we troubleshoot what is broken? Well I think I have a strategy that will work, though it will take a bit of time.

I think we should cut out as much from the configurations as possible, and then see if the mosaic can be turned off and turned on. Then if that works we keep adding in sections of coffee until we find the one that is causing the issues. If I make up a sequence of versions of NVIDIAInfo with minimal config and then more config, then we will get more of an answer out of it.

@sk666 and @FormelLMS, are you both happy to try out some more tests when the code is ready?

Thanks Terry

On Mon, 24 Jan 2022, 01:51 FormelLMS, @.***> wrote:

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019478907, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LB72NVXSN6DL776GR3UXP2VFANCNFSM5LQYQTWA . 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-1019554154, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG5ULZNZFGC4YJWBLXEEKCTUXRLL5ANCNFSM5LQYQTWA. 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: @.***>

terrymacdonald commented 2 years ago

Cool, thanks for the info @sk666. Don't work too much about a quick turnaround time. This is a tricky problem that will take a bit of time to sort out. It will be a while before we find a solution I think.

Thanks Terry

On Mon, 24 Jan 2022, 08:54 sk666, @.***> wrote:

Hi terry,

My trouble with surround began when I started to use DM 2.x version, with your fjrst version if I remember correctly.

I will happy to help you more with that but it can take a couple of days during each test because I'm starting to be a little bit busy for a couple of week. But I will do it when I will have the time for sure :)

Thank you

Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg

From: terrymacdonald @.> Sent: Sunday, January 23, 2022 2:47:10 PM To: terrymacdonald/DisplayMagician @.> Cc: sk666 @.>; Mention @.> Subject: Re: [terrymacdonald/DisplayMagician] Switching Nvidia Surround OFF doesn't work (Issue #76)

Ok cool! So we know that it is something in the way that the NVIDIALibrary interacts with the Mosaic functions that isn't quite right now. It was ok (because it was working), but now it isn't working.

The strange thing is that it is only affecting a small percentage of users. The majority are completely fine. This makes it difficult to troubleshoot, as we don't have enough samples to know where the problem may lie.

Do you remember exactly when you started having issues with DisplayMagician? If you can it might give us an idea when this started happening.

The next question is how do we troubleshoot what is broken? Well I think I have a strategy that will work, though it will take a bit of time.

I think we should cut out as much from the configurations as possible, and then see if the mosaic can be turned off and turned on. Then if that works we keep adding in sections of coffee until we find the one that is causing the issues. If I make up a sequence of versions of NVIDIAInfo with minimal config and then more config, then we will get more of an answer out of it.

@sk666 and @FormelLMS, are you both happy to try out some more tests when the code is ready?

Thanks Terry

On Mon, 24 Jan 2022, 01:51 FormelLMS, @.***> wrote:

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

— Reply to this email directly, view it on GitHub < https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019478907 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABLU5LB72NVXSN6DL776GR3UXP2VFANCNFSM5LQYQTWA

. 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-1019554154>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AG5ULZNZFGC4YJWBLXEEKCTUXRLL5ANCNFSM5LQYQTWA

. 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-1019555350, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LDSWNQMOEKGCCENCUTUXRMI7ANCNFSM5LQYQTWA . 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 commented 2 years ago

Call me in to test the steps :) For me it start to happen with the 2.x Version. I thought it will be much work to upgrade to 2.x so I’ve waited a long time to do that. But after installing Windows 11 I‘ve updated to 2.x.

Am 23.01.2022 um 21:36 schrieb terrymacdonald @.***>:

 Cool, thanks for the info @sk666. Don't work too much about a quick turnaround time. This is a tricky problem that will take a bit of time to sort out. It will be a while before we find a solution I think.

Thanks Terry

On Mon, 24 Jan 2022, 08:54 sk666, @.***> wrote:

Hi terry,

My trouble with surround began when I started to use DM 2.x version, with your fjrst version if I remember correctly.

I will happy to help you more with that but it can take a couple of days during each test because I'm starting to be a little bit busy for a couple of week. But I will do it when I will have the time for sure :)

Thank you

Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg

From: terrymacdonald @.> Sent: Sunday, January 23, 2022 2:47:10 PM To: terrymacdonald/DisplayMagician @.> Cc: sk666 @.>; Mention @.> Subject: Re: [terrymacdonald/DisplayMagician] Switching Nvidia Surround OFF doesn't work (Issue #76)

Ok cool! So we know that it is something in the way that the NVIDIALibrary interacts with the Mosaic functions that isn't quite right now. It was ok (because it was working), but now it isn't working.

The strange thing is that it is only affecting a small percentage of users. The majority are completely fine. This makes it difficult to troubleshoot, as we don't have enough samples to know where the problem may lie.

Do you remember exactly when you started having issues with DisplayMagician? If you can it might give us an idea when this started happening.

The next question is how do we troubleshoot what is broken? Well I think I have a strategy that will work, though it will take a bit of time.

I think we should cut out as much from the configurations as possible, and then see if the mosaic can be turned off and turned on. Then if that works we keep adding in sections of coffee until we find the one that is causing the issues. If I make up a sequence of versions of NVIDIAInfo with minimal config and then more config, then we will get more of an answer out of it.

@sk666 and @FormelLMS, are you both happy to try out some more tests when the code is ready?

Thanks Terry

On Mon, 24 Jan 2022, 01:51 FormelLMS, @.***> wrote:

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

— Reply to this email directly, view it on GitHub < https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019478907 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABLU5LB72NVXSN6DL776GR3UXP2VFANCNFSM5LQYQTWA

. 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-1019554154>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/AG5ULZNZFGC4YJWBLXEEKCTUXRLL5ANCNFSM5LQYQTWA

. 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-1019555350, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LDSWNQMOEKGCCENCUTUXRMI7ANCNFSM5LQYQTWA . 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, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.

terrymacdonald commented 2 years ago

Perfect. Thanks team.

I'll try have a think over the next few days about how I'm going to do this. This seems like quite a tricky little problem to discover and fix. The good thing is that you both reliably have the problem, so we should be able to know when we've fixed it too!

Thanks Terry

On Mon, 24 Jan 2022, 18:17 FormelLMS, @.***> wrote:

Call me in to test the steps :) For me it start to happen with the 2.x Version. I thought it will be much work to upgrade to 2.x so I’ve waited a long time to do that. But after installing Windows 11 I‘ve updated to 2.x.

Am 23.01.2022 um 21:36 schrieb terrymacdonald @.***>:

 Cool, thanks for the info @sk666. Don't work too much about a quick turnaround time. This is a tricky problem that will take a bit of time to sort out. It will be a while before we find a solution I think.

Thanks Terry

On Mon, 24 Jan 2022, 08:54 sk666, @.***> wrote:

Hi terry,

My trouble with surround began when I started to use DM 2.x version, with your fjrst version if I remember correctly.

I will happy to help you more with that but it can take a couple of days during each test because I'm starting to be a little bit busy for a couple of week. But I will do it when I will have the time for sure :)

Thank you

Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg

From: terrymacdonald @.> Sent: Sunday, January 23, 2022 2:47:10 PM To: terrymacdonald/DisplayMagician @.> Cc: sk666 @.>; Mention @.> Subject: Re: [terrymacdonald/DisplayMagician] Switching Nvidia Surround OFF doesn't work (Issue #76)

Ok cool! So we know that it is something in the way that the NVIDIALibrary interacts with the Mosaic functions that isn't quite right now. It was ok (because it was working), but now it isn't working.

The strange thing is that it is only affecting a small percentage of users. The majority are completely fine. This makes it difficult to troubleshoot, as we don't have enough samples to know where the problem may lie.

Do you remember exactly when you started having issues with DisplayMagician? If you can it might give us an idea when this started happening.

The next question is how do we troubleshoot what is broken? Well I think I have a strategy that will work, though it will take a bit of time.

I think we should cut out as much from the configurations as possible, and then see if the mosaic can be turned off and turned on. Then if that works we keep adding in sections of coffee until we find the one that is causing the issues. If I make up a sequence of versions of NVIDIAInfo with minimal config and then more config, then we will get more of an answer out of it.

@sk666 and @FormelLMS, are you both happy to try out some more tests when the code is ready?

Thanks Terry

On Mon, 24 Jan 2022, 01:51 FormelLMS, @.***> wrote:

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

— Reply to this email directly, view it on GitHub <

https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019478907

, or unsubscribe <

https://github.com/notifications/unsubscribe-auth/ABLU5LB72NVXSN6DL776GR3UXP2VFANCNFSM5LQYQTWA

. 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-1019554154 , or unsubscribe<

https://github.com/notifications/unsubscribe-auth/AG5ULZNZFGC4YJWBLXEEKCTUXRLL5ANCNFSM5LQYQTWA

. 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-1019555350 , or unsubscribe < https://github.com/notifications/unsubscribe-auth/ABLU5LDSWNQMOEKGCCENCUTUXRMI7ANCNFSM5LQYQTWA

. 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, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1019730480, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LFQWUHXRCQLXPAVHADUXTOIFANCNFSM5LQYQTWA . 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: @.***>

HS34 commented 2 years ago

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

Hi guys, Terry, congratulations for your amazing tool !

Unfortunately, in my case it doesn't work either in version 1.1.4. I've just checked it. I'm pretty sure it worked with version 1.1.4 sometimes ago, I think before I updated my windows 10 to version 21h2 (or maybe even before 21h1).

My NVidia Driver is still 452.06 and I will stick to it as long as I can because it's the last driver compatible with 3DVision in DX11. So my driver version has not changed for a long time. That's why I wonder if windows hasn't change something in updates.

I've got 4 screens connected on 2 TitanX (pascal) : 3x 3DVision Asus screens (for surround) + my TV (HDR enabled on the TV) When I enable or disable surround using nvidia control panel, my PC sometimes crashes, stucked with black screens. HeliosDisplayManagement and DisplayMagician worked far better (at least for a time). Congratulations again for doing better than the manufacturer !

Here is what I've checked :

Display Magician 1.1.4

created profile "3 screens only" created profile "4 screens" created profile "surround" Failed to apply profile "3 screens only" Failed to apply profile "4 screens"

I disabled surround in nvidia configuration panel and set "activate all screens" : the positions of my screens were not correct Success applying profile "3 screens only" : the positions of my screens are now OK Failed to apply profile "4 screens" Failed to apply profile "surround"

Display Magician 2.2.0.52

created profile "3 screens only" created profile "4 screens" Failed to apply profile "3 screens only"

created profile "surround" Failed to apply profile "3 screens only" Failed to apply profile "4 screens"

created profile "SLI optimise performances on 1 screen" Failed to apply profile "3 screens only" Failed to apply profile "4 screens" Failed to apply profile "surround"

I disabled SLI in nvidia configuration panel and set "activate all screens" : the positions of my screens were not correct Failed to apply profile "3 screens only" Success applying profile "4 screens" : the positions of my screens are now OK Failed to apply profile "surround"

Regards,

terrymacdonald commented 2 years ago

Hi @hs34

Could you please log this as a new issue? It sounds like it's a slightly different problem.

Please make sure that you try and make it fail, and then without closing DisplayMagician can you please ZIP up your C:\Users\\AppData\Local\DisplayMagician\ folder, and then upload it to the new issue that you create. That will give me some log entries to review, and will show me what could be wrong.

Please also tell me if you have tried v2.1.5 of DisplayMagician at all. If be very interested to see if you have the same problem with the v2.x series of DisplayMagician as you do with the V1.1.4.

It could a absolutely be a windows change affecting your system (and us too}, but it will be very difficult to know that. The fact that v1.1.4 works for @sk666 and @FormelLMS when the 2.x series doesn't shows me that there is something in the way the 2.x works that doesn't work. The fact that v1.1.4 does work for them means that it's likely a rare bug in my NVIDIALibrary custom video library.

Thanks Terry

On Tue, 25 Jan 2022, 07:35 HS34, @.***> wrote:

Hey Terry,

so I've installed the 1.1.4 again and I can submit, that it works with this version :)

Hi guys, Terry, congratulations for your amazing tool !

Unfortunately, in my case it doesn't work either in version 1.1.4. I've just checked it. I'm pretty sure it worked with version 1.1.4 sometimes ago, I think before I updated my windows 10 to version 21h2 (or maybe even before 21h1).

My NVidia Driver is still 452.06 and I will stick to it as long as I can because it's the last driver compatible with 3DVision in DX11. So my driver version has not changed for a long time. That's why I wonder if windows hasn't change something in updates.

I've got 4 screens connected on 2 TitanX (pascal) : 3x 3DVision Asus screens (for surround) + my TV (HDR enabled on the TV) When I enable or disable surround using nvidia control panel, my PC sometimes crashes, stucked with black screens. HeliosDisplayManagement and DisplayMagician worked far better (at least for a time). Congratulations again for doing better than the manufacturer !

Here is what I've checked :

Display Magician 1.1.4

created profile "3 screens only" created profile "4 screens" created profile "surround" Failed to apply profile "3 screens only" Failed to apply profile "4 screens"

I disabled surround in nvidia configuration panel and set "activate all screens" : the positions of my screens were not correct Success applying profile "3 screens only" : the positions of my screens are now OK Failed to apply profile "4 screens" Failed to apply profile "surround"

Display Magician 2.2.0.52

created profile "3 screens only" created profile "4 screens" Failed to apply profile "3 screens only"

created profile "surround" Failed to apply profile "3 screens only" Failed to apply profile "4 screens"

created profile "SLI optimise performances on 1 screen" Failed to apply profile "3 screens only" Failed to apply profile "4 screens" Failed to apply profile "surround"

I disabled SLI in nvidia configuration panel and set "activate all screens" : the positions of my screens were not correct Failed to apply profile "3 screens only" Success applying profile "4 screens" : the positions of my screens are now OK Failed to apply profile "surround"

Regards,

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1020417019, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LHZIWO3C3ROJL3L6DLUXWLYJANCNFSM5LQYQTWA . 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: @.***>

terrymacdonald commented 2 years ago

@sk666 @FormelLMS Can you please use this test version of NVIDIAInfo-v1.4.0-test1 to create a surround profile, and a non-surround profile, and try to change between them. NVIDIAInfo-v1.4.0-test1.zip

NOTE: This version of NVIDIAINfo will ONLY create a surround profile or turn it off. I've removed the other functionality to try and figure out what bits of code is causing the NVAPI_Mosaic_EnableTopo(0) error.

Then open a command line/powershell to that same folder and run through the following commands. Make sure you do every step in order, and record the results:

That's the regular config saved. Next we want to create a new surround config.

At this stage we have the two basic configs set. Next step is to see if it works changing between them:

Now, we try to swap back to Surround:

Next, create a zip archive containing the following files, and upload it here:

Hopefully that is all I need.

Thanks Terry

sk666 commented 2 years ago

Hi terry,

What DM version should ai use with these tests?

Thank you

Télécharger Outlook pour Androidhttps://aka.ms/AAb9ysg

From: terrymacdonald @.> Sent: Monday, January 24, 2022 4:17:24 PM To: terrymacdonald/DisplayMagician @.> Cc: sk666 @.>; Mention @.> Subject: Re: [terrymacdonald/DisplayMagician] Switching Nvidia Surround OFF doesn't work (Issue #76)

@sk666https://github.com/sk666 @FormelLMShttps://github.com/FormelLMS Can you please use this test version of NVIDIAInfo-v1.4.0-test1 to create a surround profile, and a non-surround profile, and try to change between them. NVIDIAInfo-v1.4.0-test1.ziphttps://github.com/terrymacdonald/DisplayMagician/files/7928916/NVIDIAInfo-v1.4.0-test1.zip

NOTE: This version of NVIDIAINfo will ONLY create a surround profile or turn it off. I've removed the other functionality to try and figure out what bits of code is causing the NVAPI_Mosaic_EnableTopo(0) error.

Then open a command line/powershell to that same folder and run through the following commands. Make sure you do every step in order, and record the results:

That's the regular config saved. Next we want to create a new surround config.

At this stage we have the two basic configs set. Next step is to see if it works changing between them:

Now, we try to swap back to Surround:

Next, create a zip archive containing the following files, and upload it here:

Hopefully that is all I need.

Thanks Terry

— Reply to this email directly, view it on GitHubhttps://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1020555356, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AG5ULZIDY3E6VRDEZ2RU3UDUXW6WJANCNFSM5LQYQTWA. 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: @.***>

terrymacdonald commented 2 years ago

Hi @sk666,

None. Please use the NVIDIAInfo-v1.4.0-test1.zip that I've added to that issue. We'll be testing with NVIDIAInfo for the next little while as NVIDIAInfo was designed for testing the NVIDIALIbrary, and that's what we need to do for the next little while. We need to avoid all the extra bits that DisplayMagician brings, and focus on fixing the underlying NVIDIALibrary problem, and that means using NVIDIAInfo.

Thanks

Terry

Message ID: @.*** com>

terrymacdonald commented 2 years ago

Ok Gents, some great news. I worked my way through NvAPIWrapper code based looking for things I didn't implement, or things I did wrong, and I think I found something! I have been using NvAPI_Mosaic_SetDisplayGrids, whereas NvAPIWrapper was using NvAPI_Mosaic_SetCurrentTopo.

This doesn't seem to be much difference in practice, but I wonder if using one over the other has some longer term side effects? I've just written some new code to try and implement these missing functions, and they don't work right now. I've got some more troubleshooting to do, and then some more internal testing to make sure it works on my test systems. At the moment the NvAPI_Mosaic_SetCurrentTopo returns a TOPO_NOT_POSSIBLE error, when I'd just set it up moments before. So once I get it working I'll get you both to test it.

I'm also going to check with NVIDIA which functions are the right ones to use. Just to be sure I'm doing it the right t way.

Thanks. Terry

FormelLMS commented 2 years ago

Yes, please don't forget me :) Yesterday I couldn't have a dive into it :)

terrymacdonald commented 2 years ago

Of course not @FormelLMS. This was a response message to @sk666.

I am definitely on a journey of discovery with this error. It looks now as though NVIDIA recommends setting the DisplayGrid Topology to a set of individual 1x1 display grid topologies to turn off Mosaic mode, so I am currently trying to figure out how to do that. I'm hopeful I will have a setup that will work within next week or so. I'll craft this into a new NVIDIAInfo, then you'll both get to test it to make sure it works. Once we've confirmed the display library works better, then we'll look at updating DisplayMagician.

Thanks Terry

Message ID: @.*** com>

terrymacdonald commented 2 years ago

OK @FormelLMS and @sk666, some amazingly great news! After a LOT of work I've finally cracked the problem of how to disable Mosaic/Surround without using disabling the NvAPI_Mosaic_EnableCurrentTopo. Turns out that with some clever processing I can convert the existing Mosaic grid topology to a series of single screen grid topologies using NvAPI_Mosaic_SetDisplayGrids, and the NVIDIA Driver will disable Mosaic/Surround!

I have also engineered it that if the NvAPI_Mosaic_SetDisplayGrids fails to work, it will revert to using NvAPI_Mosaic_EnableCurrentTopo instead. This now make the mosaic disabling much more robust 👍

So, can you please both download and extract the attached NVIDIAInfo v1.5.0, and then perform the following tests for me. Make sure you do every step in order, and record the results:

NVIDIAInfo-v1.5.0.zip

That's the regular config saved. Next we want to create a new surround config.

At this stage we have the two basic configs set. Next step is to see if changing between the display profiles works:

Now, we try to swap back to Surround:

At this point, our tests are done. Please create a zip archive containing the following files, and upload it here to this issue:

I'll go through the results, and lets see if the new code works!

Thanks Terry

FormelLMS commented 2 years ago

Terry, something strange happened...

Would do all the steps above. First step, the saving of the regular.cfg failed! In the zip file you can see the error message. Put the logfile in, too.

But: Display Magician is working now. I'm on 2.2.0.41 (dunno if it's latest, a bit confused now about that) I properly could change from Normal to surround and vice versa.

Thats very odd. But indeed I've changed something. Set some Custom DSR Resolutions into the Driver with the custom resolution tool (because I wanted to try to drive my Raceroom Racing without Surround.

Test.zip

Edit: Yes, switching DSR OFF and it didn't work again.

terrymacdonald commented 2 years ago

This is indeed good news! The fact you can swap between surround and non surround is great! I'll have a look to nail down the other parts.

This version of NVIDIAInfo also includes windows taskbar code, soon it's possible there are still a few errors there.

Can you please also try moving your taskbar to a new location (if you're on windows 10, I can't remember if you are), and then save a new cfg file? Then please swap between the two different display profiles and see if the taskbar moves places ok?

I really need to test that taskbar functionality on lots of people's computers to be sure it works. I'd hate to fix the display profile and introduce another bug at the same time!

Thanks Terry

On Sat, 29 Jan 2022, 07:22 FormelLMS, @.***> wrote:

Terry, something strange happened...

Would do all the steps above. First step, the saving of the regular.cfg failed! In the zip file you can see the error message. Put the logfile in, too.

But: Display Magician is working now. I'm on 2.2.0.41 (dunno if it's latest, a bit confused now about that) I properly could change from Normal to surround and vice versa.

Thats very odd. But indeed I've changed something. Set some Custom DSR Resolutions into the Driver with the custom resolution tool (because I wanted to try to drive my Raceroom Racing without Surround.

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1024491879, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LGTKEOWLL4K4MN3UOTUYLNFVANCNFSM5LQYQTWA . 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 commented 2 years ago

Hey Terry

have you seen my attached zip. As I’ve tried to say, with NVIDIA info I can’t do anything because saving the normal.cfg failed. I’ve attached the error message in a text file in the zip.

Switching back and forth does now work in display magician but only when I have a DSR profile enabled.

Sorry if I have not found the right words.

Am 28.01.2022 um 20:15 schrieb terrymacdonald @.***>:

 This is indeed good news! The fact you can swap between surround and non surround is great! I'll have a look to nail down the other parts.

This version of NVIDIAInfo also includes windows taskbar code, soon it's possible there are still a few errors there.

Can you please also try moving your taskbar to a new location (if you're on windows 10, I can't remember if you are), and then save a new cfg file? Then please swap between the two different display profiles and see if the taskbar moves places ok?

I really need to test that taskbar functionality on lots of people's computers to be sure it works. I'd hate to fix the display profile and introduce another bug at the same time!

Thanks Terry

On Sat, 29 Jan 2022, 07:22 FormelLMS, @.***> wrote:

Terry, something strange happened...

Would do all the steps above. First step, the saving of the regular.cfg failed! In the zip file you can see the error message. Put the logfile in, too.

But: Display Magician is working now. I'm on 2.2.0.41 (dunno if it's latest, a bit confused now about that) I properly could change from Normal to surround and vice versa.

Thats very odd. But indeed I've changed something. Set some Custom DSR Resolutions into the Driver with the custom resolution tool (because I wanted to try to drive my Raceroom Racing without Surround.

— Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/76#issuecomment-1024491879, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LGTKEOWLL4K4MN3UOTUYLNFVANCNFSM5LQYQTWA . 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, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.