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.2
2020.2.0a8
Issue ID
1241219
Regression
No
Profiler image preview data is not displayed when the profiling information is loaded from a file
How to reproduce:
1. Create a new project
2. Open the Profiler window (Window -> Analysis -> Profiler)
3. In the Profiler Modules drop-down select 'UIDetails' Module to be displayed
4. Load the profiling information from a file (UIDETAILS.data)
5. Select the 'Batch 0' object (All Canvases -> Canvas -> Batch 0)
Expected result: a preview image is shown on the right side of the Profiler window
Actual result: no preview image is shown
Reproducible with: 2018.4.22f1, 2019.3.11f1, 2020.1.0b6, 2020.2.0a8
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (2020.2.X):
This is more of a feature request. How the system gathers and stores the instructions to render is not something we save when the profiler is saved as it would contain too much data.