Search Issue Tracker
Fixed
Fixed in 6000.0.50f1, 6000.1.4f1, 6000.2.0a8
Votes
0
Found in
6000.0.23f1
6000.1.0a7
6000.2.0a1
Issue ID
UUM-84463
Regression
No
"Articulation Body" fails to move the GameObject when the "XDrive's" "Target" value is set in animation
Reproduction steps:
1. Open the attached project “AnimateArticulationDrive.zip“
2. Open the “SampleScene“
3. Enter Game Mode
4. Observe the result
Expected result: Bottom “Cube (1)” GameObject has moved upwards
Actual result: The “Cube (1)“ stays at the original position, the value “Target” is changed as expected
Reproducible in: 2023.2.0a12, 6000.0.23f1
Not reproducible in: 2021.3.44f1, 2022.3.50f1, 2023.2.0a11
Reproducible on: MacOS 14.6.1 (M1 Pro), Windows 10
Not reproducible on: No other environments tested
Notes:
- Also reproducible in Player
- None of the “Articulation Body” component’s properties are animating as well, yet the values change as expected
- Notice that in the Cube (1) in the Articulation Body component value “Target“ reaches 5 (from default 0), however the “Cube (1)“ didn’t change its position
- If you try to change the “Target“ value a bit in any direction by mouse motion, the “Cube (1)” moves according to the expected result
- If you try to change the “Target” value by mouse motion, the target value isn’t changing. If moved abruptly that way, the “Cube (1)” can move higher or lower than the “Target” value
- Manually setting the “Target“ value makes the “Cube (1)“ to move as expected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment