Search Issue Tracker
Fixed
Fixed in 6000.0.63f1, 6000.2.14f1, 6000.3.0f1, 6000.4.0a6, 6000.5.0a1
Votes
3
Found in
6000.0.60f1
6000.2.8f1
6000.3.0b6
6000.4.0a2
6000.5.0a1
Issue ID
UUM-122608
Regression
Yes
"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
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
- Console Warning -- KeyboardIconAtlas sprite Input Outline goes beyond the boundary of the Sprite rect.
- Reflection Probe “Probe Scene Editing Mode:” text is barely visible
- [HDRP] Game view doesn’t refresh after changing Camera Background Type until mouse moves over it
- Some Shaders appear twice in Material Shader selection menu
- Editor freezes with a StackOverflowException when certain asset types are assigned to a managed component in a SubScene via AddComponentObject
Resolution Note (fix version 6000.5.0a1):
Fixed a small regression triggering these error messages
Resolution Note (fix version 6000.4.0a6):
Fixed a small regression triggering these error messages
Resolution Note (fix version 6000.3.0f1):
Fixed a small regression triggering these error messages
Resolution Note (fix version 6000.2.14f1):
Fixed a small regression triggering these error messages
Resolution Note (fix version 6000.0.63f1):
Fixed a small regression triggering these error messages