Search Issue Tracker
Duplicate
Votes
0
Found in [Package]
6.9.0, 7.1.1
Issue ID
1178367
Regression
No
GameObjects with custom shader are rendered differently in Scene and Game views when fetching depth texture values
How to reproduce:
1. Open the attached 'project-1178367.zip' project
2. Load 'DepthTest' scene
3. Observe and compare the Scene and Game windows
Expected result: the cube is rendered the same in the Scene view as in the Game view
Actual result: the cube is rendered differently in the Game view compared to the Scene view
Reproducible with: 2019.2.6f1 (6.9.0, 6.9.1), 2019.3.0b3 (7.0.1), 2020.1.0a4 (7.0.1, 7.1.1)
Could not test with: 2017.4.32f1 (Package Manager not available), 2018.4.9f1 (due to shadergraph errors)
Notes:
1) The cube seems to be rendered somewhat inverted (considering the depth values in the Shadergraph) in the Game view
2) If Unlit Master node's surface is set to 'Opaque' the Scene view's cube will be black while the Game view's cube is white. Scrolling/clicking, while the mouse is within the Game window, will cause the cube to be flickering
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
This is a duplicate of issue #1225362