Search Issue Tracker
Fixed in 2022.1.X
Fixed in 2020.3.X, 2021.2.X
Votes
0
Found in
2020.3.19f1
2021.2.0b3
2022.1.0a1
2022.1.0a8
Issue ID
1367470
Regression
Yes
Profiler's timeline view loses context frames when frames go out of Frame Count bounds
How to reproduce:
1. Open the attached project "2022Project"
2. Open "SampleScene"
3. Open Profiler Window
4. Profile any target, e.g. Playmode
5. Select the CPU Usage Profiler Module, switch to Timeline view
6. Toggle on "Current Frame"/">>|" button
7. When targeting the Playmode, make sure to toggle on the "Live" button
8. Start recording
Expected result: Context frames are always visible
Actual result: Context frames disappear after frames go beyond set Frame Count (As seen in the attached video)
Reproducible with: 2020.3.20f1, 2020.3.19f1, 2021.2.0b3, 2021.2.0b15, 2022.1.0a1, 2022.1.0a12
Not reproducible with: 2019.4.31f1, 2021.1.21f1, 2021.2.0b2
Notes:
Clearing the data resets the Timeline
Does not happen when saving the capture out and reloading it
Does happen when Preferences > Profiler > Frame Count is higher when saving the data than it is when loading it back in
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
- Shader Graph Asset icon is not shown on creation unless you confirm the name
- APV Sky occlusion doesn't consider the terrain
- [iOS] "EXC_BAD_ACCESS" Player crash when Script Debugging is enabled
- Cursor skips input fields when tabbing between two sets of input fields
- "Shader error redefinition of 'Varyings'" error appears when selecting the shader
Resolution Note (fix version 2022.1):
Fixed in 2022.1.0a13
Resolution Note (fix version 2021.2):
Fixed in 2021.2.1f1
Resolution Note (fix version 2020.3):
Fixed in 2020.3.22f1
Resolution Note:
Fixed in 2021.1.28f1