Search Issue Tracker
Fixed in 2022.2.X
Fixed in 2022.1.X
Votes
1
Found in
Issue ID
1390142
Regression
No
Missing keyword declarations when using dynamic branching is not obvious to user
With the recent addition of #pragma dynamic_branch it is now possible to use keywords in runtime branching style code in addition to the preprocessor code selection.
If a shader has multiple subshaders/passes with shared code, it is easy to forget to declare all the keywords that are required for the shared code. The current errors given in this situation do not really help the user. All that we tell is "undeclared identifier 'FOOBAR'". It would be much better if we could tell the user right away that they're missing the keyword declaration in this particular pass.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment