Search Issue Tracker
Fixed in 1.0.1
Votes
0
Found in [Package]
1.0.0
Issue ID
1254870
Regression
No
Profile Anayzer - Marker Table export returns different information on 5.6 vs 2019.3
Profile Anayzer - Marker Table export returns different information on 5.6 vs 2019.3
When using the Export - Marker Table features the results from Unity 5.6 are different to 2019.3. When doing this for 2019.3 vs 2020.2 it looked to match 100%
1. Open Unity 5.6
2. Load attached pdata file
3. Go to Export - Marker Table
4. Now reapt the above on Unity 2019.3 and 2020.2
5. Notice 2019.3 and 2020.2 match
6. Notice 5.6 has differences
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
- Applied velocity is inconsistent when using Rigidbody AddForce() with ForceMode.VelocityChange
- Crash on AudioUtil_CUSTOM_HasAudioCallback when exiting Play Mode while the Inspector is displaying a GameObject with an empty script attached
- Scroll offset is framerate-dependent when scrolling with velocity in the Device Simulator
- "Object.FindObjectsOfType<T>() is obsolete" warning is thrown when using "Transitions Plus" asset
- [Mono] Crash on SystemNative_ReadDirR() when building for IOS/Android on a macOS machine
Resolution Note (fix version 1.0.1):
Fixed sorting of frames (by time/count) to be more stable by providing a secondary sort by frame index