Again i went in there 200%/8xAA, zero issues. Main difference was i went from 1903 to 20H1/466.27
Also don’t forget, i had the issues regardless of the higher fps btw, it was very easy to replicate around ardentworld.
Hmmm, maybe something changed between 20H1 and 20H2(I’m on 20H2). While I’m definitely not going to roll back to H1, I did some digging through patch notes and the closest suspect I could find was:
“We fixed a window rendering issue that causes content in a window to flash frequently when multi-plane overlay (MPO) is used.”
https://blogs.windows.com/windows-insider/2021/03/25/releasing-windows-10-build-19042-906-20h2-to-release-preview-channel/
So maybe Nvidia had some fix during H1 to counter issues, but then MS fixed their issue and it made Nvidia’s fix now act up? The 46X.XX drivers enabled MPO support. That’s why I’ve brought it up multiple times that this is likely an MPO+DWM compositor issue and that Nvidia will either have to refactor around or we’ll have to wait for Microsoft to fix the issue on their end, which you know how MS is about fixing things in a timely fashion…
Has anyone tried the 466.55 hotfix drivers? It’s not one of the things that it’s lists it fixes… but I’m just wondering if anyone has tried it. It does seem like we’re finally getting a little closer to a fix… I hope.
GeForce Hotfix Driver Version 466.55 | NVIDIA (custhelp.com)
Couldn’t take having my entire system gimped by 6 month old drivers any longer, so installed the latest ones last night. DOES NOT fix the flickering issue & even has the Warcraft problem listed in their known issues, but HEY CoD Warzone looking CRISP & running SMOOTH. #DoneWaiting
So, I just installed this hotfix but also ran the repair function on BattleNet launcher and cleared my game cache for good measure. Some combination of these DID fix the issue for me. For reference I only began having these issues in the past couple of weeks but it did work for me.
mine was the 20h1+shader cache cleanup.
however rivendreth still has that black screen as you fly in.
C:\ProgramData\NVIDIA Corporation\NV_Cache is the only directory that WoW writes shaders to. You can verify this using Procexp64 and watch the drive activity while wow.exe is selected. You can also disable shader caching for WoW and verify that none are being created within that folder, and still get the flickering.
Set shader cache to off for WoW: https://imgur.com/0jaq7e6
Verifying before and after Launching WoW that the NV_Cache folder is empty, to ensure the setting works(normally that would populate with items if caching was enabled): https://imgur.com/gy9aJHJ
Settings on 10+8xMSAA: https://imgur.com/6bZGHp0
The flickering frames still present: https://imgur.com/viZaM0k
Windows 10 21H1 now with 466.47 drivers. It’s not a shader cache issue, so don’t waste your time like I just did.
well i haven’t gone back to BFA since shadowlands…so can’t comment if that has been resolved there…however currently for me in shadowlands content i seem to be solid. will report back later if i notice flickering.
Oh it can happen in any zone in the game. It’s not SL exclusive. I’ve seen it happen in Org even. I just know I can reliably trigger it in that spot of BFA, so that’s why I tend to do it from there.
I actually get it with 2xMSAA as well. I typically run 2xMSAA and CMAA together at 3440x1440.
Yep, i had it at 2xMSAA as well, pushing to 150% or 200% also easily triggered it. For some reason it just suddenly stopped.
Only changes i had was the 1903 → 20H1, and nvidia driver 466.27. (This is not the current latest one). I only updated to 466.27 because it had metro updates for RTX requirements. Also another reason why i updated Windows from 1903.
This issue is still present. I cannot play with DX12. When is this going to get fixed? I understand that it’s an nvidia issue but we would love a response from Blizzard, an update…anything?
Based on comments in an Nvidia thread that I don’t remember if it was linked here or somewhere else, it sounds like they’ve fixed it and the next major driver release “should” have it once testing is finished. They seem to be putting a driver out about every two weeks recently so hopefully “soon”.
This is the best news I’ve heard all day! I hope they come through!
Same, the info was from an Nvidia rep, I forgot to mention that.
there might be some new drivers today as the 3080ti is scheduled for release today. (Though i have no idea why anyone would by rip off product lol. Compared to 3080 it is 5% faster, but almost 70% increased MSRP cost…)
1 Like
There was a new driver released today and the wow flicker is still an open issue listed.
Was pretty sure that would be the case. I know Artad mentioned something about an Nvidia rep talking about a fix, but I couldn’t find any shred of it. Maybe I just wasn’t using the search functions and Google correctly.
The NVidia rep (Manuel G, basically NVidia’s “face” on the GeForce forums) mentioned the fix would be in the next driver branch, not the next driver release. These new drivers are still on the 465 branch, per the opening line of the release notes.
Source:
https://www.nvidia.com/en-us/geforce/forums/user/15/453674//?comment=3076314
Manuel@NVIDIA
We have a fix in our next driver branch that addresses one of the issues that would result in random flicker. We are also working with Blizzard to solve other reports of flicker in the game.
(You’re gonna have to trust me on that link. I guess NVidia has some weird metadata stuff that Blizzard’s forums don’t like)
I suspect the next branch will be 470; though I’ve no idea when exactly that will be released, or even approximately. This is the same branch which is moving Kepler to Legacy so if you’re running a 600- or 700-series (save the 750 and 750Ti, which are Maxwell) you’ll either have to roll back to 457, switch to DX11, add the DX12 flag, or persist with temporary might-fixes like GXRestart - there won’t be a fixed driver for those.
2 Likes
So annoying! I think I’ll just update, then switch to DX11 :(. I’m having other issues in other games because I’ve been holding my drivers back.