2019 changes Constraints execution order
complete
Ponponsan
When attaching constraints on bones that were affected by FinalIK (apparently Dynamic bones too), it stops working correctly in the editor.
If this is going to be fixed in-game, a option to apply the same setting to the project through the SDK is much appreciated.
Log In
Tupper - VRChat Head of Community
marked this post as
complete
Actually, let's go ahead and complete this so I don't forget about it!
Will be fixed upon the release of 2021.3.2p1.
Tupper - VRChat Head of Community
marked this post as
in progress
A fix for this has been made and tested internally, and will be released when we next update the SDK.
MeroFune
Note that this is also an issue with offline testing in game. Fully uploaded models are fine, but models that are built for testing offline have the same issue as in editor.
Tupper - VRChat Head of Community
MeroFune: Can you confirm this? We don't see this behavior.
Local testing avatars run the exact same logic as all other avatars-- they just aren't visible to others.
「Nara」
I have a small script that works around this issue for Dynamic Bones which you can use until this get patched officially. https://github.com/Naraenda/NarasUnityTools/blob/main/Nara/DynamicBonePatcher.cs
Tupper - VRChat Head of Community
Aiming to get this into a patch soon.
Tupper - VRChat Head of Community
marked this post as
tracked
Tupper - VRChat Head of Community
To be clear, are you stating that constraints no longer:
- Correctly copy the resultant FinalIK transform location
- Correctly copy the resultant DynamicBones transform location
?
If so, can you please provide an avatar ID that demonstrates both? Ideally they should work fine on Live, but not on Open Beta.
Tupper - VRChat Head of Community
Oops, I misunderstood. This only happens in editor.
We'll look into it!