Search Issue Tracker
Won't Fix
Won't Fix in 2023.3.X
Votes
1
Found in
2020.3.40f1
2021.3.10f1
2022.1.17f1
2022.2.0b7
2023.1.0a11
2023.2.0a1
2023.3.0a3
Issue ID
UUM-16055
Regression
No
Build fails to compile due to a Shader error when using URP or HDRP packages
Steps to reproduce:
1. Open the user’s attached project
2. Open the “Assets/Scenes/SampleScene.unity“ Scene
3. Go to File > Build Settings > Build And Run
4. Observe the Console window
Expected result: Build is compiled successfully
Actual result: Build fails to compile due to “Shader error in 'Shader Graphs/glTF-unlit': 'CustomLight_float': output parameter 'Direction' not completely initialized at Assets/Shaders/UnlitReceiveShadow/CustomLight_float.hlsl(5)“ error
Reproducible with: 2020.3.40f1, 2021.3.10f1, 2022.1.17f1, 2022.2.0b7, 2023.1.0a11
Reproducible on: Windows 10
Notes:
1. Build is compiled successfully when building on top of the failed build files
2. Reproducible with URP and HDRP packages
3. Not reproducible with built-in RP
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
- Build and Run button greyed out for locally invalid architecture, despite remote build is specified
- Graphics Settings: “Use Defaults” checkboxes misaligned in Tier Settings section
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- 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
Resolution Note:
The custom function node is redefining internal (Unity shader library) preprocessor macros. Removing those gets rid of the "incomplete initialization" error.
Resolution Note (2023.3.X):
The custom function node is redefining internal (Unity shader library) preprocessor macros. Removing those gets rid of the "incomplete initialization" error.