[Feature Request] Disable Multiplane Overlay (MPO)

[pntn]

Inspired by horrendous 2 months of troubleshooting why my browser and everything changes colors when subject to anything such as a video on a Twitter or Facebook timeline or anything that uses the same codec(?), DDU reinstalls, cable switching, reformats, I would love to have that as a tickbox to disable that for myself and whoever else stumbles upon such or worse effects of MPO on RTX 3000 graphics cards.

https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/440865/mpo-multiplane-overlay-is-causing-graphical-corrup/

Solved flickering/glitching & artefacts on Windows 10/11 by disabling MPO. PSA
by u/Byakuraou in Windows10

W10 Hardware Acceleration flickering with RTX3080
by u/RaphBenben in Windows10

Stuttering and Input Latency - Nvidia Drivers may cause?
by u/LovelyResearcher in ValorantTechSupport

 

[W1zzard]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm]
"OverlayTestMode"=dword:00000005

in case anyone wonders

I can add this, good idea

 

[kDude]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm]
"OverlayTestMode"=dword:00000005

in case anyone wonders

I can add this, good idea

Do you know if you have to re-disable MPO if you DDU clean the gpu driver?
Using this https://nvidia.custhelp.com/app/answers/detail/a_id/5157/
Or does it persist trough multiple gpu driver installations?

MPO is currently enabled in my registry right?I don't see ""OverlayTestMode"=dword:00000005" in my registry.

 

[W1zzard]

MPO is currently enabled in my registry right?I don't see ""OverlayTestMode"=dword:00000005" in my registry.

Absence of that key = "enabled" I'd assume

Do you know if you have to re-disable MPO if you DDU clean the gpu driver?

Probably not, because it's in the Microsoft\Windows\Dwm key, which is a key owned by Microsoft's Desktop Window Manager, not by the graphics driver

 

[kDude]

Absence of that key = "enabled" I'd assume


Probably not, because it's in the Microsoft\Windows\Dwm key, which is a key owned by Microsoft's Desktop Window Manager, not by the graphics driver

Yea you're right I disabled it and the key appeared and I enabled it again and it dissapeared.

 

[wazer]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm]
"OverlayTestMode"=dword:00000005

in case anyone wonders

I can add this, good idea

Was this ever added? I'm using NVClean and have not seen this registry beeing applied.

 

[W1zzard]

This hasn't been added .. I forgot

Is this still useful today?

 

[wazer]

This hasn't been added .. I forgot

Is this still useful today?

Yes there's huge problems with it and is needed for both nvidia and amd cards a simply search for it via google and adding reddit seems to fix a lot of issues.

 

[thewan]

I feel like this should be somewhere else, not in nvcleaninstall, seeing that its a feature found on Windows itself that affects all GPUs, not just nvidia. Maybe some kind of hidden advanced mode in GPU-Z with a fixes section to fix simple common issues related to GPUs. Or a separate program. All GPU owners should be able to benefit from this, not just ppl who download nvcleaninstall because they have an nvidia GPU.

 

[wazer]

I feel like this should be somewhere else, not in nvcleaninstall, seeing that its a feature found on Windows itself that affects all GPUs, not just nvidia. Maybe some kind of hidden advanced mode in GPU-Z with a fixes section to fix simple common issues related to GPUs. Or a separate program. All GPU owners should be able to benefit from this, not just ppl who download nvcleaninstall because they have an nvidia GPU.

Add it both places, simple as that, no reason NOT to include it in nvclean.

 

[pntn]

If you ask me, I'd rather not have any benefits MPO provides (are there any?) and have my desktop work like it should and have been before this has been introduced, but since it's unlikely to go away now, I think adding it to nvcleanstall is first baby step, other programs might follow suit.

And yes, please add it, it's still causing problems. I was following Nvcleanstall releases and was disappointed this wasn't included in the latest one. Me and other would be ecstatic to see it in the upcoming release I bet.

 

[W1zzard]

This is included in today's NVCleanstall 1.15 release

 

[Dr. Dro]

Appreciate this being added, but as a reminder to anyone in the future being recommended to use NVCleanstall to disable this in order to fix something: it likely will not fix your problem and this setting should be used strictly for debugging purposes as multiplane overlay support is an extremely important part of modern Windows gaming experience, enabling independent flip in windowed mode and massively improving gaming latency and performance by allowing the graphics driver to bypass the DWM.

