Scroll up, someone recently gave some really good detailed information on why this is happening. It’s not as simple as it seems and it could involve Blizzard, Microsoft, and Nvidia. given Devs are backed up from COVID this might be why its taking so long if its bouncing between 3 companies.
To new people on this thread… READ some of the recent posts, it will likely answer your questions about this issue.
Still a problem with 466.27 if anyone was wondering.
sadly yep, thx for checking it out. I mainly updated for upcoming Metro update 
There’s an update from 466.11 to 466.27 today. It did not solve my audio issues, after further investigation the issue is with Windows 10. Only Microsoft can fix it.
I do hope it helps with the flickering issue.
I’ve gotten tired of having to deal with this and no longer want to use the old graphics drivers. I finally just created an addon called Resetti so you can type /rlg and it will reset the graphics and temporarily fix the flickering issues for a little while. It only takes about a second for the graphics to reset and I’ll take it with the graphics performance increase of the new drivers.
I added in the ability to reset the audio too with /rla (because when I switch windows sources, wow doesn’t pick it up until I somehow reset the audio source).
i just have a macro for the gfx api reload
You don’t even need a macro. If you want to reset your video driver just hit the Windows Key+Ctrl+Shift+B
It’s super quick and easy to make a macro for it and it’s by far the quickest/easiest solution to the problem if you’re facing it. When you /console gxrestart it just reloads all the shaders and whatnot, which corrects the issue.
Using win+ctrl+shift+b is overkill and in some cases, can cause massive issues with multiple monitor setups. I’ve had it bug out and completely wipe my setup back to defaults for left/righthand locations(my mon1 is on the right and mon2 is on the left) and which is the primary. That shortcut should really only be used when you’ve got the black screen windows bug where the image won’t appear at all.
i had the flickering but the laptop has intel UHD graphics. turning Vertical Sync to disabled fixed for me…don’t know if it well help for some people
I’m using the latest driver 466.27 for my Nvidia Geforce 1650 and it’s still happening. I do believe it has something to do with the shadows on distant objects. Most notable on tree tops when flying from Stormwind to Duskwood. Was happening around mid-day into late afternoon. However now game time is 9:30pm and flickering is gone. So it’s something to do with daylight and shadows.
Jesus…it’s already May and it all started with that Cyberpunk driver from last year. And still they haven’t fixed this???
Im so over this to the point i wont quest in bastion and wont run spires.
Its a joke
I found that it helped for me at least to swap onto my graphics and then back to auto-detect. I have minimal flickering at this point instead of EVERYTHING flickering.
That’s the only recommendation I can offer. It lags me if I try to stay on my graphics card. The flickering gets worse if I lower my graphics.
Like I have stated many times in this thread, simply make a macro with /console gxrestart and drag it out onto a bar. Click it to fix the flickering and it only takes a couple seconds to reload.
All you’re doing when you switch the gpu setting to auto is it is literally running that command under the hood when you hit apply.
If you don’t want todeal with that simple fix, switch to DX11 and it will go away completely. You can stick with DX11 until Nvidia/Microsoft/Blizzard fix their issues with the drivers.
Are we going to get compensation for this? I don’t have a choice on using an old driver anymore as my work requires the current version. It’s utterly ridiculous at this point that it isn’t fixed.
Switching to DX11 lead to system reboots using the Venthyr mirror network. Not really worth it to get rid of the flickering. Going back to 6 month old drivers fix all the issues I had.
Whatever compensation you can wrangle from Nvidia. 
From whom? If you scroll up just a little you can see it’s a multi-faceted bug involving Blizzard, Microsoft, and Nvidia. Also I doubt there’s anything in either company’s EULA that would even give a crap about that. Also, before updating drivers, read the drivers patch notes. They’ll say if the issue still exists or if it’s been fixed. Most recent driver patch notes still say it’s an ongoing issue so no need to guess by installing. Stay on what you’re happiest with. Given NVidia has it filed as a bug in their own patch notes, seems like the issue is with them. Let us know how it goes getting your compensation from NVidia. I’m guessing the time investment wouldn’t be worth it.
Still a known issue in latest driver. Embarrassing is the only word to describe the fact that this is still an issue.
Yeah I just read the release notes and it’s still listed as a known issue. This is super annoying how long this has been going.