Search Issue Tracker
Won't Fix
Won't Fix in 1.2.X
Votes
0
Found in [Package]
1.2.1
Issue ID
ARB-38
Regression
No
The Min Limit property of the Multi-Aim Constraint has no effect on a Constrained Object
How to reproduce:
1. Open the “RiggMinLimit“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Move the “Target“ GameObject on the x-axis
5. Observe the Rotation of the “Cube“ GameObject
Expected result: The “Cube“ GameObjects rotates at a 45-degree angle only to one side
Actual result: The “Cube“ GameObjects rotates at a 45-degree angle to both sides
Reproducible with: 1.2.0 (2021.3.31f1), 1.2.1 (2021.3.31f1), 1.3.0 (2022.3.11f1, 2023.1.16f1, 2023.2.0b13, 2023.3.0a10)
Reproducible on: macOS 13.5.2 (Intel)
Not reproducible on: No other environment tested
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
- Texture Import Warnings are obscured by other Terrain Layer options in the Inspector
- Active Targets section text in Graph Inspector is truncated despite available space
- Burst Inspector middle divider is jittering when resized with the Burst Inspector window docked
- Shader Graph Node information is briefly displayed in Graph Inspector when clicking on Category in the Blackboard
- JsonConvert conversion fails trying to call GetCallbackMethodsForType when [OnDeserialized] is used in a class
Resolution Note:
Thank you for bringing this issue to our attention. We are aware of this specific problem with the limits of the Aim constraint. This is something that is difficult to address properly and has a high risk of regressing existing projects using this constraint.
Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues, as well as delivering the new animation system. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However we know each case is different, so please continue to log any issues you find, as well as provide any general feedback on our roadmap page to help us prioritize.
This specific issue is definitely something we hope to address/implement differently in our new animation system. For example, separate “aim” from “limits” and be able to use one, the other, or both.
Forum announcement: https://forum.unity.com/threads/animation-status-update-q2-2023.1445425/
Roadmap: https://unity.com/roadmap/unity-platform/3d-characters-and-animation
Resolution Note (1.2.X):
Thank you for bringing this issue to our attention. We are aware of this specific problem with the limits of the Aim constraint. This is something that is difficult to address properly and has a high risk of regressing existing projects using this constraint.
Unfortunately, after careful consideration, we will not be addressing your issue at this time, as we are currently committed to resolving other higher-priority issues, as well as delivering the new animation system. Our priority levels are determined by factors such as the severity and frequency of an issue and the number of users affected by it. However we know each case is different, so please continue to log any issues you find, as well as provide any general feedback on our roadmap page to help us prioritize.
This specific issue is definitely something we hope to address/implement differently in our new animation system. For example, separate “aim” from “limits” and be able to use one, the other, or both.
Forum announcement: https://forum.unity.com/threads/animation-status-update-q2-2023.1445425/
Roadmap: https://unity.com/roadmap/unity-platform/3d-characters-and-animation