(copy of my forum post from two days ago)
Still looking for a permanent replacement for the ICC-impaired HeadCount & the display-impaired NRT, decided to start testing Raid Tracker a couple months ago.
As normally do with mods to be used on my raiding characters, started testing on a low level alt. With v2.2.60, the mod used between 0.500-0.600 CPU/second when the character was idle & solo (tested alone, all libraries disembedded & "most recent" versions from the WowAce SVN/gits). Which is not good at all; didn't test it any further.
Still looking, decided to give the current v2.2.62 a try. On the alt, the idle CPU usage has dropped to 0.130 to 0.140 CPU/second. This was after disabling the "solo" (& party) options in the mod & relogging. Which moves it into the usable category here.
One question, though: why any CPU at all when solo and/or idle? Neither NRT nor HeadCount use any CPU on idle and its unexpected behavior for a mod that should only be active in raids.
- - - - - - --
Second issue: did a couple 5-man parties & one raid. Carried over from the test, all its "party" & "solo" options are disabled (seems to use a global profile). In the 5-man, got odd debug-like chat feedback at various times:
Auto Event boss update "Trash mob".
Auto Event boss update "Prince Keleseth". (was doing heroic UK)
Received chat feedback with each boss name in the instance after the bosses were killed, like the above. Opened up the Raid Tracker window, it showed the instance name in the header on the left side of the window. No bosses or drops were recorded on the right side of the window.
For the raid, however (it was the weekly raid, first boss in Ulduar), names were recorded as expected along with the loot drops.
In addition to the unneeded chat feedback, seems to be improperly semi-active in 5-man instances even when you have told it not to record anything in them.
- 2 comments