Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-311
Regression
No
[ECS] EnableableComponent is not ignored in EntityQuery when WithAll() is not enabled
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Scenes/SampleScene.unity” Scene
3. Enter the Play Mode
4. Observe the Console window
5. Notice the Active Component’s EnabledState is True
6. Notice the EntityQuery is reporting it affects 0 entities
7. Notice the Active Component’s EnabledState is False
Expected result: Active Component is ignored and not executed
Actual result: Active Component is executed as seen in Repro.mp4
Reproducible with: 1.0.0-pre.65 (2022.2.19f1)
Could not test with: 1.0.0-pre.47 (2022.2.19f1) (Assets\DisablerSystem.cs(31,59): error CS1503: Argument 1: cannot convert from 'Unity.Entities.EntityQuery' to 'Unity.Entities.SystemHandle')
Reproducible on: Windows 10 Enterprise 21H2
Note:
- Active Component should have been ignored because the required WithAll() flag Component was not enabled. But it seems to have been executed anyway
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
- Required SpriteMask class (ID 331) is stripped when "Strip Engine Code" is enabled
- “Maximized serialized file backup not found” error is thrown when minimizing a window in a newly opened project
- Build stack trace contains invalid lines when building with IL2CPP using scripts with delegates containing generic types in the signature
- Entities Systems window has a “Show Full Player Loop” dropdown which does nothing when clicked after enabling “Show Full Player Loop”
- Entities Hierarchy Search “Show/Hide” button’s Lens Icon is blurry when the Editor is on an external monitor
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.0.X):
There are no fixes planned for this Bug
Resolution Note (1.0.X):
The observed behavior is correct and intended, but definitely surprising. For now we've updated the API docs to better call out the unusual behavior of this function, but we'll consider a behavior change in a future package release.