Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.2.0b2
2021.1
Issue ID
1280961
Regression
No
Changing the Profiler Frame Count size doesn't affect the data loading time when loading from a file
How to reproduce:
1. Open the attached project (case-1280961.zip)
2. Open the Profiler window (Window -> Analysis -> Profiler)
3. Enable 'Deep Profile' (just to make the issue easier to reproduce)
4. Enter Play Mode and exit it when the Profiler records more than 2000 frames
5. Save the profiling data to a file
6. Load the newly created data file to the Profiler and time it
7. Change the Profiler Frame Count to 300 (Edit -> Preferences -> Analysis -> Profiler)
8. Load the data file to the Profiler again and time it
Expected result: since only 300 frames are being shown, it takes less time to load the data from the file
Actual result: it takes the same time to load
Reproducible with: 2019.4.12f1, 2020.1.6f1, 2020.2.0b5, 2021.1.0a1
Could not test with: 2018.4.27f1 (changing Frame Count size not introduced)
Notes:
Increasing the Frame Count size when the data is already loaded does not reveal the hidden frames
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
- HDRP 6-way VFX Shader is lit incorrectly when World coordinates are used
- 2D Sprite Renderer in front is affected by Sprites in the background when using Sorting Layers and a Shadow Caster 2D with Self Shadow
- Modifying UI Prefab child's Height only confirms the first 1 or 2 digits when the Scene is newly opened or the Prefab is newly created
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
Resolution Note:
Team resolution is to close the performance optimization issue by design as this contributes to a feature request, which we need to address anyway as a part of scalability initiative