Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2019.4.29f1
2020.3
2021.1
2021.2
2022.1
Issue ID
1356346
Regression
No
Configurable Joint behavior is noticeably different depending on Fixed Timestep
How to reproduce:
1. Open the attached project "PhysicsTest_Modified.zip"
2. Open "SampleScene" Scene
3. Enter Play Mode
4. Notice the behavior
5. Change Fixed Timestep to 0.001041667 (Edit > Project Settings > Time > Fixed Timestep)
6. Notice the behavior again
Expected result: The behavior stays similar despite used timestep
Actual result: The behavior is noticeably different
Reproducible with: 2019.4.31f1, 2020.3.20f1, 2021.1.24f1, 2021.2.0b15, 2022.1.0a12
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
Resolution Note:
With higher fixedDeltaTime values you tend to get a less accurate simulation and what is perceived as "expected" in this case, may just be the result of the simulation being inaccurate. Alternatively with drastically smaller fixedDeltaValues the simulation should be much more accurate and show the closer result to what the "true" result of the simulation should be based on the Joint settings.