Search Issue Tracker
Fixed
Fixed in 6000.1.0b4, 7000.0.0a20
Votes
0
Found in
6000.1.0a10
7000.0.0a20
Issue ID
UUM-91635
Regression
Yes
"Incompatible keyword states" error is thrown for shaders when launching the editor.
How to reproduce:
1. Open the attached “IN-90989_XRacer“ project
2. Navigate to console and observe.
Expected result: Nothing of note happens
Actual result: The console shows “Incompatible keyword states“ error
Reproducible with: 6000.1.0a4, 6000.1.0a10
Not reproducible with: 2021.3.47f1, 2022.3.55f1, 6000.0.33f1, 6000.1.0a3
Fixed in: 2022.3.29f1, 6000.0.1f1
Reproducible on: MacOS 15.1.1 (M1 Max)
Not reproducible on: No other environments tested
Notes:
- If it doesn’t reproduce, just close the editor and open it again.
- It was a bug before and it was fixed for previous streams but it regressed from 6000.1.0a4 in 6000.1 stream.
- Link to the Issue Tracker for the Related Case:
[https://issuetracker.unity3d.com/issues/material-using-a-particle-standard-unlit-shader-with-rendering-mode-set-to-fade-additive-or-subtractive-causes-console-errors-to-be-thrown-when-the-editor-is-active]
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note (fix version 7000.0.0a20):
A specific condition with terrain shaders and UsePass triggered a case where some keyword related data was copied around before it was fully ready. This is now avoided by doing things in a different order.
Resolution Note (fix version 6000.1.0b4):
A specific condition with terrain shaders and UsePass triggered a case where some keyword related data was copied around before it was fully ready. This is now avoided by doing things in a different order.