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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
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