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
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment