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
- The <sprite> tag inserted image from a Sprite Asset into the UI Builder Button disappears when the Inlined Style Text Shadow Horizontal or Vertical Offset is set to be more than 0 px
- Build fails when building with ILCPP Scripting Backend and ARMv7 as the Target Architecture
- Textures turn black in Player when they are referenced by a script instance
- [Android] Virtual device crashes with "Scudo ERROR: invalid chunk state when deallocating address" error in Firebase Test Lab when Optimized Frame Pacing is enabled
- Particle System does not resume when its Culling Mode is set to "Pause" or "Pause and Catch-up," and particle position simulate in world space
Add comment