Search Issue Tracker
Fixed in 0.14.0-preview.18
Votes
0
Found in [Package]
0.13.0-preview.24
Issue ID
1267160
Regression
No
[ECS] SystemState components may not be removed via SetArchetype error when not removing SystemState
Reproduction steps:
1. Open attached project "SetArchetype.zip" and scene "SampleScene"
2. Enter Play Mode
3. In Game View, click the "Hit this" button
4. Observe Console window
Expected result: No error message
Actual result: "ArgumentException: SystemState components may not be removed via SetArchetype" error message
Reproducible with: 2019.4.7f1, 2020.1.1f1, 2020.2.0a20 (ECS 0.13.0-preview.24)
Note:
Issue reproduces with Burst enabled
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 0.14.0-preview.18):
There was some incorrect iteration of the archetypes when a system state component was involved. Depending on the ordering of these archetypes it would incorrectly fail to find the system state component in the user's new archetype. This has now been resolved