Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2021.2.0a16
2021.2.0a17
Issue ID
1338318
Regression
Yes
'Incompatible keyword states' errors spammed to console after a Unity update to 2021.2.0a16 or later
How to reproduce:
1. Download the attached project "Wolf_2021_1.zip"
2. Open in it with Unity 2021.2.0a16
Expected result: No or more detailed errors are printed to the Console
Actual result: 'Incompatible keyword states' is spammed to the Console
Reproducible with: 2021.2.0a16, 2021.2.0a17
Not reproducible with: 2019.4.27f1, 2020.3.11f1, 2021.1.9f1, 2021.2.0a15, 2021.2.0a18
Could not test with: 2018.4.34f1 (errors downgrading)
-
atr0phy
Jun 15, 2022 20:37
Happening also in 2022.1
-
solkyoshiro
Apr 04, 2022 16:20
This is happeneing agian in 2021.2.18f1
-
StarFluke
Jan 15, 2022 16:25
This is happening again in 2021.2.7fi and 2021.2.8f1.
-
Peter77
Jun 05, 2021 04:05
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.2):
Does no longer reproduce with: 2021.2.0a18