Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2018.4.16f1
2020.1.0b9
2020.2
Issue ID
1248645
Regression
Yes
[Frame Debugger] Shader properties and Texture data is clipped in Frame Debugger Editor
Shader properties and Texture data is clipped in Frame Debugger Editor. Refer the attached video
Steps to reproduce:
1) Create a new project with HDRP template
2) Window > Analysis > Frame Debugger
3) Enable Frame Debugger
4) Select GBuffer
Actual result: Texture data is clipped in Editor
Expected result: Texture data should not be clipped
Occurring on: 2020.2.0a11, 2020.1.0b9, 2019.3.14f1, 2019.2.18f1, 2019.1.8f1, 2019.1.0b1
Working fine in: 2018.4.15f1
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