Search Issue Tracker
Fixed in 5.2.2
Votes
0
Found in
5.1.2f1
Issue ID
719296
Regression
No
WheelCollider: when collider position doesn't match the position of parent object WC is positioned wrong
Steps to reproduce:
1. Open "ScaleBug.zip" project
2. Open scene bug
3. Select "GameObject" and scale it
4. Notice that wheel collider is scaled incorrectly
5. Select "GameObject>boxColliders" and remove the box collider
6. Scale "GameObject" and notice that bug still persists
7. Remove rigidbody from the "GameObject" and attach it again
8. Scale "GameObject" and notice that bug is no longer present
- This bug occurs when the object which has box collider attached isn't in the same position as its parent object. If we set the position of "GameObject>boxColliders" to (-1, 0, 0) and set the center of its box collider to (1, 0, 0) then the bug won't be present.
- Any type of collider can cause this bug (e.g. box collider, capsule collider)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error ‘cannot use casts on l-values’ when a variable is assigned inside a second-level nested if statement before being used in a conversion
- "You cannot save to an invalid folder" warning dialog box is shown when canceling Tile Palette creation
- Global Volume visual details are blurred when Tonemapping mode is set to any other than 'ACES'
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
Add comment