AV3 animations bugging when sitting on a station that doesn't have a animator
complete
HolyKnightAD
This bug has been ongoing for a long time now. I think I didn't address this bug properly before. I'm not even sure as well if anyone else has already brought this issue up before. Anyway, if you use an avatar 3.0 with animations while sitting on a chair, your animations starts to bug. This only happens when a station doesn't have an animator in it.
What I find is that during an animation, any particle effects, sounds and probably other components that are controlled by animation will only play the first frame repetitively for the entire duration of the animation state. When transitioning to another state, the same animation bug will happen again.
Because of this bug, this might introduce a variety of symptoms such as lag when an avatar (with lots of complex animations) is sitting on a station that doesn't have an assigned animator.
So far, one possibly way to prevent such bug from happening is to assign an animator on a station. Another possible way also is to just change to an avatar that have little to no animations.
I hope the devs would fix this issue.
If you want to test this animation bug, just find a world or avatar that has a station in it. There's a pretty good chance that it doesn't have an animator assigned on that station.
Note: I'm not good on how to word things out. So please bear with me.
Log In
StormRel
complete
HolyKnightAD
As of VRChat 2023.1.2p1 build 1287. It seems to have been fixed. I've been to worlds with stations (with or without custom animators assigned). So far, AV3 animations are now working normally and doesn't have that annoying repetitive animation bug anymore. Haven't done with avatar stations yet. Thank you dev team for taking the time to work on this.
HK
available in future release
HolyKnightAD
HK: Does "AVAILABLE IN FUTURE RELEASE" means that it will be fixed in future release? (I've never seen this tag before so I just want to know what that means.)
HK
HolyKnightAD: Available In Future Release means we have a fix working internally which will be released with an upcoming update, barring sudden discovery of other issues with the fix.
HolyKnightAD
HK: Ah got it.
owlboy
HK: How far into the future we talking? 😉 Maybe this is done?
HK
owlboy: "Available in Future Release" is a completed status. Because the process of updating tickets is manual (for now) we mark this when we finish work on it, and then it will generally release whenever the next update occurs. So, presumably, this is released quite some time ago, though if the issue is reoccurring, we can look back into it.
Eventually, we will have automations in place that will go through and mark all tickets as Complete upon release. I'm aware the wording is somewhat confusing, but for now I think we would both agree that our time is better spent addressing tickets that have not been addressed yet.
owlboy
HK: Makes sense to me! I didn't think about it that way and figured a ping would be useful when I ran across this looking for another issue. Thanks for the explanation!
HolyKnightAD
Just want to leave this here because I think it's about the same thing...
Lush
tracked bug