Im trying to track this down, and have been running some utilities, like filemon, to see whats happening. In doing so, I noticed a wierd issue.
In the past, we had a wdb file, that contained a cache of items/mobs/etc. In 2.0 they moved it. It is supposed to be in the new Cache folder, but mine wasnt. I manually added a WDB, then an enUS folder into the cache folder (Cache\WDB\enUS) and my framerate went up, my network traffic went down, and I got a bunch of cache files put into that folder by the wow client.
Can anyone else try this and report back on lag/issues it resolves, or doesnt resolve.?
I'll check when I get home. Any particular hoops once you create the folder? (I'm assuming mine's missing, given how unpleasant things were last night.)
Edit: Yup, it was gone, and yup, this worked great.
I've been running 500-2000ms ever since the patch was released, but I've talked to other people and most of them seem to be fine. My internet outside of WoW is running just fine, so I'll give this a go once I get home and hopefully it'll resolve this issue. I'm seeing the same things though, naked people/slowly loading gear.
1. My Windows box at home has the Cache directory, but only a Survey.mpq file in it - no directory hierarchy at all.
2. A TBC Beta install on the same machine has Cache/WDB/enUS, populated with several cache-looking files in it : creaturecache.wdb, itemcache.wdb, itemtextcache.wdb, pagetextcache.wdb, wowcache.wdb, gameobjectcache.wdb, itemnamecache.wdb, npccache.wdb, questcache.wdb.
3. My MacBook has the Cache/WDB/enUS directory, populated with the same files as the TBC Beta above.
I only have physical access to the MacBook currently, so I can't test creating the directory on the Windows box and see if it suddenly gets populated while playing. But given that it exists on the Mac and on TBC Beta, it seems likely that it would start seeing use, if it existed.
Wodahs, major props. I went in game testing some other things, and someone mentioned their Alchemy tab never caching and it reminded me of this so we both tried it out. Sure enough, my FPS are up and his alchemy tab is caching.
Before you start to drift, and your soul begins to scream.
I just wanted to tell you, that you're listening to a dream.
Ha. Yes, I had noticed that my directory structure had a totally empty "Cache" folder now, but no WDB anymore (I noticed this since deleting my WDB is something I always do when DLing a major patch update, because I often get issues like naked players and invisible items if I don't). Good catch.
I only have minimal raid testing with this, but everything else is faster, so I am hoping raid performance is better.
Last night, having vid lag issues, I removed all mods, set graphics to low settings, and had 9 fps on patch, 1-2 at times during the fight. I am pretty desperately trying to find a fix here.
Yeah, I have been wondering about the empty cache folder every since they said that the WDB folder was removed and everything should exist in the Cache folder but mine was empty.
Another confirmation, as soon as I made the directory it got populated with the usual cache files that used to sit in our WDB folders. I was wondering what happened to the stuff too , since many people were complaining of the "all white character model" /??? items etc.
<Gwaihir> mage time is like booterang
<Gwaihir> AUGH BOOTERANG
<Gwaihir> AUGH MAGE TIME
<Ama> AUGH MAGE TIME
<XI|> AUGH MAGE TIME
Thanks a lot, fixed my FPS issues. Spreading a word now :)
Originally Posted by zeidrich
Women's breasts can be modeled as a cone and measured as V = (Db^2*h*.785)/3 and since breasts can be thought of as an amorphous fluid, you just have to worry about containing the volume of the breast.
Someone posted this on our guild forum, don't know from where but it might elaborate on some things.
Dear Blizzard and Readers,
This post points out that after patch 2.0, without corrective action on the user's part, the client doesn't cache WDB files anymore. It explains how to solve the problem and why it's important to solve it.
Symptom
When logging in, every time, a lot of the items placed on the action bars are red question marks for a few seconds. Also, when opening a crafting profession's window for the first time, delay is observed in loading the icon for items and list of ingredients. Other symptoms that indicate that the client is not performing caching and has to query the server for data with each login session.
Explanation and Solution
The old WDB folder is now gone with patch 2.0. The client is supposed to cache data in the "World of Warcraft\Cache\WDB\<locale>" folder, where <locale> depends on your client language. It's enGB for EU English players. However, during a standard installation and patching scenario, only "World of Warcraft\Cache" folder gets created, and the client doesn't automatically create its subfolders. This means that the client never saves cache files.
To force WoW to start saving cache files, manually create a WDB subfolder in Cache, i.e. make sure that a folder named "World of Warcraft\Cache\WDB" exists. The client will take care of the rest, create the locale specific subfolder and start saving files.
Why this is important
For starters, this improves the game experience of the end-user. However, more importantly, with so many players, all the clients querying the server for information that was supposed to be cached could lead to additional load on the servers. Only Blizzard knows the significance or fraction of this additional load, but it's important that we as users do everything we can to reduce load on the servers.
Edit: It appears that this may be an issue only on the Windows client and not Mac
How the hell does something like this get past internal testers?
OT and all, but having a fair understanding of the processes involved, the only way to 100% guarentee that this never happens ever is to run the installer for every stable breed of the patch on clean installs, repeatedly. Even using extremely fast computers with great imaging software you're talking aobut a nontrivial amount of time for -every- build including ones with dealbreaking problems entirely unrelated. I'd say that odds are pretty good that there was a feature to do this very thing, fully functional in at least one push.
Not to mention the issues on patch day doubtless invovled slightly altering the installer in an extreme time crunch so some stuff gets overlooked.
I'm all for slagging blizz as much as the next guy, but this looks like a pretty easy one to miss as QA.
Originally Posted by bartolimu
It makes me want to hit Marge Thatcher on the nose with a rolled up newspaper.
As another datapoint I haven't messed around with any files and I see the folder is already there on the OS X client, so this may be a bug related only to the Windows one.
I and a number of people in my guild have done this. It does indeed populate with the cache files, but none of us have noticed any increase in performance as a result. We did a little raiding in Naxx tonight and the FPS was as painful as it was last night.
Hey guys after reading this thread i went to my WoW folder to see if the WDB fodler was there and the whole cache folder structure was there and also the .wdb cache files that were named above, BUT all of the fodlers were read-only, so I turned that off and logged back into to WoW and the 1-2 sec lag issue with trade skills was gone. So make sure your cache folders are not write-proteced, thats another f.ck up by Blizzard (pardon my language).
When i made these folders the other day i got all the files mentioned above in them. But checking the folder today the files are gone again. Other people in my guild are also missing the files again, and are notcing that the lag is back. I had to download somthing when i loged in today, so it might have somthing to do with that. Anyone know anything about this?
It seems the WoW client sets the read-only attribute on the folders when starting up. I unset the attribute as I already had the folders in question, and found that after the cache files appeared as the should, the folders were again read-only. Exiting WoW does not reset the attributes, thus the folders stay read-only.
For the record, the cache files themselves are not read-only, meaning read-only folders dont really matter, as the WoW client just updates the already existing cache files. So if you have cache files already, there is no point in changing folder attributes
12/07/06, 3:24 PM
Similar Threads
