Search Issue Tracker
Fixed
Fixed in 2022.3.0f1, 2023.1.0b20, 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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note (fix version 2023.2.0a17):
Fixed dynamic branching keywords when using strict variant matching
Resolution Note (fix version 2023.1.0b20):
Fixed dynamic branching keywords when using strict variant matching