Search Issue Tracker
Fixed in 0.7.0-preview.1
Votes
0
Found in [Package]
preview.1 - 0.6.0
Issue ID
1235853
Regression
No
[Profile Analyzer] Offset depth value is incorrect when when comparing Profile Analyzer capture data
How to reproduce:
1. Open the Profile Analyzer
2. Go into the compare tab
3. Load 'Profile Analyzer - Capture (2019.3.6f1).data.pdata' in the 1st data slot
4. Load 'editorcapture.pdata' into 2nd data slot
5. Notice it shows 'Auto Right (0)'
6. Now load 'editorcapture.pdata' into 1st data slot
7. Load 'Profile Analyzer - Capture (2019.3.6f1).data.pdata' in the 2nd data slot
8. Notice it shows 'Auto Right (-17)'
Actual result: results are inconsistent when reversing comparison
Reproducible with - 2018.4.21f1, 2019.3.10f1, 2020.1.0b5, 2020.2.0a7
Package reproducible with - preview.1 - 0.5.0, preview.1 - 0.6.0
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 0.7.0-preview.1):
Offset depth now correctly calculated