I’m not entirely sure what settings cause it but I know changing the overall quality setting (slider with values ranging from 1 to 10) causes the game to freeze and so does toggling the Reduce Lag option (freezes right when I click Apply).
Adjusting the Texture Resolution setting doesn’t cause the freeze.
After forcing the game closed and then re-opening the game the setting changes were seemingly successfully saved even though I only attempted to Apply the changes and never hit Okay.
Windows 10 x64 v1809 (17763.288)
Intel i7 920 CPU (D0 Stepping)
24GB RAM
Geforce 1070Ti (416.81 driver)
ASUS P6T Motherboard
DirectX 12
change to DX 11 and see if the issue is resolved
1 Like
Yes that fixes the issue, I’d of course like to use DirectX 12 though. As far as I can tell the freeze when messing with the options in DirectX 12 is the only issue with DirectX 12, when actually playing the game there is no issue.
I have a feeling the issue dates back to when DirectX 12 was first introduced to WoW outside of the PTR (I never played the PTR), I just never reported it because afaik the new forums at the time didn’t have any section that allowed expired accounts to make posts.
I personally have only seen it on older CPU’s not sure why. AMD FX CPUs and the very old intel I-5 and I-7’s
1 Like
Yep this happening to me aswell…
i7-8950h CPU, nvidia 1070 max-q
Any updates on this. It’s really annoying as I change my graphics settings often depending on content/laptop load etc.
I’ve narrowed the problem down to the Steam Overlay/launching the game via Steam.
While in DirectX 12 mode I’ve performed the following 4 tests:
With the Steam Overlay disabled I was able to launch the game 2 separate times from the desktop and succesfully apply changes to the Quality slider in the graphics settings each time.
With the Steam Overlay active/launching the game via Steam the game froze during each attempt at applying changes to the Quality slider.
Steam shortcut: "F:\Battle.net\Battle.netLauncher.exe"
Updated my post to be a little clearer regarding my testing and also mentioned what path I set Steam to use when I try to play the game via Steam (within Steam you can create “non-Steam shortcuts” to programs to access the Overlay in programs not purchased via Steam).
I had this problem, discovered similar problem/fix. FX 6300 here, I recently discovered this issue too after doing some upgrades/Overclocking and adjusting my settings. The OP said they were using the Steam overlay, however I was using Riva overlay with MSI Afterburner to show my own overlay settings.
I fully closed and disabled Riva temporarily and set game overlay detection to off. Went back to WoW adjusted graphic settings with 0 errors. Tried slider, shadows, etc. The Riva Overlay was only causing this problem on DX12 for me.
1 Like
The issue appears to be fixed in regards to launching the game via Steam. Now when you adjust the Quality slider and click Apply the game application will reset the graphics renderer and everything will continue/function like normal.
Btw I’m NicSteel/Cedrek
Edit:
However if I adjust the Quality Slider multiple times I get this interesting error…
\---------------------------
WoW
\---------------------------
This application has encountered a critical error:
ERROR #132 (0x85100084) Fatal exception!
Program: F:\World of Warcraft_retail_\WoW.exe
ProcessID: 11948
Exception: ACCESS_VIOLATION
The instruction at “0x00007ffcf2aec4a0” referenced memory at “0xffffffffffffffff”.
The memory could not be “read”.
Press OK to terminate the application.
---------------------------
OK
---------------------------
Crash report ID: E3B7FAFB-DCD8-4445-B84C-F40399929E2C
Crash report ID: 794A81D6-335B-4FA0-80E7-ECEA8BFF1378
Issue is replicable.
(Trying to format the post to correct the text formatting seems problematic, the preview example is inconsistent with how this message actually appears when I submit it so I can’t figure it out: Firefox, Windows 10 x64)