Disabling MPOs generally causes more issues than it solves, even in Nvidia's poor implementation (AMD MPO support is much better). It also requires Turing or newer, while AMD supports it as far back as Vega. If you're on Pascal or earlier, doing this will be a waste of time.

 

[AsRock]

Appreciate this being added, but as a reminder to anyone in the future being recommended to use NVCleanstall to disable this in order to fix something: it likely will not fix your problem and this setting should be used strictly for debugging purposes as multiplane overlay support is an extremely important part of modern Windows gaming experience, enabling independent flip in windowed mode and massively improving gaming latency and performance by allowing the graphics driver to bypass the DWM.

Disabling MPOs generally causes more issues than it solves, even in Nvidia's poor implementation (AMD MPO support is much better). It also requires Turing or newer, while AMD supports it as far back as Vega. If you're on Pascal or earlier, doing this will be a waste of time.

With AMD or nVidia, as i was getting issue's with it and been using this fix for a few weeks now.

 

[Dr. Dro]

With AMD or nVidia, as i was getting issue's with it and been using this fix for a few weeks now.

It's unfortunate you are having problems with it, MPO is a game changer... you can play windowed with absolutely no latency or desktop composition performance penalty. Without MPOs, you can only expect low-latency gaming by using borderless fullscreen and if any sort of overlay shows or loss of focus occurs, it will fallback to composed flip mode and it really hurts performance.

Shame it's just so buggy with NV in general (as the initial posts from 2021 show), and it has improved little since

 

[JackOO7]

I get this message after latest driver update with 1.15.

 

[Dr. Dro]

I get this message after latest driver update with 1.15.

View attachment 280690

Also occurs to me, 528.24 Studio / RTX 3050 mobile, did not touch the checkbox

 

[W1zzard]

Uploaded 1.15.1 to fix this issue: https://www.techpowerup.com/download/techpowerup-nvcleanstall/

 

[DamnSpyware]

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm]
"OverlayTestMode"=dword:00000005

in case anyone wonders

I can add this, good idea

Uploaded 1.15.1 to fix this issue: https://www.techpowerup.com/download/techpowerup-nvcleanstall/

I've just got the latest nvcleanstall version and found this new setting "disable multiplane overlay (MPO)"
So my question, is it generally recommended to check this box or only if issues appear?
From what i have read about MPO it can cause flickering and by disabling it responsiveness might sightly be increased, can you confirm that?
What are the benefits and downsides from this setting if any?

 

[W1zzard]

or only if issues appear?

Only if issues appear, and turn it back off if it makes no difference

 

[Dr. Dro]

Uploaded 1.15.1 to fix this issue: https://www.techpowerup.com/download/techpowerup-nvcleanstall/

Hey W1zz, busy night here (won't ping you again, sorry mate), this issue still occurs when running NVCleanstall 1.15.1 on Windows 7:

I did not tick the disable MPO checkbox, left it at default since Windows 7 does not support MPOs to begin with. It might be trying to write a value to the registry regardless, as it also throws this error afterwards

After this the app crashes, though at this point the driver (474.11 I mentioned on the other thread) is already installed correctly.

Thanks for the hard work

 

[W1zzard]

It might be trying to write a value to the registry regardless

Aha .. seems the problem is with Windows 7. Does Windows 7 even support that MPO key?

 

[Dr. Dro]

Aha .. seems the problem is with Windows 7. Does Windows 7 even support that MPO key?

AFAIK it shouldn't, the earliest implementation of MPO was in Windows 8.1 with WDDM 1.3 driver

 

[Fang]

The registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm" isn't present on my install of Windows 7 and instead I found it at "HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM"

This might be the cause of the registry key access error being thrown.

 

[Dr. Dro]

The registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm" isn't present on my install of Windows 7 and instead I found it at "HKEY_CURRENT_USER\Software\Microsoft\Windows\DWM"

This might be the cause of the registry key access error being thrown.

It shouldn't matter, really. the old WDDM 1.1 display driver model used on Windows 7 does not support MPOs. This feature was added in version 1.3 alongside Windows 8.1, and is only/can only ever be supported on this operating system or newer with WDDM 1.3 or 2.x drivers. The solution is to add an OS check and if it's Windows 7, then just gray out or hide the option and not write anything to the registry at all.