Search Issue Tracker
Fixed
Fixed in 2022.3.29f1, 6000.0.1f1
Votes
0
Found in
2022.3.17f1
2023.2.6f1
2023.3.0b3
6000.0.0b11
Issue ID
UUM-60832
Regression
Yes
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
How to reproduce:
1. Open the “Game Feel.zip“ project
2. Observe the Console
Expected results: No Console errors are thrown
Actual results: “State comes from an incompatible keyword space” and “Incompatible keyword states“ errors are thrown whenever the Editor is active
Reproducible in: 2023.3.12f1, 2022.3.17f1, 2023.2.6f1, 2023.3.0b3
Not reproducible in: 2021.3.34f1, 2022.3.11f1
Reproduced on: Windows 11
Not reproduced on: No other environment tested
Notes:
-The errors are thrown endlessly
-Reproduces only in the user's project
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
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment