Search Issue Tracker
Fixed in 2020.1.X
Votes
4
Found in
5.2.0f3
Issue ID
725365
Regression
No
[WheelCollider] Suspension generates negative forces on high damper values
Repro steps:
1) Create a new project and import the package I attached
2) Open scene Negative suspension force
3) Run and notice the telemetry data in the Game view
4) Press Enter to give force to the object
5) Notice that F(Which shows WheelHit.force data) becomes negative for a short time
6) Pressing R restarts the position and pressing T enters slowmotion so you can see it a little bit better
7) By changing Vehicle - Huge Damper -> WheelColliders child component Damper value to a lower will stop generating negative force
-
Lex3425
Apr 25, 2020 19:38
That is an easy enough fix and like so of the bugs needing to be fixed, a simple setting to true can fix the issue. Glad to know the negative force can be avoided. We always are learning from this site and the fixes that take place to apply to other websites like https://www.anchoragesepticservice.com. Reading issues like these and taking into account what the fixes are helping keep everything operating smoothly.
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
- NullReferenceExceptions are being thrown when saving a ScriptableObject with an array of a type with a CustomPropertyDrawer that uses TrackPropertyValue
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
Resolution Note (fix version 2020.1):
Fixed in 2020.1.0a15, requires suspensionExpansionLimited be set to true on WheelCollider