Search Issue Tracker
By Design
Votes
0
Found in [Package]
0.16.0-preview.21
Issue ID
1293511
Regression
No
[ECS] ArgumentException is thrown when EntityCommandBuffer.DestroyEntity is used
How to reproduce:
1. Open the user's attached project("Iteration3-Jobs.zip")
2. Enter Play mode
3. Wait a couple of seconds
4. Press the left mouse button on the Plane
Expected results: ArgumentException is not thrown because Entity in CommandBuffer is not null
Actual results: ArgumentException is thrown
Reproducible with: 2020.2.0b14 (ECS 0.16.0-preview.21)
Couldn't test with: 2018.4.30f1, 2019.4.16f1, 2020.1.16f1, 2021.1.0a8 (Couldn't upgrade/downgrade)
Note: Does not reproduce if EntityManager is used directly
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:
The root of the error is that the user is creating temporary Entity ids (entity ids with negative indexes) with one ECB, then recording commands using these temporary Entity ids in another ECB. This is never valid.