Search Issue Tracker
By Design
Votes
0
Found in
2023.2.9f1
2023.3.0b6
6000.0.0b11
Issue ID
UUM-62808
Regression
Yes
”connectedAnchor” is set to 0 when setting “FixedJoint.autoConfigureConnectedAnchor” to false
How to reproduce:
1. Open the user’s attached “FixedJoint.zip” project
2. Enter Play Mode
3. Observe the 2nd debug text in the Console window
Expected result: Text is not (0, 0, 0)
Actual result: Text is (0, 0, 0)
Reproducible with: 2023.2.0a20, 2023.2.9f1, 2023.3.0b6
Not reproducible with: 2021.3.35f1, 2022.3.19f1, 2023.2.0a19
Reproduced on: macOS 14.2.1 (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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
Hello,
During the 2023.X lifecycle we changed the way Joint::connectedAnchor is being handled. Previously setting Joint::autoConfigureConnectedAnchor to false would override the previous value of Joint::connectedAnchor, effectively losing any user data that was provided. During 2023.X we've changed it so the value being set to connectedAnchor is maintained even when Joint::autoConfigureConnectedAnchor is set to true.
If you want to have the old behaviour this can be achieved by doing the following:
var calculatedAnchor = myJoint.connectedAnchor; //connected anchor still returns the calculated value when autoConfigureConnectedAnchor is true
myJoint.connectedAnchor = calculatedAnchor;
myJoint.autoConfigureConnectedAnchor = false;
We are aware that neither behavior was ideal depending on use case and are planning to further improve this API and the joint inspector going forward.
Cheers,
AlexRvn