- Sep 9, 2005
- 929
This may help with some of the issues people have been encountering.
http://www.wowinsider.com/2008/03/27/issues-with-omen/
http://www.wowinsider.com/2008/03/27/issues-with-omen/
Make sure everyone has the newest versions of Omen/Threat and no conflicting libs. If you use WAU, do the following:
1) Open WAU.
2) Go to Prefs. Make sure that "Download Dependencies" is checked. Make sure that "with Externals" is NOT checked.
3) Go to Files-->Reinstall All (near the bottom of the menu).
Have people do that, and update regularly. A couple of the Threat-2.0 updates have been backwards incompatible, and will make people not be able to see other people, which is bad.
There was a big change to Threat 2.0 very recently and it's Threat 2.0 thats the important bit. You may find that everyone had the correct version of Omen installed, but those using wowaceupdater downloaded a newer version of Threat 2.0.
To fix this you also need to ask your raid to search \WoW\Addons\ and all subdirectories for "Threat*" and delete all old instances then download the latest version of Threat 2.0
This is one of the biggest things that messes up Omen imo - some people just don't configure properly (or even use) wowaceupdater and have multiple copies of the Threat 2.0 folder in the "Libs" subdirectory of every addon. Everyone else automatically updates to the latest version of Threat through wowaceupdater and it all ends up a mighty mess.
My general approach is, without externals and with automatic dependecies. This keeps you from having like 369 lib folders in your addons embedded that all use "LibHealComm" or one of the Babble ones. It clutters your interface a little more but saves you hdd space and the game doesn't have to iterate through redundant files on login.
Without externals definately saves downloading and loading time if you have a lot of Ace addons. More importantly, I've had compatibility issues at times where addons have included outdated externals, causing other addons that depend on the same library to fail. Since going external-free, it has been smooth sailing, so I recommend it for everyone.
WITH Externals
AddonA uses libraryX and LibraryY, and AddonB also uses the same two libraries. If you installed both AddonA and AddonB "With Externals", you would have a folder structure as follows:
Interface\AddOns
..AddonA
.....Libs
........LibraryX
........LibraryY
..AddonB
.....Libs
........LibraryX
........LibraryY
When you load AddonA and AddonB, each addon instructs WoW to load the libraries contained within it's folder structure, meaning LibraryX and LibraryY both get loaded twice (once for each addon). X and Y are smart enough to know that they are the same library so only one copy remains in memory. This is also called "embedding libraries".
WITHOUT Externals
Using the example above, but installed "Without Externals", the folder structure would instead be as follows:
Interface\AddOns
..AddonA
..AddonB
..LibraryX
..LibraryY
AddonA and AddonB will have instructions in their TOC file to force WoW to load LibraryX and LibraryY first before attempting to load either addon (specifically, A and B will list LibraryX and LibraryY as dependencies). This means you only load each library once, shortening the loading time when first logging in. This is also called "disembedding libraries".
To run without externals, enable "Automatic Dependency Download" and disable "Default mode WITH externals".