Lag in general with WoW 2.0 (naked People/?s for gear/Raid lag)
Posted 07 December 2006 - 08:24 PM
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.?
Posted 07 December 2006 - 09:25 PM
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.
Posted 07 December 2006 - 09:38 PM
Posted 07 December 2006 - 09:41 PM
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.
[edit: updated with TBC Beta directory info]
Posted 07 December 2006 - 09:58 PM
Posted 07 December 2006 - 10:16 PM
EJBSG 27 - Cally; EJBSG 22 - DeeBaltar; EJBSG 20 - Tory; EJBSG 19 - Leoben; EJBSG 14 - Helo; EJBSG 12 - Starbuck
Posted 07 December 2006 - 10:18 PM
Posted 07 December 2006 - 10:19 PM
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.
Posted 07 December 2006 - 10:30 PM
Posted 07 December 2006 - 10:32 PM
<Gwaihir> mage time is like booterang
<Gwaihir> AUGH BOOTERANG
<Gwaihir> AUGH MAGE TIME
<Ama> AUGH MAGE TIME
<XI|> AUGH MAGE TIME
Posted 07 December 2006 - 10:46 PM
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.
Posted 07 December 2006 - 11:12 PM
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.
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
Posted 07 December 2006 - 11:18 PM
edit: confirmed with a guildie in beta on enGB at least.
Posted 07 December 2006 - 11:31 PM
for the EU-enGB client.
Will have to see if it fixes the fps issues i had in Naxxramas tonight
Posted 08 December 2006 - 02:34 AM
Posted 08 December 2006 - 02:47 AM
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.
How the hell does something like this get past internal testers?
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.
It makes me want to hit Marge Thatcher on the nose with a rolled up newspaper.
Posted 08 December 2006 - 02:52 AM
Posted 08 December 2006 - 03:28 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users