btarunr

• [World of Warcraft: Shadowlands]: Random flicker may occur in certain locations in the game [3206341]

God this has been a thing since Shadowlands released. Why is this not fixed yet!?

and STILL no fixes for the sezure-inducing flickering in World of Warcraft...

COME OOOOOOOOOOOONNNNN...

CrAsHnBuRnXpGod this has been a thing since Shadowlands released. Why is this not fixed yet!?

I'd expect this level of neglect from AMD in the past, but effing hell nvidia...

CrAsHnBuRnXpGod this has been a thing since Shadowlands released. Why is this not fixed yet!?

Disabling MSAA fixes it.

Someone else can test these with a 1080 Ti, I'm too lazy to test every driver version. :laugh:

VR issue still not fixed. I'm gonna bang my head against a wall.

CrAsHnBuRnXpGod this has been a thing since Shadowlands released. Why is this not fixed yet!?

I have no issue on my 6800 gpu. lol hard to believe such an old game still has issues

m2geekand STILL no fixes for the sezure-inducing flickering in World of Warcraft...

COME OOOOOOOOOOOONNNNN...


I'd expect this level of neglect from AMD in the past, but effing hell nvidia...

*licks my 6800 gpu* i play shadowlands every night, its yummy and flicker free!

Chloe PriceSomeone else can test these with a 1080 Ti, I'm too lazy to test every driver version. :laugh:

I will but I'm too lazy to post a review on it xD
I'm just curious about :

Some displays may show incorrect color levels after booting into Windows. [3285148/3287063]

If it does weird stuff I will post again, if I remain silent it would mean it's fine.

AlexaVR issue still not fixed. I'm gonna bang my head against a wall.

May I ask what the issue is? Just curious as I am not a VR user.

R-T-BMay I ask what the issue is? Just curious as I am not a VR user.

Nauseating micro-stutter and hiccups on VR. I never experience it in my 2070 Super. To add, I can use 6 ft DP extensions and USB on my 2070S but they don't work on my 3080.

Weird. That sucks, hope they resolve it faster than it took for my last issue to be resolved! (nearly 7 months)

lynx29I have no issue on my 6800 gpu. lol hard to believe such an old game still has issues

That statement proves you havent played it in a while.

CrAsHnBuRnXpThat statement proves you havent played it in a while.

lol sure thing. my ilev 213 dps monk disagrees with you, but mmk

What VR issue? Complete fine on my 3090

lynx29I have no issue on my 6800 gpu. lol hard to believe such an old game still has issues

The game is constantly updated, last expansion came out half a year ago. No reason to be surprised something might not work.

lynx29lol sure thing. my ilev 213 dps monk disagrees with you, but mmk

Its funny that you think just because it's an old game that it isnt susceptible to bugs and glitches. When it's actually on nvidia and not blizzard.

birdieDisabling MSAA fixes it.

No it doesn't. But disabling Raytracing shadows fixes it. At least for me here. Nvidia 3090. Tested in Bastion.
Nevertheless, the driver doesn't do anything in this regard.

CrAsHnBuRnXpGod this has been a thing since Shadowlands released. Why is this not fixed yet!?

Indeed, but there is a profile fix for it. I've been using it for months now, with no issues.

Save the following as a .nip file and load it into Nvidia Profile Inspector, or check the attached .zip.

<?xml version="1.0" encoding="utf-16"?>
<ArrayOfProfile>
<Profile>
<ProfileName>World Of Warcraft - Retail</ProfileName>
<Executeables>
<string>_retail_/wow.exe</string>
<string>_retail_/wowt.exe</string>
<string>_retail_/wow-64.exe</string>
<string>_retail_/wow64.exe</string>
<string>_retail_/wowb-64.exe</string>
<string>_retail_/wowb.exe</string>
</Executeables>
<Settings>
<ProfileSetting>
<SettingID>7168407</SettingID>
<SettingValue>2729785185</SettingValue>
</ProfileSetting>
</Settings>
</Profile>
</ArrayOfProfile>

Source: nvidia/comments/kqldhb/blizzard_has_reproduced_the_texture_flickering/giinq84/

lynx29lol sure thing. my ilev 213 dps monk disagrees with you, but mmk

To me, Warcraft died along with the Lich King.

i use clean edition drivers because i don't want any nvidia crap and we obviously all know how bloated official drivers can be

Vendori use clean edition drivers because i don't want any nvidia crap and we obviously all know how bloated official drivers can be

NVcleanstall is a godsend.

Chloe PriceSomeone else can test these with a 1080 Ti, I'm too lazy to test every driver version. :laugh:

@qubit is our resident “throw all caution to the wind” driver tester. :laugh:

rtwjunkie@qubit is our resident “throw all caution to the wind” driver tester. :laugh:

Yup, I install the latest driver the minute it comes out and I haven’t come unstuck yet lol.
Mind you, I don’t play games all that often, so that probably helps.

qubitYup, I install the latest driver the minute it comes out and I haven’t come unstuck yet lol.
Mind you, I don’t play games all that often, so that probably helps.

Play something, our guinea pig :laugh:

VannyTo me, Warcraft died along with the Lich King.

good for you

CrAsHnBuRnXpIts funny that you think just because it's an old game that it isnt susceptible to bugs and glitches. When it's actually on nvidia and not blizzard.

AMD managed to make it work just fine, /shrug

Chloe PriceSomeone else can test these with a 1080 Ti, I'm too lazy to test every driver version. :laugh:

I did. I haven't seen anything wrong about 466.11 yet, other than a very few crashes with Cyberpunk 2077 (v1.21 Hotfix), but that was something I expected.

My result with 466.11 after 2 days:

- Fixed raw images showing up as black (blank?) images in Bridge and Lightroom for me. Not Adobe's fault. This issue was from the Re-Bar driver (465.89), which I uninstalled immediately. I have no idea when this issue started or from which driver or branch, but 441.66 and 456.71 (Studio driver) didn't have it.
- Cyberpunk 2077 ran fine, but with a very few crashes. Something I always expected from Cyberpunk 2077. Probably memory leak like some people reported in CDPR forums, Steam forums and Reddit, because the crashes seemed related to opening map or trying to hack objects (cameras, turrets, etc.). Free roaming and other things didn't crash the game.
- Didn't have problem running and playing Nioh 2, and so did 441.66 and 456.71.
- This is not a studio driver, but I didn't have problem with Photoshop at all. Re-Bar driver sometimes caused Photoshop not detecting and using my GPU. Restarting Photoshop fixed it.
- Yakuza 6 crashed a lot, but I'm sure it didn't have nothing to do with the new driver. QLOC being the studio porting the game does have something to do with the game's problems (SEGA, please stop using them!).
- Didn't have problem with Firefox (browsing, watching videos, etc.). I don't have Chrome and would rather not have one so I couldn't test the driver with it. Didn't test the driver with Edge either.

I came a long way from 441.66 and 456.71. From what I read, many other Pascal users have been using 456.71 too although they're using the Game-Ready driver, not the studio one I had. But I'm confident to replace my 441.66 and 456.71 with this driver. Hopefully nothing will go wrong or bad in many days to come. Seems a very good and stable driver for me, but keep in mind that I don't play games a lot and often (always have a lot of projects to work in) so I have no idea if this driver works great with many games.

Your result may be different from mine. I say it doesn't hurt to try. You can always go back to 456.71 or whatever driver works for you if 466.11 gives you problem.

rtwjunkie@qubit is our resident “throw all caution to the wind” driver tester. :laugh:

I always have a feeling of admiration towards those who always take one for the team.