Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.13f1
2023.1.20f1
2023.2.0f1
Issue ID
UUM-56497
Regression
No
The articulation joint drive effect is not being applied to the GameObjects it is attached to when the Drive Type is set to Target Velocity and the Target Velocity value is less than 1
How to reproduce:
1. Open the “SuspensionDemo“ project
2. Open the “MainScene“
3. Open the “Assets/Wheel“ Prefab to edit in isolation
4. Open “Wheel > Suspension_Base > Suspension > Wheel“ child GameObject in the Inspector
5. In the Articulation Body Component set Drive Type to Target Velocity, Target Velocity field to 0.1, and Force Limit to 100000
6. Enter Play mode
7. Observe the “Car Body“ GameObjects movement in the Scene view
8. Observe the “Wheel-LF > Suspension_Base > Suspension > Wheel“ child GameObjects x-axis Rotation value in the Inspector
Expected result: The “Car Body“ GameObject is moving and the “Wheel-LF > Suspension_Base > Suspension > Wheel“ child GameObjects x-axis Rotation value is increasing
Actual result: The “Car Body“ GameObject is not moving and the “Wheel-LF > Suspension_Base > Suspension > Wheel“ child GameObjects x-axis Rotation value is not increasing
Reproducible with: 2022.3.13f1, 2023.1.20f1, 2023.2.0f1, 2023.3.0a5
Not reproducible with: 2023.3.0a14
Fixed in: 2023.3.0a6
Could not test with: 2021.3.32f1 (No option to choose the Drive Type)
Reproducible on: Windows 10 Pro
Not reproducible on: macOS 13.5.2 (Intel)
Notes:
- Reproducible in Player
- In version 2023.2.0f1 and up the Drive Type field should be set to 3
- Not consistent reproduction, when switching versions a fresh project should be 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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
After review we have elected not to address this issue at this time.