Old textures don’t work either, at least for us. Characters that were made before the customization update - using old skins and hairs - still show up as void monsters.
Oh interesting. Most here have reported that old zones and textures are working. I think all cosmetics may have been changed to the new texture, if that’s the only place you’re seeing issues. Some hairstyles looked a bit “nicer.” But that could be my graphics settings, too.
Yeah… let me just go drop a lot money I don’t currently have upgrading not only the processor to something with an equivalent clock speed… mind you, this would also require upgrading the mobo and ram… WTF… just fix the damned rendering issue, the processor I have works just fine for the rest of the game.
Seems likely. It’s the only good explanation anyhow. It is strange, this issue seems to affect player character textures exclusively - and any NPCs who also use player textures.
I appreciate everyone’s enthusiasm here, but we’ve already determined that it’s a K10 vs Bulldozer issue. Something about the new models is not rendering properly on systems with pre-bulldozer architecture. It doesn’t make sense to me, but it’s the truth, since no one with post-Bulldozer systems have issues. If I were a betting elf, and I am, I would bet that they changed something in the game engine to target new technology and no matter how we complain about it, they’re not likely to fix it over night.
I’ve been thinking a lot about this and while it seems simple on paper, it might be more complicated than you’d think. I’d suggest only reporting issues and leaving speculation where you put your dirty shoes: At the door on a special mat so you don’t scuff the floor and make other guests mad at you.
You got this wrong. Understandably, as you’re not having this issue.
The non-rendering of textures happens to both old and new textures. And some “new textures” such as blood elves black skin, or bracers, are rendering for me.
Funnily enough, for me blood elves are having the face rendered, but the rest of the body isn’t. For undeads, some parts are rendered, some aren’t.
It’s really, really not an issue with old or new textures.
It’s a workflow for rendering that is meant for a certain architecture that doesn’t exist for old AMD processors.
I noticed ambience texture glitch as well. On character creation, texture on bodys and hair. The fingers on my warlock glitched as well. Face, eyes clothing, ok. I mean, if my character is nude, is glitched. I guess I’ll keep dressed lol.
Old textures only being hairstyles and eyes that existed before prepatch? The rest of the world looks fine? Because I think all eyes/hair are upgraded to new textures. I’m suggesting a switch you can flip to make everything cosmetic use an old-style texture to avoid this bug.
Sorry if it’s a redundant question, I don’t think I can read all 330 posts again
Oof.
The issue seems pretty simple to me. But again, I don’t work in the field. It might be incredibly thorny to solve. And if you’re saying they’re not likely to fix it soon, there goes my hopes.
Shortest expansion experience ever!
I’ll have to agree with @bragonsdane here. Is pointless to especulate on this issue.
Whatever you say, officer.
The world mostly looks fine from the very few I played. There are some textures here and there not rendering.
There are parts of the characters (both your, other players, and npcs) that are not rendering. For the parts rendered, they can be old textures or new, it doesn’t matter. For those parts not rendered, same thing.
If everything else looks good, clothes, mounts, weapons. In my case it’s just the eyes and hair (old and new) I even see the new mounts without any problem
For the new posters reporting in–keep the reports coming! The more traction and information we can get to work with, the better. And in case you missed it(since it kinda got buried), Bragonsdane gave an excellent breakdown earlier on what the potential issue could be.
Okay, So this will probably be a bit of a long post so feel free to get a cup of coffee. The AMD FX whatever was listed as the minimum system requirement… I wager this means that it is actually required! But enough of that. Let’s dive in and take a look at what this means. The FX platform was built off the AMD Bulldozer core. You can read more about that [here (wikipedia link)](https ://en. wikipedia .org/wiki/Bulldozer_(microarchitecture)). What’s important is that when the Bulldozer core c…
Oh and the reason old Intel CPUs don’t have this issue? they run AVX instruction sets.
That’s pretty much it right there 100%. I have no idea why AVX is likely the culprit, but it definitely explains why FX and later cpus have no issue. Up until then, SSE4a was the latest AMD had and sadly Phenom II was one year shy of getting it. Weirdly enough Intel and AMD both shipped CPUs supporting it at the same time. Intel shipped the Core platform with the i3, i5, and i7 first in Q1 2011. AMD followed with the FX in Q3 which sparked a lot of “add moar cores” memes. nerd talk aside, I ha…
As I’ve stated before, it seems a really weird problem to be caused by a processor, especially when everything else in WoW seems to be working normally. Other modern titles I’ve played recently have had zero issue as well. The example I used above was Monster Hunter:World, which released in 2017 and is much more demanding on the graphics. Another example I would point to is Planet Zoo–PZ released Nov 5, 2019, so it’s not even a year old yet, and given what sim games are–it can put a load on both the CPU and GPU with big zoos. I have had zero issues running Planet Zoo, even with the online franchise mode.
Thus it seems strange that there wouldn’t be a workaround somewhere, though it might take a few days to pinpoint and announce a solution and a few days more to actually get everything fixed. One of the major selling points in the past for WoW has been that it runs well on older hardware, so it also seems odd that Blizzard would suddenly abandon that position now(not saying they have). Ultimately, they’re gonna do whatever they’re gonna do; it’s just a wait-and-see at this point.
To be honest, I leveled from 45 to 50 this night. And saw this issue only one time outside of character, and explored pretty much all of zuldazar region.
it doesn’t matter if it’s an old or new style, none is rendered
Yeah, we cleared that up a few replies back. All cosmetics seem to be “new.” Their design isn’t new, but the way they are all displayed, even hair styles you’ve known for years, has changed.
Hey all,
Thank you for all the reports so far. We are currently investigating the situation and hope to have more information as soon as possible.
My processor: AMD Phenom 2
My video card: Geforce GTX 960
What I have done so far (these all resulted in the same outcome: black hair and skin and no eyes - the eyes are definitely the most disturbing part lol):
Put my boyfriend’s video card (Geforce GTX 1060) in my computer.
Tried different variations of DXDIAG (9-12) via WoW command line (-d3dx9, etc) and updated DXDIAG via Windows.
Put graphics to the very bare minimum.
Uninstalled WoW entirely (deleted all files), then reinstalled Windows 10, and reinstalled WoW once that was complete.
As an aside, guildmate has the same video card as I do and does not have this issue.
And lastly, with a different outcome, put my hard drive into my boyfriend’s computer to eliminate a software issue. Works fine on his computer.
In our opinion this seems to be a motherboard/GPU issue (or possibly memory). They’re just not playing too well together. Motherboard drivers and updates may help with this issue if there are any available but at this point we’re ready to just upgrade my motherboard and processor and get new memory.
I do want to point out that prior to patch, my computer had no issues at all running WoW at fairly high settings.
Sorry to everyone that is having this issue…it’s very frustrating.
Mark 2 more down with the same issue both with older AMD processors. Game runs great otherwise and I’ve been from BFA zones to Azeroth, to Outlands. We have different video cards so I’d agree with the architecture issue somewhere.