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
0
Found in
2018.4
2020.1.0b8
Issue ID
1246013
Regression
No
CPU time spikes because we do not have async readback for environment
How to reproduce:
1. Open the attached project "1246013.zip"
2. Open the "MainGame" Scene
3. Open the Profiler window and select the "Editor" mode
4. Enter the Play Mode and look around in the Scene
Expected result: no spikes in CPU time used by the EditorLoop appears in the Profiler
Actual result: CPU time used by the EditorLoop has spikes
Reproducible with: 2018.4.26f1, 2019.4.6f1, 2020.1.0f1, 2020.2.0a19
Notes:
- CPU time usage spikes occur only when the GPU usage is high (90% and more)
- The issue can be reproduced with less real-time lights on slower devices (with slower GPUs)
- The issue seems to be related to the Gfx.WaitForPresentOnGfxThread process which may take ~30-60ms of the CPU time
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
- Editor crashes when starting a new game session using Direct3D12 Graphics API
- Play on awake does not work with an audio random container when instantiating a game object
- Play on awake does not work with an audio random container when loading a scene
- Prefab components are not rendered correctly in the Inspector Window when "HideFlags.HideInInspector" is used
- The "Editor.CreateInspectorGUI" method is being called twice when the Console and the Inspector windows are in the same panel
Resolution Note (2021.2.X):
This issue will be fixed as part of a larger work undertaken in that area.