Search Issue Tracker
Fixed in 1.1.0
Votes
0
Found in [Package]
1.1.0-pre.2
Issue ID
1331764
Regression
Yes
[Profile Analyzer] Frame Start/End values aren't matching on Frame Control and Frame Summary when the data is loaded
How to reproduce:
1. Open the user's attached "Blank_2021.2" project
2. Open the Profile Analyzer (Window->Analysis->Profile Analyzer)
3. Load in the user's attached "Profile Analyzer - Capture (2019.3.6f1).data.pdata" data
Expected results: The frame Start/End values on Frame Control and Frame Summary are the same
Actual results: The frame Start/End values on Frame Control and Frame Summary are diffferent
Reproducible with: 1.1.0-pre.2 (2018.4.34f1, 2019.4.26f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16)
Not reproducible with: 1.0.3 (2018.4.34f1, 2019.4.26f1, 2020.3.7f1, 2021.1.6f1, 2021.2.0a16)
Notes:
- Pulling the data will not produce the same issue
- If the data is pulled first then other data is loaded the frame start/end values will match
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
- Graphics State Collection warm-up does not work when using with Addressables Shaders
- "Baked Shadow Radius" field is visible but inactive when when the Shadow Type is set to "Hard Shadows" under the Light Component
Add comment