Description

I have a progress A progress bar containing a model used to be configured in this order (this is the expected ordering in my mind):

In this state, a model could be used as a backdrop for a progress bar and have a foreground bar color visible over the top.

The bar color starts as transparent, and then on conditions is changed to orange/blue/green.

It looks like this before.

on a trigger condition it looks like this

Since 5.3.2, to return to this behaviour, the model must be placed behind the background layer to work consistently. (this is an unexpected ordering in my mind).

here are both change and unchanged auras side by side. OG is in BG/model/FG order, new is in Model/Bg/FG order

Occasionally, in the expected order (bg/model/fg) the color will work as expected, im not sure what triggers the working state again

WeakAuras Version

5.3.2

World of Warcraft Flavor

Retail (Default)

Tested with only WeakAuras

• Yes
• No

Lua Error

N/A

Reproduction Steps

use this aura https://wago.io/J5V9sTM0F
enter ecplise states (solar/lunar or CA)
observe bar color does not change.

reorder model behind background layer and repeat test.
observe bar color changes

Last Good Version

5.3.1 (prior release)

Screenshots

No response

Export String

No response

Using alpha version of weakauras it works as intended, but you forgot to tick the option "Clipped by Progress"

in this case i dont clip the model.
the model should cover my entire progress. (i.e. the total, not the value)
the bar color should cover value only
i think that may be irrelevant to this issue though.

if its working in alpha il wait for that - it seems that the way i had it initially is expected to work

in this case i dont clip the model

That doesn't match the screenshots included in ticket

You need to provide a simple aura that shows the problem, not one that contains custom code that changes the region in various ways.

hmm, ok.
i feel like the presented issue is not being understood.
The issue isnt related to ticks, or to the model and its clipping.

The ticks are overlays and not edited directly on the region.

The foreground color representing the progress value does not display - i.e. the bar at the value of 43 in the above screenshot should be orange.
this worked until 5.3.2 where the ordering perhaps changed, and now works inconsistently

Il reduce it as much as possible. and feedback further

top image - model/bg/fg - not experiencing issue
middle image - bg/model/fg - the issue is here
bottom aura - model/bg/fg (the full aura)

reduced aura with issue https://wago.io/auFsQHmJr
reduced aura without the issue https://wago.io/b3wB86Ngt

these reduced auras do not interact with the region at all, the only custom code is to produce the value/total and overlay values

only change between these 2 auras is the position of the model subelement

after an unknown period of time or event, the middle aura begins to work, or stop working. see both variants working here now with no change

I'm not even sure after all these messages if the overlays are relevant. If the overlay color changes in the conditions are relevant. Whether the color changes in condtions are relevant.

Please create an aura from scratch that clearly shows the problem and has easy steps to reproduce.

Again, I stress, MINIMAL aura that shows the problem.

I can at least confirm that it looks different in the alpha compared to 5.3.2 Whether that's the intended look.

So I guess it's fixed already.

to be honest im not sure why it was addressed as a model issue, or an overlay issue.
the overlay works as expected and is only to place a dark opaque overlay over the non-progressed area

the issue presents itself in the BAR not being shown.
ive removed even more from those auras and uploaded new versions at the same link.

im not sure what else can be removed to prove this issue at this stage - its just a bar with a value and a total

top bar - foreground bar is visible and blue.
second bar - foreground image is not visible

We don't ask for more screenshots, but a MINIMAL example without custom code and conditions

I think I understand the aura now, and I'm confident that it is indeed fixed already.

But for your next bug report, please create a small reproducable exmaple. You haven't succeded in that here, because you somehow think that you need to retain as much of your aura as possible.

Thanks for following up on this

I believed the screenshot showing the ordering was clear, so was surprised comments were related to clipping or ticks or editing regions were produced.

in my mind in those examples I’ve removed everything that was irrelevant and left what reproduced the issue clearly - there’s definitely no intention to keep as much as possible. I agree the initial example still maintained some unneeded areas