Energy text update

[lerb]

Hey!

Having a problem with my unitframes. Playing a rogue, and my powerbar updates well, but my energy TEXT updates in per 20 energy ticks. Currently using oUF_Lily.

How do i fix this?

[yj589794]

In oUF_Lily the power bar is set with frequent updates, so it will update very often.

The power text tag is set to update only when certain events are received, hence the large jump in values it shows.


When the fontstring to hold the power text tag is created you can also apply frequentupdate settings:

	local PowerPoints = Power:CreateFontString(nil, "OVERLAY")
	PowerPoints:SetPoint("RIGHT", HealthPoints, "LEFT", 0, 0)
	PowerPoints:SetFontObject(GameFontNormalSmall)
	PowerPoints:SetTextColor(1, 1, 1)
	PowerPoints.frequentUpdates = true
	self:Tag(PowerPoints, '[lily:power< | ]')

As the updates will occur more often, then the cpu usage will also go up.

[haste]

You can also use an update value instead of true, which defaults to .5.

[Waverian]

If you want to mimic the default value for accurate energy updates use .1

[lerb]

Thanks alot guys, youre awesome

[zork]

Good to know that.

[Ferous]

I know this thread is a tad old, bit its awesome to know, now my tags are updating very well. Thanks

edit -

When I do put that tag:

self.name.frequentUpdates = .1

It updates faster, but it doesn't seem to still update as fast as say... Grid or VuhDo showing buffs, anyway to replicate the tags showing as fast as they are applied or happening?

[Dawn]

You could still decrease the number (which in turn increases cpu cycles used). The question is, if it's worth it. Or how accurate does it have to be without cutting to much performance.

[Ferous]

Originally Posted by Dawn You could still decrease the number (which in turn increases cpu cycles used). The question is, if it's worth it. Or how accurate does it have to be without cutting to much performance.

oUF doesn't use nearly as much memory as say VuhDO and PitBull together, so it wouldn't matter for me... but you're right, considering I'd like to have others maybe use it, they may not like it :P

[Freebaser]

Originally Posted by Ferous oUF doesn't use nearly as much memory as say VuhDO and PitBull together, so it wouldn't matter for me... but you're right, considering I'd like to have others maybe use it, they may not like it :P

This really has nothing to do with memory. Changing the value could make a big difference when your running an OnUpdate on 40 frames. It use to lag me quite a bit in AV, but this was before the 1.4 tag fix. I haven't tested it lately though.

[Ferous]

Originally Posted by Freebaser This really has nothing to do with memory. Changing the value could make a big difference when your running an OnUpdate on 40 frames. It use to lag me quite a bit in AV, but this was before the 1.4 tag fix. I haven't tested it lately though.

I'll check it out. Having it at .1 and no lag. I'll try out lower and see how my lag goes.

[Ferous]

I tried it all day doing batlegrounds, and i set it to .05, no lag, no nothing, everything was fine and it updates as fast as any other thing i.e. vuhdo so if you were lagging previously to the lag fix, it must have made it better.

[Dawn]

Like Freebaser said, it's not about memory it's about consuming CPU cycles. It can hurt slower PCs, but even cause lag on fast ones if you use it on an element that is spread over several frames.

You can test the performance with AddonManager - enable the CPU option, reload, try different values and take a look at how many CPU cycles are used. Basically half the time takes twice as much cycles (rough said).

That's why I said

The question is, if it's worth it. Or how accurate does it have to be without cutting to much performance.