Search Issue Tracker
By Design
Votes
0
Found in
2019.4
2020.3
2020.3.7f1
2021.2
2022.1
2022.2
Issue ID
1402429
Regression
No
Procedural Shader is not displaying correctly when using SV_POSITION
How to reproduce:
1. Open the attached project (ShaderTest.zip)
2. Open scene Scenes/SampleScene
3. Observe the GameObject "Shader Plane" in the Scene view and Game view, positioning the Camera right above the Plane
Expected result: large pink markings are visible on the entire Plane
Actual result: the Plane is mostly black with little to no pink markings visible
Reproducible with: 2019.4.37f1, 2020.3.31f1, 2021.2.16f1, 2022.1.0b13, 2022.2.0a8
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2022.2.X):
This issue was caused by a mistake in the user's code, declaring "const float3 AA" in the global scope.