Search Issue Tracker
Duplicate
Votes
0
Found in
5.3.2f1
Issue ID
827682
Regression
No
Angular Drive Damper effectiveness drops after a certain value
Reproduction steps:
1. Open the attached project 'Angular'
2. Open the available scene
3. Play scene
4. Observe the behavior in scene view
5. In the 'Cube' gameobject, disable the Constant Force component
Note: This is the desired behavior
6. In the 'Anchor' gamebject's Configurable Joint component increase the Angular X Drive Position Damper to any number above 5000
Result: Increasing the Position Damper from 5000 up to the maximum has no effect on the rotation speed of the cube
Expected: Having increased the Damper up to a certain amount, the behavior should be close to the one in step #5. User expects the Damper effectiveness to be proportional to it's value.
Reproduced with: 5.5.0b2, 5.4.0p4, 5.3.6p3
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
This is a duplicate of issue #675704