Following up https://feedback.vrchat.com/sdk-bug-reports/p/freeze-to-world-on-constraints-will-always-bake-offsets-if-there-are-0-sources A parent constraint with "Freeze to world" enabled before the object containing it is turned off will not properly snap back when "Freeze to world" is disabled and the object is turned back on (on the same frame), if "Freeze to world" is re-enabled a frame later. Repro: Two objects, X (i.e. the avatar's armature) and Y (droppable) Parent constraint on object Y has a single source to X, activated via "Zero". A toggle is linked to two animations: * False = Object Y is turned off (2 keyframes, both are the same, animation duration is 0.017). * True = Object Y is turned on, "Freeze to world" is disabled on keyframe 0, enabled on keyframe 1 (animation duration is also 0.017) Assumption would be that because the parent constraint "freeze to world" is turned off, it would make object Y snap back to object X. This works in the editor , but does NOT work in game. A further observation was then made - adding a 3rd keyframe ("keyframe 2", animation duration 0.033) that is a copy of "keyframe 1" (object on, freeze on) made it work in game, but removing "keyframe 1" (so the animation duration is simply longer) did not solve it, it appears that for whatever reason the duplicated keyframe is necessary for the expected unfreeze/freeze snap to work in game.
