PapiOphidian
This is a collection of perceived bugs from ever since the interval version of FinalIK got updated/Avatar 3 released. I know I am very late to be posting this stuff, but I have been very annoyed noticing these differences all this time considering I am a very old player from when VRC used Unity 5.6. The issues I am outlining affect SDK2 and SDK3 Humanoid avatars unless specified otherwise.
  • Control being passed back to the VRIK component is considerably delayed (~3-5 seconds) after stopping locomoting even when all layers of every PlayableLayer have stopped transitioning. This is very noticeable by looking at the LowerBody (especially the feet) when in TrackingType < 6 and coming to a full stop when locomoting.
  • (SDK3) Auto-footstepping is only enabled when Upright > 0.7 (Even if the active state is the standing state).
  • Jumping seems to lock the LowerBody to the idle pose instead of control being retained by the VRIK component even if no Animator Tracking Control components are affecting any LowerBody field. (this was tested on Desktop. The effect is subtle, but noticeable and causes LowerBody IK such as auto-footstepping to be disabled for ~3-5 seconds)
  • (This should be done with default PlayableLayers for a noticeable effect) Switching to an SDK2 avatar from an SDK3 avatar partially retains the Locomotion Animator layer. This is easily observable by being in a TrackingType of 6 (FBT) and jumping while sitting down. The expected behavior is that the legs should continue to retain tracking to the feet trackers. What actually happens is they're forced into the idle pose while "tracking control is set to animation". I surround that in quotes because that concept theoretically should not exist to SDK2 avatars and does not exist if the user loads into a scene in an SDK2 avatar. Transitioning scenes while in an SDK2 avatar fixes this issue.