|
Nothing Yet?
|
#42
9/2/2012
|
Support Forum Agent
|
Sëvën, Bellamii,
I think you two may be confused. The componentThread variable is not a fix or a workaround. It's exactly the opposite of that. That setting will cause the issue to occur, if it isn't happening already. There is no fix or workaround for the actual issue at this time. As I mentioned, we're working on a hotfix but it is expected to take some time before its ready. Kirsa, TechFox does not have cybernetic legs. :( ________________________________________________ Technical Support Want to speak with someone directly? http://us.blizzard.com/en-us/company/about/contact.html Check your G-diffuser system! |
#43
9/3/2012
|
|
Thank the Gods, I was loosing my mind. My computer has held up this far but sheesh.
|
#45
9/4/2012
|
|
My Pc Runs the game fine i Run it on The Highest Settings but i cant se the dam Characters with armor in the back there all naked to me D.. but other than that my game runs smooth
|
#46
9/4/2012
|
|
Edited by Kybeorie on 9/5/12 9:35 AM (PDT)
On a lighter note, people with multiple core processors can simulate the bug by forcing the game to only use one processor! Just add the following line to your Config.wtf file: Hmm.... what if there was a way to fool Wow into thinking you had more than one core? Would the bug go away? Hmm.... Or does the bug exist because they hard coded one core to display the front half of the textures, on players, with the other core the back? So a user with a single core gets a naked texture. Odd? It sounds like they forgot to program in an "Except." Like, "share the load across the cores AND do it all on one core if there is only one core." |
#48
9/5/2012
|
|
I don't know if this would be possible (maybe it is), but my guess is that while it would eliminate this bug, it would probably also significantly degrade performance overall. When WoW is on a multi-core system, it takes advantage of that fact by having separate processor threads on different cores. If you force all those threads onto one core, the CPU has to waste a bunch of time switching between threads, whereas if the game knows its all on one core, it does it all in one thread. |
#49
9/5/2012
|
|
...just that a blue confirmed it and a fix is in the works made my day Unlke the 134 problem. /sadface |
#51
9/7/2012
|
|
Edited by Kaimeline on 9/7/12 6:46 PM (PDT)
I am experiencing this bug on an Intel Core i7-2600k, definitely a multi core machine, running Win 7 64-bit.
How would I confirm the game is using more than one core? Using Asus' AI Suite, I can see activity on all cores when I bring WoW up, but it doesn't identify the processes. EDIT WITH FIX! Doing the 'Restore Defaults' button in Launcher/Options/Game Preferences seems to have fixed it for me. I'll reset to how I had it before and see if it messes up and where. |
#52
9/7/2012
|
|
Same problem here, very annoying!! I first noticed this when i restored an old computer of mine (because it actually runs the game smoother than my laptop and has a better graphics card)
I didnt want to redownload the game due to a download limit with my isp, so i simply transferred the files through a network. My first assumption to the problem was a file got corrupted somewhere along the way but now i know thats probably not the case. My second assumption was could it possibly be that my laptop was running a 64bit version of the game while my computer im using now is 32 bit. Therefore id be running 64 bit wow on a 32 bit system (could this be an issue?) Im actually not sure if this is a single core computer - its an AMD Athlon(tm) 64 processor 3500+ 2.20 GHz. Any word back would help, thanks! |
#53
9/8/2012
|
|
It only affecting single core processors is load of crap, mine is a quad core and i still have this issue
|
#54
9/9/2012
|
|
Thank you for listening and I hope this is fixed soon.
I am hoping this is fixed before the Theramore event, I want to take screen shots :/ |
#55
9/9/2012
|
|
Likewise having this problem while running on Windows 7, but I suppose I'll try the solutions that have been suggested to see if those work. If not, glad to know Blizz is aware and working on a hotfix for it and will wait patiently for it to be ready :)
|
#56
9/9/2012
|
|
I set componentThread to 0. I cannot reproduce this issue, but characters are either flickering or invisible. Oddly enough, I see a decent increase in with the component thread disabled, but that's probably because it's not rendering all of the character models simultaneously.
________________________________________________ The wise speak only of what they know. - J.R.R. Tolkien CORE I7 3.8GHz | 12GB RAM | ATI 5970+5870 | F120 SSD Unofficial Tech Support: irc://chat.freenode.net/wowtech |
#57
9/10/2012
|
|
Please fix this soon... the backs are naked the front does not look right! This is really messing up my transmog business... I understand that only people with single core processors are getting this problem, but it's a big enough impact to seriously hinder how i make gold and enjoy my game.
|
#58
9/11/2012
|
|
Support Forum Agent
|
This issue should be fixed with today's patch. I'm no longer able to reproduce it with the component thread variable. Are people with single core systems still experiencing it?
________________________________________________ Technical Support Want to speak with someone directly? http://us.blizzard.com/en-us/company/about/contact.html Check your G-diffuser system! |
#59
9/11/2012
|
|
It's fixed for me! I cannot even tell you how happy I am. Thank you so much for fixing this!
|
#60
9/11/2012
|
