Makes ya wonder how closely the framerate optimizations are related to the scene flicker.
I’ve noticed it’s also tied to the pixelated particle/refraction bug as well because when I apply the profile fix or use older drivers, that bug goes away as well. Seems like some weird optimization where it renders at a lower mip level and then upscales, but it forgets to use an upscale filter like bicubic to smooth it back out. So instead, you end up with minecraft particle effects and water refraction.
If I had to take an educated guess, the black flickering is related to this as well. There’s an issue in the game content creation world with UVs and textures where you need edge padding. This prevents issues when the game shifts levels of detail in models/textures.
If they are doing some kind of upscaling trickery, this could explain some of it.
There’s a fine line between “optimization” and “quick and dirty shortcut”. I sense the 46x.xx drivers are on the far side of the line.
Yep. Main advantages of DX12 comes on the min fps.
SIde note what’s your GPU O.o…cinemetic fps :D?
For not its worth taking the slight flickering here and there for the added benefit of fps.
That’s how it always works though. Driver companies make a new major driver revision that handles new architectures and gpus, then they make minor patches that change some flags on a per game basis. Those minor patches are usually exactly that: quick and dirty shortcuts.
Oh it’s only a 1650. It does great on 8-10 settings 1080p 60fps. Like I said, normally my frame rate is locked 60, but runs in the 80-100fps range. That spot I picked crushes frame rates though. If you had some 2080 or 3080, it would drop your frame rate to a 1/3 of what it normally is too. Might mean 60fps instead of 180 though in those cases though.
It’s ok…when raid timer hits 0 and we pull the boss…fps is cinematic :D…eg Sire lol
I do hope they fix this soon, i tested out the profile / on and off as well, the downgrade to min/.1% is pretty substantial.
It is basically DX11 vs DX12.
I don’t want to switch back to DX11 and the work arounds only seem like to help temporarily 
Try using direct X 11 instead of 12. That helped my flickering issue.
DX 12 looks and runs a lot better than DX 11 especially on the 20 & 30 series cards so it makes no sense to use DX 11 or disable DX 12 optimizations. Therefore, using an older driver is the only sensible solution albeit not an ideal one.
DX11 is visually identical to DX12 unless you’re using ray-tracing. In many situations with an NVidia card it can even run as well or better due to the amount of time NVidia has spent optimising their drivers prior to any CtM APIs becoming available.
There’s a post about 10 back from yours where someone has tested it and found an increase in framerates using DX11, particularly when the driver hack that causes the flickering is disabled. Granted that’s only one system, one user, and one test environment, it’s still worth considering if you don’t use DXRT.
You might have misread it. DX12 offered higher, also in s game like this, you can gain a lot on the .1%
No, I’m pretty sure I got it. Perhaps the 99th percentile is better (debatable) but overall it’s still trending worse, at least for that particular user under those particular conditions (WoW isn’t exactly an easily repeatable test). Unless 24 is now greater than 34, and both 25 and 33 are greater than 35…
I do know that AMD cards fare better with CtM APIs than NVidia ones do, but they also aren’t having this particular rendering issue so their results are moot to this conversation.
Just a tip for those also plagued by this issue: I have found changing to Video Card option from either auto or selecting it specifically fixes temporarily the glitching, almost like resetting the issue, comes back but at least fixes it for a while
By the way those saying to use older November drivers: can’t here as I am on a 3080 new laptop with no drivers before January. Also, DX11 runs horribly on 30 series
Could be his old GPU not really benefiting much. On my 3080, when DX12 was implemented with the latest drivers, min fps in Boralus went up 20-25fps~, a perfect spot is overlooking from city into the water. There is a video of a guy doing some shadowlands benchmarks on Ardent/Bastion/BFA confirming the .1%/1% Improvements (Almost doubling 30->60~)
1 Like
Your results are the same as mine on a 2080Ti. DX12 also allowed WoW to use multi-core and since its so CPU bound really helped with performance. DX11 is a huge step back unless you’re running on not so modern gear imo. I’m on a i9-10900k and a 2080Ti, there is a noticeable performance hit using DX11.
The same can be done by using a macro with /console gxrestart
You’re just forcing the shaders to reload when you change that video setting.
It doesn’t work like you think. All the DX12 multithreading helps with is when the CPU has to prepare the draw calls for the GPU, which is only a portion of rendering a frame. Also, I don’t think WoW is really a game where there’s 5-10k draw calls on screen at once. They tend to do a lot of instancing and batching when they can, from what I can tell.
Well all I can say is that on my 3080 i7 10th gen laptop, DX11 was not playable for me in 4k… dungeons in particular, was averaging like 30 FPS… DX12 on and I am back at 80+
And awesome thank you will use this
That has to do with DX11 and fullscreen optimization issues. Good example: You can’t use things like the nvidia control panel vsync options on WoW because it’s not fullscreen exclusive. When you switch the API to DX12, it can do those things again (I know this because I use adaptive vsync in the control panel).
New 466.11 drivers out. Still marked as a known issue
2 Likes