Latency overlay sometimes fills 80-100% of castbar when interacting with objects
TorianKel opened this issue ยท 4 comments
Description
As you see on screenshot there're 2 castbars: one is mine and other is some import from wago to show that it's not unique to my setup.
WeakAuras Version
Weak Auras 4.1.4
World of Warcraft Flavor
Retail (Default)
Tested with only WeakAuras
- Yes
- No
Lua Error
No response
Reproduction Steps
- Find interactable object (usually a quest one)
- Click on it to start casting (there's some chance of issue being present, but if the object "caused" it once, you can stop the cast, and reproduce it)
Last Good Version
No response
Screenshots
Export String
No response
I cannot reproduce that anywhere. I've tried various interacteable objects, such as chests, world quest objectives and the cast bar behaves like expected.
Where is your screenshot from? We need to be able to easily reproduce it to figure out where the bug is.
Thanks for looking into. The issue is global for me, and it happens in Wotlk-classic too.
I printed the following values in-game on cast:
- select(4, UnitCastingInfo("player")) on UNIT_SPELLCAST_START
- GetTime() on CURRENT_SPELL_CAST_CHANGED
But they return the same value. What am I missing in the calculation?
Currently my noobly guess that some event doesn't fire (or in incorrect order) in case of interacting with quest objects. But it often masqued by hidden abilities like Demon hunter's double jump, gliding, etc that trigger CURRENT_SPELL_CAST_CHANGED
Sorry, but we don't need your help in debugging the issue. We need your help in figuring out how to reproduce that. And I specifally asked you for that, and you did not provide any hints how to reproduce it.
I'm still interested in how to reproduce it.