Search Issue Tracker
Fixed in 2022.2.22f1
Fixed in 2022.3.X, 2023.1.X, 2023.2.X, 2023.2.0a17
Votes
0
Found in
2022.2.18f1
2023.1.0b15
2023.2.0a12
Issue ID
UUM-34873
Regression
No
Dynamic Branches do not work with Strict Variant Matching
Strict Variant Matching always fails when using Dynamic Branches instead of other types of keywords.
I've made a simple repro project, with Strict Variant Matching enabled, where I have a simple shader (Stripped down to almost nothing from the URP Lit shader) and two boxes in a scene. In the shader I have a define (_USE_DYNAMIC_) to switch between using a dynamic branch or multi compile for the three Fog keywords.
Expected results are:
- Fog disabled: RED
- Fog enabled with _USE_DYNAMIC_ disabled: BLUE
- Fog enabled with _USE_DYNAMIC_ enabled: GREEN
In the editor everything works fine but if the define is set to 1 and you make a build and run, Strict Variant Matching will fail and render the boxes in magenta.
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note (fix version 2023.2):
Fixed dynamic branching keywords when using strict variant matching
Resolution Note (fix version 2023.1):
Fixed dynamic branching keywords when using strict variant matching