Search Issue Tracker
Won't Fix
Votes
0
Found in
2019.4
2020.3
2021.2.12f1
2021.3
2022.1
2022.2
Issue ID
1406024
Regression
No
Inconsistent GameObject movement when changing the order of Constraint components
Reproduction steps:
1. Open the user's attached project "Constraint Order.zip"
2. Enter Play mode
3. Select the "constrained" GameObject in the Hierarchy window
4. Change the order of components in the Inspector window
5. Repeat step 4 (~5 times)
Expected result: The movement of the "constrained" GameObject depends on the order of components
Actual result: The movement of the "constrained" GameObject can be different even when the order of components is the same (Sometimes the "constrained" GameObject circles around the "center" GameObject while facing it, other times the movement is jittery and the "constrained" GameObject looks away from the "center" GameObject)
Reproducible with: 2019.4.38f1, 2020.3.33f1, 2021.3.1f1, 2022.1.0b16, 2022.2.0a10
Notes:
1. User reported that this might happen when loading/unloading scenes or adding/removing Constraints. Could not reproduce the issue that way.
2. Relevant documentation: "When updating the GameObject, Unity evaluates Constraint components from first to last as they appear in the Inspector window." (https://docs.unity3d.com/2021.2/Documentation/Manual/Constraints.html)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
After evaluating the impact, workaround and risk associated with fixing this issue, in addition to the current team's bandwidth and priorities, we have concluded that this issue will not be addressed in the foreseeable future.
As an alternative, you can use our Animation Rigging (package) constraint.
We are closing this issue as Won’t Fix. Please inform the end user.