Search Issue Tracker
By Design
Votes
0
Found in [Package]
14.0.2
Issue ID
1423991
Regression
No
unity_FogParams.y is never used in URP, considering unity_FogParams.y is useful for FOG_EXP mode
Reproduction steps:
1. Open user's attached project
2. In the Project Window find and open "ShaderVariablesFunctions.hlsl" (Packages/com.unity.render-pipelines.universal/ShaderLibrary/ShaderVariablesFunctions.hlsl)
3. Go to "ComputeFogFactor" function
Expected result: "ComputeFogFactor" function uses unity_FogParams.y
Actual result: "ComputeFogFactor" function doesn't use unity_FogParams.y
Reproducible with: 10.9.0 (2020.3.34f1), 12.1.6 (2021.3.2f1), 13.1.8 (2022.1.0f1), 14.0.2 (2022.2.0a12)
Could not test with: 7.7.1 (2019.4.38f1) - URP doesn't have "ShaderVariablesFunctions.hlsl" file
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:
We decided to not support this fog mode, so this is by design.