Search Issue Tracker
By Design
Votes
0
Found in
6000.0.22f1
Issue ID
UUM-83999
Regression
Yes
Shader Keywords are not detected when defined in include files
Reproduction steps:
1. Open the attached “BugRepro” project
2. Open the “Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Press the Spacebar
5. Observe the Game view
Expected result: Both spheres change color
Actual result: Only one sphere changes color
Reproducible with: 2023.2.18f1, 6000.0.22f1
Not reproducible with: 2021.3.44f1, 2022.3.50f1, 2023.2.17f1
Reproducible on: Windows 11
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
- 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
Resolution Note:
The documentation says that keyword directives can only be included using a special directive, `#include_with_pragmas`.
Please use this one instead of regular includes. It will work in all currently supported versions of Unity.