Search Issue Tracker
Fixed in 2020.2.X
Votes
0
Found in
2018.1.6f1
Issue ID
1053580
Regression
No
ML-Agents causes Time.unscaledTime progression to slow down significantly vs. Time.realtimeSinceStartup when running at 30 fps
How to reproduce:
1. Open the "Test" scene in the attached project
2. Make sure that "Academy" Game Object is active
3. Enter the Play mode
Expected result: When running at ~30fps, Time.unscaledTime is not progressing more slowly than Time.realtimeSinceStartup.
Actual result: When running at ~30fps, Time.unscaledTime is progressing more slowly than Time.realtimeSinceStartup.
Reproducible with - 2017.2.0b1, 2017.2.3p2, 2017.4.7f1, 2018.1.8f1, 2018.2.0f2, 2018.3.0a4
Reproducible on all desktop platforms.
Notes:
- Could not be tested on 2017.1 due to errors ("<...> The type or namespace name `PlayModeStateChange' could not be found. Are you missing an assembly reference?").
- The issue is also reproducible after building and running a standalone version of the project.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment