my fps only went down 3 when i changed between the 2. i’m not advocating that dx11 is a solution, i’m just saying it stops the flickering. whats worse? potentially playing with less fps or constant texture flickering?
just switch for now and switch back later when its fixed.
You need to test it under more stressful cpu events. During those events DX12 will far outperform dx11 on 1%~.
It doesn’t though for WoW. I ran some tests with it a while ago in this thread and at no point did DX12 pull ahead of DX11 on average frame times. Went to an area with a bunch of draw calls, overdraw and CPU particles. I run in the 100-150 FPS range and this specific spot could drop my frame rate down to like 20-30, so it’s as close to a benchmark as I could get.
The latest drivers put DX12 to just below DX11, but that’s where whatever hacky stuff they did causes the flickerings and such.
What hardware are you running? Most the people that are seeing performance issues with DX11 are running higher end hardware. So if you’re on a 10xx card with a i5 or older i7 it may be less noticeable than say if you’re on a i9 10900k with a 20xx or a 30xx.
I fall in to the higher end category and I see performance degradation when I have used DX11. There are a lot of variables to this issue but they all revolve around some sort of issue with Nvidia’s drivers.
I’m on a 1650 OC and a 10100 i3. Same turing architecture as the 20XX series minus the raytracing cores.
All DX12 mostly does is help speed up the batching of draw calls on the CPU by allowing them to be prepared using multithreading. It’s actually a pretty small portion of what goes into rendering a frame. If anything, you’d see more benefit on lower end rigs that struggle to push the 60-90fps(10-20ms range) range vs the overpowered rigs that can push 200fps(5ms range) with the same settings. Frame time variance in the 1-5ms range is barely perceptible so long as it’s not happening for dozens of frames in a row.
You probably have something going on with other drivers and also WoW’s DX11 won’t go full screen exclusive(changing the “disable fullscreen optimizations” will do zero for it).
Since you’re on a higher end rig, I’m going to assume you’ve got a g/freesync monitor. Check your nvidia control panel settings for gsync, if you use it, and make sure it’s set to fullscreen AND borderless windowed. Then make sure to turn on vsync from the NVCP for WoW.exe. Not going to go into all the details and specifics, but it works well with gsync/freesync and doesn’t do the normal input lag that you’d get with non-g/freesync+vsync on. You could always throw low latency mode to on or ultra as well, but you shouldn’t need it if you’re already in the 100+ fps range.
I also know there was some recent windows update that was also giving people a lot of issues with game performance. Might look into that as well.
Not sure what to say mate, but my 3080 and previously 1080ti gained major value from DX12, especially the .1%/1%.
All we know is,
46X onwards, drivers with the previous DX12 optimizations cause flickering.
For now Raiding/M+ hasn’t caused major impact for me. HoA is the only dungeon where i have to turn off shadows to blob.
EDIT: False alarm, I had on the target FPS option, so it was dropping quality on things to meet frame rate.
What I am getting at is for me personally, someone with a significant amount of disposable income, it seems that Nvidia has really been working very hard in the past 12 months or so to make sure I never want to buy anything from them again.
We’re not talking about an indie game that has 25K players here, we’re talking about the most successful MMO in the history of MMOs, one that just released an expansion at the end of last year and a bug that substantially diminishes the experience of the newest content for a large amount of players.
Whatever the issue and whoever needs to be involved in fixing it, it needs to be resolved. 5 months is not a reasonable service level for this. If it took me 5 months to fix a bug that affects this many people to this degree I would be tossed out on my Sylvan-a$$.
If it’s on, I turn it off, let the screen do it’s flash, and then turn it back on again. Mostly just letting the video reset it self by changing the setting. I also noticed I seem to get less if the Particle Density is set to Good rather than High/Ultra. Again, the worst is Ardenweld 
Idk if someone posted this earlier, I don’t have time to go through 700 posts, but I fixed this by either limiting my frame rate to 60 fps or changing the graphics card option in the advanced section of the system menu to my actual graphics card instead of auto detect.
That’s a different issue.
This one affects only Nvidia GPU users and has nothing to do with the GPU selector, since it affects computers with only one GPU.
After doing a ton of research on this topic and the pixelation issue, I think the root culprit of it all is the multiplane overlay system in Windows. It’s supposed to be a big increase in DX12 performance and Nvidia enabled it in their drivers in the 46X.XX series of drivers apparently. This is likely why the DX12 performance was much better in these drivers, but at the cost of having flickering issues. MPO has been around since Windows 8, but wasn’t really used until recently.
I didn’t read too much into the actual system, but apparently it has to do with things of different render scales being composited in the DWM and it seems like something might be going wrong in there.
I found out about it all because I work with UE4 a lot and was having issues with right click menus disappearing and the UI flickering sometimes. I’ve noticed Chrome does it too sometimes. Did some digging through other devs talking about the problem and they found it was mostly related to MPO. Oh and the regedit tweak floating around won’t fix the Nvidia driver level problem that’s causing it.
Definitely a case of Nvidia and Microsoft having to hammer this out, that’s why this is taking so long to fix.
If I had to guess, it might be the case that Nvidia is having much lower productivity fixing issues due to WFH. Fancy testing setups often require some degree of physical babysitting. Collaboration is also really helpful for fixing bugs, and on my (not Nvidia) software team collaboration is a lot more difficult to do remotely.
This has also been suspected for Blizzard’s software team addressing the large backlog of bugs in WoW. And if this driver bug requires collaboration between Nvidia, Blizzard, and Microsoft, it’s no wonder it hasn’t been fixed yet.
Can’t believe this is still here like half a year later. Figured I’d update my drivers given how long it’s been because “There’s no way that stupid flickering bug still exists right?”
LOL Think again.
466.27 released today and still no fix 
Came across this issue 2 months ago and still no fix, I had to revert my drivers back to 457.71, I thought SURELY there would be a fix by now and tried to update my drivers, nope. Man I am glad I don’t play any other games right now because I can’t even update my drivers.
Is it still in the notes as a known issue? I can’t believe it’s going on half a year and this is still an issue.
Yep, the reason why I’m still on 457.30
I don’t know anything about computers so it’s really weird to me that what seems to be such a relatively minor issue (compared to all the extraordinary things that GPU’s do nowadays) is apparently so difficult to fix.
Anyone who knows what they’re talking about have an idea what might make this so hard to fix?