Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.4.X
Votes
0
Found in
2018.1.0a1
2018.4
2019.2
2019.3
2020.1
2020.1.0a11
Issue ID
1193516
Regression
Yes
Unable to load a Profile Capture from Unity 2017 when Unity 2018 or above is used
How to reproduce:
1. Create a new project
2. Open the Profiler window
3. Load the attached profiler capture named "Data_1193516"
4. Observe the console window
Expected result: Capture is loaded without any errors
Actual result: "Profiler data stream has invalid signature. Are you using a player built with an older Unity version ?" Error is thrown
Reproducible with: 2018.1.0a1, 2018.4.12f1, 2019.2.11f1, 2019.3.0b9, 2020.1.0a11
Not reproducible with: 2017.4.34f1
Notes:
Loading the profile capture using 2018.1.0a1 results in a silent crash
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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Resolution Note (fix version 2020.1):
As the error message suggests, the Profiler is not necessarily backwards compatible to old profiler data formats. From 2019.2 onwards, we are currently maintaining backwards compatibility but can't guaranty that we won't break it in the future.
Fixed in - 2020.2.0b1
Resolution Note (fix version 2019.4):
Fixed in - 2019.4.14f1