Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0b5
2018.1.9f2
2018.2.0a1
2018.4.0f1
2019.1.0a1
2019.2.0a1
2019.3.0a1
Issue ID
1167755
Regression
Yes
Collider's position is not updated in runtime when Time.timeScale is set to 0
How to reproduce:
1. Open the attached project ("timeScale test.zip")
2. Open the repro scene ("SampleScene")
3. Enter Play Mode
4. Click and drag the cube around the scene a few times
Expected results: Collider's position is updated (the cube can be dragged repeatably)
Actual results: Collider's position is not updated
Reproducible with: 2018.1.0b5, 2018.1.9f2, 2018.2.21f1, 2018.4.4f1, 2019.1.10f1, 2019.2.0b9, 2019.3.0a9
Not reproducible with: 2017.4.30f1, 2018.1.0b4
Note:
Manually simulating the physics with "Phsyics.Simulate" fixes the issue (https://docs.unity3d.com/ScriptReference/Physics.Simulate.html)
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
- Inspector elements are rendered twice when the script component is added via drag-and-drop while the HideFlags.HideInInspector property is set
- Error "Light baking failed with error code 5 (Convergence data not available while rendering lightmaps)" thrown in Console when generating lighting for specific GameObjects
- Copy and Paste options for an Animation Property value are disabled in the Right click contextual menu
- Asset is not found when searching the Label "NewLabel" in Search Window
- "Compute dispatch: missing texture ID..." and "Compute dispatch: missing UAV ID..." warnings are thrown after changing the platform in High Definition 3D template
Resolution Note:
https://docs.unity3d.com/ScriptReference/Time-timeScale.html
"FixedUpdate functions will not be called when timeScale is set to zero." => physics won't be simulated either.