Search Issue Tracker
Fixed
Votes
0
Found in
6000.0.26f1
6000.1.0a3
Issue ID
UUM-87251
Regression
Yes
"State comes from an incompatible keyword space" errors are thrown when saving changes in Shader Graph where sprite is casted as a shadow
Steps to reproduce:
1. Open the attached “IN-88166.zip” project
2. Open the “SampleScene”
3. Open Assets → Shaders → “SpriteShadowShader.shadergraph”
4. Select “Graph Settings”
5. Edit any variable
6. Save the Shader Graph
7. Change to Scene View
8. Observe the Console Window
Expected result: No errors are thrown
Actual result: “State comes from an incompatible keyword space“ error is thrown
Reproducible in: 6000.0.0b16, 6000.0.26f1, 6000.1.0a3
Not reproducible in: 2021.3.45f1, 2022.3.52f1, 2023.2.19f1
Couldn’t test in: 2023.3.0a2, 6000.0.0b15 (because Shader Graph package didn't work correctly)
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
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
- Group Node name text is way smaller in the renaming state than the actual display size
Resolution Note:
Fixed by another internal issue: UUM-87539: "State comes from an incompatible keyword space" error is thrown when using the editor