Search Issue Tracker
Won't Fix
Won't Fix in 6000.6.X
Votes
1
Found in
6000.0.4f1
6000.1.0a7
6000.2.0a1
6000.3.0a1
6000.4.0a1
6000.5.0a1
6000.6.0a1
Issue ID
UUM-72784
Regression
No
Shaders created with Shader Graph generate a large amount of shader variants and cause slow build times when using a baked lightmap in BIRP
How to reproduce:
1. Open the attached “shader_variants_birp” project
2. Open the Build Settings (File → Build Settings…) and ensure that “Development Build” is selected
3. Press “Build”
4. Take note of the build time
5. Observe the result in the Console window
Expected result: The build takes a short time to complete (less than a minute) and few shader variants are generated
Actual result: The build takes a long time to complete (several minutes) and a large amount of shader variants are generated (30 000 - 60 000)
Reproducible in: 2021.3.39f1, 2022.3.31f1, 6000.0.4f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- Not reproducible in URP/HDRP
- The number of generated shader variants depends on the selected graphics API
** Direct3D11 - 50583
** Direct3D12 - 50583
** Vulkan - 33435
** OpenGLES3 - 32975
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 fails when building a project containing an 18+ dimension array with IL2CPP
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note (6000.6.X):
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.