WowAce

The default unit frames have shown absorbs as an additional bar attached to the health bar for a long time now. I haven't been able to create a bar anchor to the health frame in order to mirror this functionality. But recently after having done Ko'ragh, it is aparent that this is now a major shortcoming as the default raid frames also show a reversed absorb bar to indicate healing needed.

The functionality seems to be similar to the incoming healing bar; an attached bar to the health bar that extends in either direction based on the absorb or reverse absorb.

You can create a new bar to display heal-absorbs (for example a lateral bar). Anyway if you want a heal-absorb bar attached to the health bar but in reverse direction, this can be done too using lastest grid2 versions. - Create two new bars for healh-deficit and heals-absorbs statuses, put the healh-deficit bar on top of the standard health bar (selecting a higher framelevel). -Create a transparent color status, and assign this color to the health-deficit bar. -Enable "reverse fill" for the health-deficit bar and attach the heals-absorbs bar to the heal-deficit bar. -Ready.

Thanks for the help, what causes the "Anchor to" dropdown to show up? Some of my bar indicators have it and some don't.

@Imminent: Go

The rule is: no more than one indicator can be linked to another indicator. So if you link heals <-> health , no other bar can be anchored to heal or healths. The current system does not fit well with the grid2 design; it's a little hackish, im finishing a multibar indicator to replace the actual system.

Uploaded a version including a multibar indicator, supports reverse and non reverse bars. Maybe some configuration options are not intuitive enough, especially the "overlap" option. "Overlap" must be disabled in bars like a "shields" bar, if a previous reverse bar is defined: because we want to avoid anchoring the shields bar to the bottom of the reverse bar. Any feedback, specially malfunctioning reports will be appreciated.

I'll switch from using your previous suggestion to the multibar and play around with it in raids this week.

After updating from the release version to alpha, the frame updates are noticeably slower, ill ns regrowth someone and their bar wont move for a second or two, very disconcerting.

@Imminent: Go

The new indicator has more cpu impact, but not so much, i think it must be faster than raid blizzard frames for example. I cannot reproduce this behaviour (at least in my shaman resto). Do you have lua errors enabled ? Maybe something is crashing continously.

Not the best example, but just recorded a quick segment showing the delay on 50% of casted regrowths. I'll try a comparison tomorrow of grid r734 and blizzard frames.

https://www.youtube.com/watch?v=RTWnXe7uk_c

The last 3 or so casts really show the delay.

@Imminent: Go

I cannot make tests in raid until tomorrow (its early in morning here), i cannot detect any delay in proving grounds. Can you test the issue with different health update methods ? normal, fast , instant ?

Its hard to confirm the issue especialy with several healers in raid, for example if a player receives extra damage during the heal cast, the applied heal is not going to increase the player health, and the health change after 0.5 seconds could be due to another healers casts (0.2-0.5 seconds is the tipical notification delay of the game for health changes caused by damage or heals casted by another players). Yes, it would be good to compare with blizzard raid frames, in this case use the "fast update" method.

Another good test will be: You can create an additional standard bar indicator to display health, place the bar at the bottom (like a mana bar), so you can compare the behavior of the two indicators.

Here's a comparison between blizz frames and grid2 r749. The frame order is reversed but you can see during the tranquility that the blizz frames will update immediately and the grid2 frames are slightly delayed.

https://www.youtube.com/watch?v=cDqbOZzGBFY

@Imminent: Go

The only logical explanation is: Your health status update frequenty configuration is set to Normal, not Fast or Instant. Tested the 3 options, and the instant option is even faster than blizzard raid frames catching health drops (and fast option has identical behavior than blizzard frames). The only option with some delay is Normal, and its the expected behavior.

The status update was set to normal, oops. Thanks for the help, it works beautifully now. I haven't had any issues with the multibar, the health-current, heal-absorb reverse and shields all on one indicator seems to work fine. I'm excited to test it out on koragh this week.

Edit: Worked perfect on koragh.