Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2019.3.0a8
Issue ID
1166946
Regression
Yes
[Profiling] Multiple errors thrown on trying to view shader property matrices in Frame Debugger
Multiple errors thrown on trying to view shader property matrices in Frame Debugger. Refer the attached video.
Steps to reproduce:
1) Create a new project
2) Window > Analysis > Frame Debugger
3)Shader properties > Matrices > Unity_Matrix
Actual result: Multiple errors are thrown on trying to view shader property matrices
Expected result: Shader property matrices are displayed and non errors are thrown.
Occurring in: 2019.3.0a8, 2019.3.a07
Working fine in: 2019.3.a06, 2019.2.0b8
Environment: Both Windows and Mac.
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
Add comment