Our records show that you have outstanding author rewards points. Please confirm your latest payment information and redeem your points balance via the Author Reward Store.
This was on a 8 x virtual,4 x core relatively new processor. Is it possible to reduce its CPU usage?
On a sidenote... WoW isn't optimized to use more than two cores. While it does use more if told to, it does not benefit enough from those to make a notable difference (besides that it doesn't run on the same core as the OS).
So Skada shows a summary of ~1433M Dmg and Recount shows only 314M Dmg, how exactly are those to windows comparable?
For me it looks like Skada is showing the whole log and Recount only last boss!?
Yeah, Blizz also tells you to run repair.exe and delete WTF and Interface folders whatever problem you run into...
most GMs just don't have a clue beyond what their knowledge base tells them (or just don't care to read/use them, as there's also an official support article stating several possible causes).
The error states, that a certain part of memory could not be read. And while Skada is triggering this, because you may just not need that part of memory without it, because of lower overall consumption, this most certainly is a driver or hardware problem.
This is most probably not the case.
WoWMatrix leeches its Addons from those at Curse and WowInterface, which still have a free enough license to do so. The only addons that should be more up-to-date using WoWMatrix would be those with own hosting, where the authors don't push every revision to Curse (e.g. DBM).
WM places a file in the addon folder, to check for the addon's version, in the past that led to problems with CC, you should reinstall all addons using the Client and see if that fixes your problem.
I don't know if there's a mod like that and honestly, how would you determine whether a user is afk and whether you stand around waiting for someone or because you have to buff after a wipe?
By the flag? Trust me, we had a raid where you where not allowed to go afk outside of a break in the middle and you get pretty used to jumping just the moment before you'd go afk, following the right people to not run into any corners and stuff :P
By standing around? That would as well count those waiting before their PC for those afk or those with no buffs while buffing, unless you force them to jump or move every minute.
An idea would be to upload the combatlogs to one of the popular sites where you can analyze raids (World of Logs for example tells you the overall time of the raid and the active time).
While it might seem simple that whenever Necrotic Plague jumps, Plague Siphon stacks too, the stack size on Lich King's buff doesn't tell how many stacks Necrotic Plague has. For instance, the Plague might disappear if the adds died too quickly and it didn't have any close units to jump to OR separate smaller stacks of the plague can combine into one larger stack.
So, you need to track Necrotic Plague stacks, and when the stacks go high, it jumps around pretty quickly and might be quite hard to keep track off.
Just have only one plague on all mobs.
When we did this on Tuesday we let the first plague vanish (decurse the one with it just out of camp).
Then gave the mobs the second one, to asure that enough mobs are present.
After that just decurse every plague until you're done and have the bored ranged DDs monitor the debuff... they got nothing better to do anyway...
They aren't hosting anything I hold the copyright for, so I didn't use their contact form, but I did report their illegal redistribution of computer software to their web host, here:
Seems it worked :p
Sorry, this page is not available any more, error 404.
0
0
On a sidenote... WoW isn't optimized to use more than two cores. While it does use more if told to, it does not benefit enough from those to make a notable difference (besides that it doesn't run on the same core as the OS).
0
Ontopic: I dont have problems with a single addon using LDB.
0
So Skada shows a summary of ~1433M Dmg and Recount shows only 314M Dmg, how exactly are those to windows comparable?
For me it looks like Skada is showing the whole log and Recount only last boss!?
0
most GMs just don't have a clue beyond what their knowledge base tells them (or just don't care to read/use them, as there's also an official support article stating several possible causes).
The error states, that a certain part of memory could not be read. And while Skada is triggering this, because you may just not need that part of memory without it, because of lower overall consumption, this most certainly is a driver or hardware problem.
0
http://wow.curse.com/downloads/wow-addons/details/enhanced-colour-picker.aspx
0
P.S.: There's a forum called "Addon Ideas" for those not looking for help, but to deliver... well... addon ideas.
0
WoWMatrix leeches its Addons from those at Curse and WowInterface, which still have a free enough license to do so. The only addons that should be more up-to-date using WoWMatrix would be those with own hosting, where the authors don't push every revision to Curse (e.g. DBM).
WM places a file in the addon folder, to check for the addon's version, in the past that led to problems with CC, you should reinstall all addons using the Client and see if that fixes your problem.
0
0
0
0
http://forum.spartanui.com/
Dunno if any of their Devs hang around here, but they will for sure there ;)
0
By the flag? Trust me, we had a raid where you where not allowed to go afk outside of a break in the middle and you get pretty used to jumping just the moment before you'd go afk, following the right people to not run into any corners and stuff :P
By standing around? That would as well count those waiting before their PC for those afk or those with no buffs while buffing, unless you force them to jump or move every minute.
An idea would be to upload the combatlogs to one of the popular sites where you can analyze raids (World of Logs for example tells you the overall time of the raid and the active time).
0
Just have only one plague on all mobs.
When we did this on Tuesday we let the first plague vanish (decurse the one with it just out of camp).
Then gave the mobs the second one, to asure that enough mobs are present.
After that just decurse every plague until you're done and have the bored ranged DDs monitor the debuff... they got nothing better to do anyway...
0
Seems it worked :p