Search Issue Tracker
Fixed in 2022.3.54f1
Fixed in 6000.1.0a7
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (fix version 2022.3.54f1):
Fixed by another internal issue: UUM-87539: "State comes from an incompatible keyword space" error is thrown when using the editor
Resolution Note (fix version 6000.1.0a7):
Fixed by another internal issue: UUM-87539: "State comes from an incompatible keyword space" error is thrown when using the editor