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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
This is a duplicate of issue #1225362