Getting graphics glitch since the last patch 11.1.7 came out

A graphics engine restart and a full system crash are not the same thing.

It is still happening for me (July 20). Also 2 other bugs. One is when using the public taxi through the Coreway, the bird (sometimes) stops and perches with it’s wings folded in mid air, 1/2 way along. The 2nd is (sometimes) when I try to zone into or out of a delve, nothing happens and I am stuck with the grey entry shimmer at both ends of the tunnel. Hearthing, /reload, reloading the game and mage port doesn’t help. The only way to ‘unstuck’ my toon is to totally restart my PC. Then it is working again.

1 Like

Use the scan and repair tool. I was having this issue as well, but this seemed to fix it.

1 Like

Yeah anything that causes a re-render of character models can do it. Transmog & collection are just the easiest game features to access that require re-renders.

Best suggestions I can give:

  • Check graphics settings and make sure your actual correct graphics card is selected and not set to “Auto detect”. For some reason the 11.0.7 patch added options for it to potentially use on-board graphics on the motherboard instead of the actual installed GPU (probably the biggest culprit I’ve seen)
  • Make sure your graphics driver is updated
  • Switch Graphics API to DirectX 11 instead of auto or DirectX 12
  • Do a scan & Repair on WoW

If those don’t work, Then from top to bottom of the graphics options:

  • Disable VSync
  • Try different Anti-Aliasing options
  • Try different Resample Quality settings
  • Disable Optional GPU Features
  • Disable Multithread Rendering
  • Disable Advanced Work Submit

Might want to mix & match various setting configs to see if you can find a sweet spot setup that stops the crashes. I ended up having to do pretty much all of them before it stabilized for me.

Beyond that, probably not a lot that can be done from our end until Blizz and/or NVidia figure something out and take actual action on the problem.

1 Like

I get the graphics restart like everyone else does too. But in my case it continues on with a crash.

The last patch introduced a large number of crashing bugs which all appear to be related to the graphics engine. They just have worse outcomes on some system configurations than on others.

2 Likes

It appears this graphics glitch that Bliz introduced this past week also tends to freeze the game when trying to log out. Getting tired of using my control panel just to kill the game because it’s frozen preventing a regular log out.

Geesh Bliz, you need to fix your messes.

1 Like

along with the graphic glitches described in this thread, I also have an issue with zoning. like. … clicking on a portal, or hearthstone, just nothing happens. I also realized it wasn’t applying my talent tree in overcharged delves. i.e. the electrical puddles were rooting me. I thought it was just my computer at first, but then it happened to my partner too.

Well I got this response from a tech mvp:

"You wouldn’t see anything except new threads about the issue in both the tech support and bug report forums if it were “extremely common.”

Since switching to DX11 (GPU-based issue) or force-updating Windows (OS-based issue) fixed it for many people, it’s difficult to make a case against Blizz on this one. That’s probably why we haven’t seen anything from them about it. :dracthyr_shrug:"

So probably we’ll have to see how to fix this for ourselves because no one seems to give a (rude word).

1 Like

I don’t know why Blizzard is ignoring this issue. I’ve sent multiple reports to them but not a single response. I’ve tried tinkering with graphics settings, reinstalling the game… literally nothing works and it keep happening. Even on lowest graphics settings it happens. I am getting extremely annoyed with this and them.

1 Like

World eating delve bug is a separate issue and fixed by not running 3d bio printer.

1 Like

After reading all your suggestions, I found for me ‘Scan & Repair’ did not help, BUT reverting to DirectX 11 fixed the problem. Thanks for the suggestion.

The problem with that is that Bioprints are far and above the literal best option for tanks and any Agi/Str class because they scale with Attackpower. None of the other damage curios in that row are even contenders by comparison of damage done.

I have seen the only actual requirement is that you dismiss your bioprints before trying to leave the delve. (They’re two buffs in your buff pile that can be individually dismissed.)

If all else fails, you can change your utility curio to something harmless just before leaving and remember to change it back when you start your next delve.

1 Like

This worked thanks

Still happening

Same issue here. Nvidia 1660 super. Every time i try to transmog my graphics reset. Very annoying. havnt been able to transmog for 3 weeks. it sometimes happens without transmogging too.

2 Likes

Same here. Thankful to see im not the only one. All my drivers are updated and I even reinstalled the game. Any fixes?

1 Like

Nothing reliably consistent sadly. I’ve mentioned these before but Best advice if you’ve already updated your video drivers:

  1. Confirm the graphics settings are set to use your actual video card instead of “Auto detect” or the onboard video of the motherboard. WoW apparently has the option to see both now (added in 11.1.7) and might default to the onboard instead of the actual video card.
  2. Switch Graphics API to DirectX 11 instead of auto or DirectX 12
  3. Do a scan & Repair on WoW

If those don’t work, Then from top to bottom of the graphics options window:

  • Change or Disable VSync settings
  • Try different Anti-Aliasing options
  • Try different Resample Quality settings
  • Disable Optional GPU Features
  • Disable Multithread Rendering
  • Disable Advanced Work Submit

I’ve seen some folks have success with the very first step, and some (like me) who had to do all of them in combination before the problem stopped. Good luck

STILL HAPPENS IN 11.2 I AM UNSUBBING I WON’T PLAY THIS GAME WITHOUT TRANSMOG FOR ANOTHER ENTIRE PATCH LIKE 11.1.7 was…

I was able to fix the issue by changing graphics api to directx 11 instead of autodetect. The bug did not hit me until 11.2 though.

3 Likes