Game was working fine last night, this morning after the patch it doesn’t even load and startup properly. Nothing has been changed on my PC except for the WoW patch this morning.
The screen goes black as it goes to full screen, then I just get the “World of Warcraft” program bar flashing about twice a second at the top of the screen. The mouse pointer has changed to the gauntlet. Clicking the close program “X” in the program bar when it appears doesn’t do anything, so I need to open task manager and terminate the WoW process to exit.
PC is an AMD 5800X3D, 64GB RAM, Nvidia 3080TI and Windows 7.
Ran the scan and repair tool, no difference, still doesn’t work.
1 Like
I have the same problem. Also, with Windows 7.
I have noticed that after waiting for a while with the “World of Warcraft” program bar flashing, and repeatedly pressing the “Enter” key, the game enters because it is showing the progress bar of the area you are in. But instead of showing the game, it just shows the mouse pointer on a black screen with sound and music in the background.
I think this may be a problem with the rendering engine.
1 Like
While not excusing this issue/bug you guys really need to move on to a newer operating system.
1 Like
Also black-falshing only. Win10 + NVIDIA+Intel i7
Thanks to ASAP give a hotfix
1 Like
Interesting, yes I think you could be right.
Noticed that the sound is still playing with the black screen and flashing program bar at the top. And if I keep pressing enter to login and start then it goes to the static loading screen with loading progress bar. But once it finishes loading and goes into the game itself then it’s back to the black screen again, then it crashes.
So yes, seems to be a problem with the 3D graphics display, as the 2D loading screen was working OK.
As for Windows 7, it does everything I need, plays the only game I play (or at least it did until today!) and if you know how is still receiving monthly security updates under ESU until 2026. So what’s the problem?
1 Like
Not truly. The users pay some money to use this game as a service. Like a plumber, a pizza, etc. Or, are you spending a lot of money for a new house, when a pipe get a hole?
There is a bug. That’s probably by weak onesystem-developers, and incompetent patch-testers, who don’t know even the basic rules of profession.
1 Like
Still exactly the same after the small update just installed there, doesn’t work.
The most recent update is nothing more than a content cleanup to free up space.
I think I’ve come up with a possible solution. Delete the Retail > WTF > Config.wtf file (or make a backup so you can remember what values you had configured previously). Remember that this file only has the general configuration values (graphics, sound…), not the custom ones for each character or the addons configuration. After deleting the file, start the game normally. Of course, all graphics options will have been reset to default values. Reconfigure the game. Change the graphics options one by one to see which one triggers the error in your case.
In my case, the option that triggers the error is anti-aliasing > image-based techniques > CMAA. You can test it to see if this is your case, since I use DX11 and render scale of 150%. I don’t know if the problem also happens with DX12 or other options.
2 Likes
Yes, well done and thank you!
It’s the CMAA anti-aliasing that was breaking it for me too.
Rather than deleting the config.wtf file I just edited it as it’s just a text file, then you don’t have to re-set all your other settings again.
Search for the line :
SET ffxAntiAliasingMode “3”
and change the “3” for a different anti-aliasing mode, changing it to “1” gives “fxaa low” anti-aliasing and a “2” gives “fxaa high” anti-aliasing so I went with that and now it’s working fine again.
So look inside the game directory down the “retail” directory (with underscores in the directory name, can’t show them here) and then down the “WTF” directory, then right click the “Config.wtf” file and select “Open with” and select “Notepad”.
The file should open as a text file, now find and change that line
SET ffxAntiAliasingMode “3”
Then exit notepad with saving the file.
Alternatively you can rename the “Config.wtf” by adding a “.txt” file extension, so it becomes “Config.wtf.txt” , then double click it to open in Notepad, change the required line and save the file, then remove the “.txt” extension to change the file back to just “Config.wtf” again.
2 Likes
That is incredibly odd. My next suggestion was going to be update your C++ libs. Are you running in DX11 or DX12 mode?
https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/
I’m running in DX11, which is all that’s available under Windows 7.
Not sure why they were updating anything to do with the rendering stuff in this patch but they definitely screwed something up and broke the CMAA anti-aliasing option for some of us.