Search Issue Tracker
Active
Votes
0
Found in
6000.0.60f1
6000.2.8f1
6000.3.0b6
6000.4.0a2
Issue ID
UUM-122608
Regression
No
"State comes from an incompatible keyword space" error when clicking on a shader
How to reproduce:
1. Open the project “IN-117089_shader-test”
2. In the Project tab, click on Assets → Triplanar_Simple
3. Observe the Console tab
Expected result: No “State comes from an incompatible keyword space” errors appear
Actual result: “State comes from an incompatible keyword space” errors appear
Reproducible with: 6000.0.60f1 (61dfb374e36f), 6000.2.8f1 (c9992ac36c34), 6000.3.0b6 (211490bb75a6), 6000.4.0a1, 6000.4.0a2 (79bd4f638ac0)
Could not test with: 2023.1.0a1 (ArgumentNullException), 6000.3.0a6 (DirectoryNotFoundException and asset import failed errors)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Notes:
- The issue started after upgrading the project from 6000.0.47f1 to 6000.0.58f1
- Changing the fallback shader to Simple Lit fixes the issue
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit's TextInput element does not inherit layout parameters from the TextField element when TextField.multiline is true
- The TileMap grid in the Tile Palette is not visible when Screen Space Ambient Occlusion is enabled
- Pressing “-” twice to remove a Tag in Project Settings > Tags and Layers throws errors in the Console window
- "State comes from an incompatible keyword space" error when clicking on a shader
- Test Runner's Player test fails when the IL2CPP scripting backend is selected
Add comment