Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X
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
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Windows player with a custom .exe file crashes in FixupD3D12SDKPath
- "Property exceeds previous array size (2 vs 1)" warnings are thrown making it impossible to work with the Update Zones of the CustomRenderTexture when updating the script
- Bug Reporter recommends invalid discussion links when writing a Title of the issue
- Freeze when calling Rigidbody.SweepTestAll in a specific project
- Crash on UI::RectTransform::SetDrivenByObject when rapidly undoing copies of a specific GameObject
Add comment