Search Issue Tracker
In Progress
Fix In Review for 2022.3.X, 6000.0.X, 6000.3.X, 6000.4.X
Fixed in 6000.5.0a2
In Progress in 6000.5.X
Votes
1
Found in
2022.3.62f1
6000.0.49f1
6000.3.0b5
6000.4.0a3
6000.5.0a1
Issue ID
UUM-105298
Regression
No
"Scene Depth Difference" Node has an input Port which is called Position WS, directly referring to the World Space Position, when only the View Space Position can reflect if the object's depth is below or above the Plane
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/ShaderGraphBug.unity” Scene
3. Open “/Assets/Shaders/SceneDepthDifference.shadergraph“
4. Observe that the “Scene Depth Difference” Node has an input Port named Position WS
5. Observe the Capsule in the Scene view
6. Select “/Assets/Materials/Capsule.mat“ in the Project window
7. In Inspector, change "Position Input Space" from "View" to "World"
8. Observe that the Capsule is all green, even below the Plane
Expected result: “Scene Depth Difference” Node has a Position Port, which does not refer to World Space
Actual result: “Scene Depth Difference” Node has an input Port named Position WS, which stands for World Space position
Reproducible with: 2022.3.62f1, 6000.0.49f1, 6000.1.3f1, 6000.2.0b1
Reproducible on:
Play Mode
Windows Standalone Player
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Note:
- In Shader Graph, the Scene Depth Difference node asks for the World Space position ("Position WS"), and provides it by default if the input is not connected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment