Search Issue Tracker
Fixed in 2019.1.X
Votes
0
Found in
Issue ID
1098090
Regression
No
Playmode tests timeout when Time.timeScale is large
The Playmode tests are probably using the GameTime to decide when to timeout, which make most tests that would touch Time.timeScale timeout way faster than expected.
Here's a snippet that reproduces the problem:
public class Wrapper
{
[UnityTest]
public IEnumerator ShouldNotTimeoutButItDoes()
{
Time.timeScale = 10;
yield return new WaitForSecondsRealtime(3.1f);
Assert.IsTrue(true);
}
}
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- APV data is sometimes incorrectly loaded from multiple baking sets when loading a scene
- GC Alloc spikes occur when calling UnityEngine.Resolution and UnityEngine.RefreshRate with Equals() and GetHashCode()
- Type error is thrown when a new ComputeShader is instantiated after destroying previous ComputeShader
- APV data becomes incorrect when reselecting the currently active Baking Set
- Launch screen image exceeds the screen bounds on IPad when building for iOS
Add comment