[BUG] VRC Avatar Parameter Driver does not work for a few frames after avatar loading
logi_9
In build 1101 and 1102, it seems that VRC Avatar Parameter Driver may not work correctly for a few frames after avatar loading.
I made a small Animator Controller to reproduce this problem.
This Animator Controller contains two layers:
- Layer0: This layer writes 1 to the local parameter Local.
- Layer1: This layer counts the number of frames it took for the parameter Localto be changed.
I think that Layer1 should stop at state 0 because modified values will be observable immediately, but actually it stops at state 2. This behavior is different from older builds.
Log In
n
nannokitty
I am not sure but whenever I load a new avatar was it makes my camera view like go up and my avatar is down on the floor and I’m not sure if I explained it more but I’ll come back to this and send a picture :)
Tony_Lewis
Actually, I found, when joined to instance,
ALL object assigned on ring menu will be disable state more likely as visual then initialized once local got loaded up avatars.
It means if avatar got multiple clothing on avatars and it set on ring menu to swap on join, it more likely happen to be naked on join until that people locally loaded up. (It is around few seconds.)
Non intentionally naked on join is kind of annoying things to be happen. (only can be seem by remote so users may not know it happened too.)
So it is better to be fixed ASAP.
Tupper - VRChat Head of Community
Although this appears to be a bug, it is best to assume that during the first few frames of the avatar being loaded and initialized the state machine may not run frame-for-frame perfectly. You should build your animators with that understanding.
Parapet Cloud
Tupper - VRChat Head of Community: I can understand if the animation controller holds for a few frames/seconds, but that's not the issue here. The issue is that the animation controller will go past a parameter driver without setting the parameter.