The new NVIDIA driver causes the engine interface to display abnormally

I used the driver from Nvidia last December last year. I started using the new driver a month ago. Since using the new driver, I have a chance to trigger a bug when using Unreal Engine. This bug caused many windows of the engine to open and disappear immediately, including some floating text. When using the blueprint, the full-screen blueprint window will cause the window to become completely black, and the node cannot be placed by the right mouse button (because the right-click window will disappear), and the drop-down menu cannot be opened.
In this month, I replaced the NVIDIA driver several times and found that the new driver would cause problems, but last year’s driver did not. I only found this bug in UE4, which makes many windows, drop-down menus, and text prompts disappear. I don’t know how I triggered this bug. Restarting UE4 will recover, but it may trigger again after a period of use. Computer configuration: I7 8700, rtx2060s ,win10 20H2 .Bug drive version 461.92 normal version 460.89

Aye, reported many, many times in the recent weeks. Or has it been months? Mostly new cards, GeForces 20xx and 30xx. There’s something in the newer drivers the engine feels uneasy about.

problem is from the driver itself, not your system

From poster shubyyy_yg:

Nvidia drivers from 461.09 onwards introduced a new feature called Multiplane Overlays, which apparently has some issues. The temporary solution for this is provided on this Nvidia page:

https://nvidia.custhelp.com/app/answers/detail/a_id/5157

Running the mpo_disable.reg file will disable multiplane overlays on your system, which seems to fix the numerous issues I have had with UE and Chrome. There’s also a mpo_restore.reg to re-enable the multiplane overlays later.

1 Like

Imagine not fixing it 2+ years

Even worse. Imagine them releasing a new driver yesterday, which reintroduced the issue even when using the old fix. Yeah, that just happened.

starfield drivers made this happen again for me in 5.3 :weary:

edit: It wasnt the drivers, it was me actually enabling MFAA on the NVIDIA control panel, if you come over here with this same issue, make sure you check if you have MFAA enabled! If so, disable it and retry

Nvidia is a meme at this point, imagine that you have to use 20 y.o control panel