Search Issue Tracker
Feature Request
Votes
0
Found in
6000.0.25f1
Issue ID
UUM-85473
Regression
Yes
Configurable Joints are not scaled when the GameObjects containing the Joints are scaled
How to reproduce:
1. Open the “AnchorBug.zip“ project
2. Open the “SampleScene“
3. Enter Play Mode
4. Observe the Game view
Expected result: All cubes maintain the same respective distance apart while they are scaling up and down
Actual result: Cubes start touching when they are scaled up and are further apart when they are scaled down
Reproducible in: 6000.0.4f1, 6000.0.25f1
Not reproducible in: 2021.3.45f1, 2022.3.51f1, 6000.0.3f1
Reproduced on: Windows 11 Pro (23H2)
Not reproduced on: No other environment tested
Notes:
- Joint scales are updated in a script by resetting the “Joint.autoConfigureConnectedAnchor“ value in each frame
- The script becomes ineffective after the regression is introduced
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
- Mono release JIT incorrectly replaces long multiplication with a left-shift operation
- [IL2CPP] RuntimeInitializeOnLoadMethod is stripped/not executed for Android development builds
- Animation fails to trigger when Animator enters Animation State and Animator Component is on the parent GameObject
- "NullReferenceException" is logged when adding a visual element to a list using the Item Template setting
- Errors are thrown and the view is not rendered properly when using Overlay Camera with Non-Default 2D Renderer
Resolution Note:
Heya, thank for you for the report but this is not a regression. The reason why the previous approach worked was due to the fact that joints never cached their initial frame and would sag/break each time they were changed at runtime. Making use of autoConfigureAnchor to pick up scale changes is a good idea and a valid usecase. As such we'll open up a internal task to add proper scale handling for joints and tie in this report to it.
Cheers,
AlexRvn