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
- The build size is larger when Models have Animation Type set to Generic
- Error "ArgumentException: Both 'ok' and 'cancel' strings are null or empty" logged when User is trying to create circular dependencies in UI Builder Hierarchy
- "SupportsRandomWriteOnRenderTextureFormat()" shows "False" when executed on 2023.2 and 6000.0 streams
- Size of ShadowCaster2D with Casting Source set to a Collider increases when RigidBody2D is attached to the GameObject
- GameObjects with a material derived from a Custom Lighting Surface Shader are displayed as skewed on quads when the Camera's Width and Height properties of the Viewport Rect are lower than 1
Add comment