Search Issue Tracker
By Design
Votes
0
Found in
2018.1.0a1
2020.1
2020.1.0a19
Issue ID
1214048
Regression
No
Profiler Record toggle is disabled after loading a file
How to reproduce:
1. Open the attached "1214048.zip" project and open the Profiler window
2. Enter Play Mode to begin profiling
3. Exit Play Mode and save profiling information to a file
4. Load the file that contains profiling information using the Profiler's 'Load' button. This will display the previously captured Profiler data in the Profiler window
Expected Result: The Profiler Window's record button stays toggled on
Actual Result: The the Record toggle is off (Does not reproduce for 2017.4.35f1)
5. Enter Play Mode
Expected Result: The Profiler begins profiling, data is shown in the Profiler window
Actual Result: The profiler window appears to not be profiling and the Record toggle is off (Does not reproduce for 2017.4.35f1)
Alternative Steps (particularly for 2017.4 and earlier):
1. Open the attached "1214048.zip" project and open the Profiler window
2. Enter Play Mode to begin profiling
3. Exit Play Mode and save profiling information to a file
4. Enter Play Mode
4. Load the file that contains profiling information using the Profiler's 'Load' button. This will display the previously captured Profiler data in the Profiler window
Expected Result: The Profiler loads the file and then continues profiling, data is shown in the Profiler window
Actual Result: The Profiler Window stops receiving new frames (and for versions after 2018.1, the Record toggle is off)
Reproducible with: 2018.1.0a1,2018.4.16f1, 2019.2.20f1, 2019.3.0f6, 2020.1.0a21, 2017.4.35f1
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
- Texture Sampling overlap causes graphical errors on specific Graphics APIs and Devices when using Framebuffer Fetch
- [Android] AssetBundle loading performance degradation when loading from a local Assetbundle
- [iOS][Android] Reflection with Generic Class returns unexpected values
- Shader Variant Collection Asset UI is hard to read when multiple Shaders and keywords are added
- Regression for "WebGL build is missing "malloc" and "free" functions when passing "-sERROR_ON_UNDEFINED_SYMBOLS=0" to emscriptenArgs"
Resolution Note (2020.1.X):
Since recording data on top of just loaded data might push that data out of the retained frame scope, and also potentially include recording the frame in which the data was loaded, this behavior is intentional.