CLU (Codified Likeness Utility)

I understand that you have tried to make CLU heal when needed but for me it simply wasnt. The whole raid got as low as 20% and stayed that low for at least 5 seconds.By the time CLU reacted, half the raid died and it only casted a rejuv on one person.I had to take over at that point by popping CD's to keep the rest of the people alive but it still ended with a wipe.And then i sadly got kicked

 

I recently (last weekend) noticed this too. My Priest was just standing there, as if no one needed healing. Log/Debug in HB did not write anything either, simply because nothing was happening. This went on for about 5 seconds, and then I manually cast a spell. After that, the CC kinda "woke up" and took over again. So, yeah, had this once too. I can blame lag, the CC, HB, the PC... not sure.
I did not notice this with my Resto Druid, only Priest because my AA/Disc Priests needs a target to heal (mob for Smite and Holy Fire).

Giving it a go tonight again.

 

I also noticed this with my Holy Paladin, I was also in a 5 man group and it was having problems healing some heroics. My gear is ilvl 382 and should be fine. Sometime he pauses and does nothing even when peoples HP is very low.

I am raiding tonight with my Resto Druid (my main) who is ilvl 393 so I will see how that goes as I have only ever used Hazzdruid for healing. This will be the first time using CLU on my resto

 

Well, I get kicked all the time because of this. By the way, has anyone tested the Holy Priest rotation? It seems that it has been tweaked a couple of days ago...

 

wulf,

Thanks for you work! I keep getting this error when trying to go into class config. There's more but here is a snip.

8:16:48 PM:953] You are a level 85 Frost DeathKnight
[8:16:48 PM:987] Loading settings ...
[8:16:48 PM:991] Settings loaded
[8:16:49 PM:011] [CLU] 2.7.8: WoWStats: Connected to the Grid
[8:16:58 PM:568] System.TypeInitializationException: The type initializer for 'CLU.GUI.Configuration' threw an exception. ---> Styx.InvalidObjectPointerException: Cannot read a descriptor on an invalid object.
at Styx.WoWInternals.WoWObjects.WoWObject.#eve[T](UInt32 field)
at Styx.WoWInternals.WoWObjects.WoWObject.#dve[T](Int32 offsetIndex)
at Styx.WoWInternals.WoWObjects.WoWUnit.GetCurrentPower(WoWPowerType type)

 

Im getting the same thing ^

 

Restart WoW, restart HB. I will go checking for more null objects tonight Having a target before entering the GUI may also not cause the error.

 

Guys, If it is doing nothing it is because CLU has no Target selected (probably because someone Died).

CLU is designed not to execute the rotation unless you have a target.

Next time you see the "Pause" happen simply select a target and the rotation will continue.

 

Wizard

 

I assumed this only was the case with a Disc Priest, as it kinda requires a hostile target for the main rotation. I noticed it with my Druid last night too. Just standing there, made me panic lol. Actually let 2 group members just die, doing nothing
Als Wulf, does the Resto Druid prioritize Tank healing? I notice it switching from members (5-man) to the tank continuously (really fast, targetting looked like it went berserk). Even if one of the members is down to 50%, the tank gets hit from 90% to 80%, it starts healing the tank and not the dps. Does it calculate or check incoming damage or something? Didn't notice this before, but now I can see the Resto Druid is letting group members getting dangerously low in health (and die!) all in favour of the tank, even if the tank is at 80%+

 

The Key bindings wouldn't be saved for me Folder rights are okay.. any idea?

 

Im sure you have it set ok but this is how I am running all the healing rotations with lazyraider.

 

Hi alexvip, Fixing now should have an update soon.

 

Well yeah, same as me except I'm running 30fps. Tried "follow tank" and in CLU "handle movement: YES" but that does not work at all lol.
Do 60fps get better results than 30fps?

 

1 FPS equals 1 TPS from HB if set to 60TPS and running at 60FPS.
Everything above 30TPS is more stable/faster on a decent computer (i5 3750k or better, 8GB ram and at least 6590HD)

 

Change Log
-------------

* 12/7/2012 [2.7.9]

• Keybinds not saving *fixed*
• Null Objects crashing the GUI settings *fixed*
• Two bugs with AreaHealing and Partyhealing returning Null *fixed*
• Resto druid minor tweaks.

 

Quite the system specs you need for a game released in 2004
I assume you mean a HD6950, as I have never heard of a 6590...

I still can not get 60fps on my rig (i5 2500K OC'd with 16GB RAM and HD6870 and Samsung 830 256GB SSD), even with somewhat toned down settings. Although it does not drop below 30 now (previously I had set everything to max on 1920x1200). I'm now on Good and High, which already goes against my principles... the rig should be able to handle all @ 60fps...

 

> Mainboard : Asus P8P67 DELUXE
> Chipset : Intel P67
> Processor : Intel Core i7 2600K @ 3400MHz
> Physical Memory : 16384MB (4 x 4096 DDR3-SDRAM )
> Video Card : NVIDIA GeForce GTX 590
> Hard Disk : C300-CTFDDAC128MAG (128GB)

Outside of raid with FXAA on I get 110+FPS (Outside) and 180+fps (indoors) (I dont run vsync)...Inside raid the minumum I get is 45fps on occasion. Everything Maxed (ULTRA)

I will say that before I ran FXAA I had multisampling set to x8 ingame with ultra and it was very whorey...FXAA with multisampling x1 ingame is godesend.

 

Thanks for the update. Saving keybinds works like a charm again. Cheers.

 

No worries Buttercup, Apologies for the delay