Search Issue Tracker
By Design
Votes
0
Found in
5.2.2f1
Issue ID
747895
Regression
No
[WheelCollider] Wheel Colliders does not spin until 4000 force is applied to an object
To reproduce the issue follow the steps:
1. Open "u5wheels" project user has attached
2. Open "wheelrepro" scene
3. Play scene
4. Open "Cube" GameObject in inspector
5. Increase force variable in "Force Add" script component
6. "Cube" is going to start move when force reaches about 4000 units
Note: User added "cheat" variable in "Force Add" component that adds motorTorque and temporary fixes the issue.
Workaround: Adding small torque to the wheels unlocks their movement.
Repro Video: http://screencast.com/t/Np2KmoRW
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment