Search Issue Tracker
Won't Fix
Won't Fix in 0.3.X
Votes
0
Found in [Package]
0.3.2-preview
Issue ID
ARB-11
Regression
Yes
Constraining a Prefab instance transform under the Rig Builder prevents the root from moving
How to reproduce:
1. Open the user's attached project "My project.zip"
2. See that the "CARRYABLE" GameObject is assigned to Constrained Object in "PlayerArmature" > "Rig-REPRO" > "AttachCarryable"
3. Enter Play mode and move the character using WASD or arrow keys
Expected results: The character is able to move
Actual result: The character is unable to move
Reproducible with: 0.3.2-preview, 1.0.2, 1.2.0 (2020.3.35f1), 1.2.0 (2021.3.4f1, 2022.1.4f1, 2022.2.0a15)
Not reproducible with: 0.2.7-preview (2019.4.40f1, 2020.3.35f1)
Reproducible on: macOS (Intel) Monterey 12.3.1
Notes:
- In 0.2.7-preview character is able to move but the constrained GameObject is not attached to the root's upper body
- Upgrading the package version from 0.2.7-preview yields the above-mentioned results
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Package signature validation unexpectedly return an invalid signature status if the validation check is done after the code signing certificate validaty range has passed
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (0.3.X):
There are no fixes planned for this Bug
Resolution Note (0.3.X):
As designed : the multiparent constraint in the project holds a TransformStreamHandle on the character game object. Such handle internally creates a root motion binding for that transform, which overwrite any input data coming from player input, editor...
Its equivalent of having an AnimationClip that has a curve for the root bone, in this case as well it creates a root motion binding inside the controller that overwrite the value every frame
The user can easily avoid this issue by adding an empty child GameObject to the character game object (with same position & rotation), and using this GameObject as parent constraint instead of the character game object itself