Search Issue Tracker
Fixed in 0.5.0-preview.1
Votes
1
Found in [Package]
0.51.0-preview.32
Issue ID
1214110
Regression
No
Movement of Unity Physics and Havok Physics objects are dependent on the framerate
How to reproduce:
1. Open attached project "New Unity Project.zip" and scene "SampleScene"
2. In Hierarchy window, select "physics_step"
3. In Inspector window, set "Physics Step" -> "Simulation Type" to either "Unity Physics" or "Havok Physics"
4. In Hierarchy window, select "FrameLimiter"
5. In Inspector window, set "Desired FPS" to 0 (this will uncap the fps of the Editor)
6. Enter Play mode
7. In Scene view, observe the amount of time it takes for the sphere to move from one column to another (on my machine it takes about 9 seconds)
8. Repeat steps 4-6 but with "Desired FPS" set to 30
9. In Scene view, observe the amount of time it takes for the sphere to move from one column to another (on my machine it takes about 60 seconds)
Expected result: the sphere travel time with different "Desired FPS" is the same
Actual result: the sphere travel time with "Desired FPS" set to uncapped is about 9 seconds and "Desired FPS" set to 30 is ~60 seconds
Reproducible with: 2019.3.0f5, 2020.1.0a20 (0.1.2)
Could not test with: 2017.4, 2018.4 (Havok and Unity Physics not yet implemented) AND 2019.2.19f1 (0.1.1) ("Havok.Physics trial period has ended. is thrown" and the sphere does not move)
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
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
- Previously deleted “DefaultLookDevProfile“ is present when upgrading the Editor version
- [Ubuntu] UI text and buttons are missing spaces in Unity Version Control > New Workspace window
- "Inherit attribute is not supported" warning is shown but attributes are available in VFX Graph Output and Update blocks
Resolution Note (fix version 0.5.0-preview.1):
Fixed in: 0.5.0-preview.1