Search Issue Tracker
Fixed
Fixed in 6000.0.38f1, 6000.1.0b6, 6000.2.0a3, 7000.0.0a19
Votes
0
Found in
6000.0.36f1
6000.1.0b4
6000.2.0a1
Issue ID
UUM-95909
Regression
No
Keyword space mismatch error is constantly appearing in the Editor Console window when shaders contain compilation errors
How to reproduce:
1. Open the attached “IN-90920.zip” project
2. Open the “MeshInstancing” scene
3. Ensure Game View is in focus
4. Open “Assets/Shaders/MeshInstancing.shader”
5. Cause a compilation error by adding random text to the “Test” Shader Pass (added “asd” at line 58 in testing)
6. Notice the “Keyword Space Mismatch” errors in the Console window
Expected result: Only expected shader errors appear
Actual result: A large number of unexpected “Keyword space mismatch” errors are constantly appearing
Reproducible in: 6000.0.36f1, 6000.1.0b4, 6000.2.0a1
Could not test with: 2022.3.57 (“missing ‘RayTracingShader’ namespace” errors)
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note: GPU with ray tracing support is required to reproduce
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
- 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
- Text Script Importer Reference button links to a Missing Page when clicking the Reference Button in the Inspector
Resolution Note (fix version 7000.0.0a19):
Fixed a bug triggering the error messages
Resolution Note (fix version 6000.2.0a3):
Fixed a bug triggering the error messages
Resolution Note (fix version 6000.1.0b6):
Fixed a bug triggering the error messages
Resolution Note (fix version 6000.0.38f1):
Fixed a bug triggering the error messages