Search Issue Tracker
Fixed
Fixed in 2022.3.40f1, 6000.0.11f1, 7000.0.0a13
Votes
0
Found in
2022.3.9f1
2023.1.13f1
2023.2.0b9
2023.3.0a5
6000.0.0b11
6000.1.0a7
7000.0.0a1
Issue ID
UUM-48599
Regression
No
Dynamic Branching generates Shader Variants when building the Project
Reproduction steps:
1. Open the attached “Test Project” project
2. Make a Clean Build of the Project (File > Build Settings > Build > Clean Build)
3. Open the Project Auditor window (Window > Analysis > Project Auditor)
4. Press the “Analyze” button
5. In the Project Auditor window view Compute Variants (View > Assets > Shaders > Compute Variants)
Expected result: There are no variants with the dynamic_branch keyword
Actual result: There are over one million variants with the dynamic_branch keyword
Reproducible with: 2022.1.0a15, 2022.1.24f1, 2022.3.9f1, 2023.1.13f1, 2023.2.0b9, 2023.3.0a5
Not reproducible with: 2021.3.30f1, 2022.1.0a14
Reproducible on: Windows 10
Not reproducible on: No other environment tested
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
- VisionOS Player and Simulator crashes on "nw_read_request_report [C1] Receive failed with error "No message available on STREAM"" when playing a video through VisionOSVideoComponent
- Shader starts acting unexpectedly when SV_primitiveID is used in a Hull/Domain Shader
- [iOS] "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously when using specific Project Settings and Anti-aliasing is enabled
- Inconsistent help box font size in Project Settings window
- Local package MonoBehaviour scripts appear as missing after updating the project when the project and package paths share the same prefix
Resolution Note (fix version 6000.0.11f1):
Filter out dynamic branch keywords when computing shader variants.