Z-Order keeps changing on aura update
tetsuomiyaki opened this issue ยท 15 comments
Describe the bug
Before update 2.17.0, I could properly set the z-order of auras in an aura group. This allowed me to overlay textures.
After update 2.17.0, the z-order of the auras now keep changing dynamically when any aura updates. They will only reset correctly after I type /wa. However, the problem will continue again the moment an aura updates.
Do you have an error log of what happened?
There are no errors.
To Reproduce
Screenshots
I have uploaded 3 images to show what it looked like before, and how it is now.
https://imgur.com/a/qTKOkRx. Each picture has a description of the problem.
Did you try having WeakAuras as the only enabled addon and everything else (especially something like ElvUI) disabled?
No.
Which version of WeakAuras are you using?
2.17.0
Are you on World of Warcraft Classic or Retail?
Retail
Was it working in a previous version? If yes, which was the last good one?
Yes, the release version right before 2.17.0.
Can you explain how to reproduce and give an export of an aura showing the issue ?
Also "no" is not the answer we expect when we ask this question
Did you try having WeakAuras as the only enabled addon and everything else (especially something like ElvUI) disabled?
I found the cause, it's actually because of the 'Set parent to Anchor' option when anchoring to other auras. The z-order no longer jumps around if I disable that option. Seems like 2.17 made it inherit the parent's z-order?
@tetsuomiyaki we still need your auras to reproduce and fix the issue.
aura group: https://pastebin.com/tmjpDS2h
textures/media: https://drive.google.com/file/d/1w9PJR0k2sMgTlqCSmbjaR-gyP7Rx5HD4/view?usp=sharing
To repro, just cast Immolation Aura to update fury resource.
The z-order will jumble up.
It can be fixed by making all the auras disabling 'Set Parent to Anchor'.
Does it still happen when you disable the addon you use to skin weakauras icons ?
Which addon are you using for this ?
I use Masque to skin the icons, but since it works on your import then it's not a bug I guess, I'll fix it manually from my end :)
I'll investigate this on the next weekend, hopefully I can figure out how to reproduce it
I couldn't reproduce the issue. I do have a iea where it could come from. Can you test whether https://github.com/WeakAuras/WeakAuras2/suites/629528427/artifacts/5087545 fixes the issue?
(Make a backup of your settings and then install that version of WeakAuras)
We have released this as a potential fix, if you still have problems we can try to investigate this more.