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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment