Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
2
Found in
2017.4.0f1
2018.3.0a1
2018.3.5f1
2019.1.0a1
2019.2.0a1
Issue ID
1133379
Regression
No
Standalone Player has highly unstable frame times when Dynamic GI, moving Light and Frame queuing is used
How to reproduce:
1. Open attached project
2. Build and Run Windows Standalone Player
3. Adjust the slider in the right bottom corner of the screen to get FPS around 100
4. Press "Backspace" to change the value of maxQueuedFrames to 0. Average FPS will decrease but frame time will be stable.
5. Return maxQueuedFrames back to 4 by pressing "Backspace" again.
6. Press "Enter" to stop the light animation. FPS will increase significantly and micro freezes will disappear.
Reproducible with: 2017.4.22f1, 2018.3.8f1, 2019.1.0b6, 2019.2.0a7
Actual results: unstable frame times
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment