Search Issue Tracker
Won't Fix
Won't Fix in 1.0.X
Votes
0
Found in [Package]
1.0.0
Issue ID
ECSB-170
Regression
No
The same entities are yielded when using 'SetSharedComponentFilter' with two different SharedComponent values
How to reproduce:
1. Open the attached user project “dotsnav - f1.zip“
2. Open Scene "RVO Circle Test" (Assets/Development/RVO)
3. Enter Play Mode
4. Select the four GameObjects named "Poly" and disable, enable, and disable them again
Expected result: The filter works and assigns the correct SharedComponent values (“filtering Entity(56:1): Entity(59:1), Entity(60:1)” and “filtering Entity(57:1): Entity(58:1), Entity(61:1)” should be logged in the Console)
Actual result: The filter doesn’t work and doesn’t assign the correct SharedComponent values (“filtering Entity(56:1): Entity(59:2), Entity(61:2)” and “filtering Entity(57:1): Entity(58:2), Entity(60:2)” is logged in the Console)
Reproducible with: 1.0.0-pre.15 (2022.2.2f1, 2023.1.0a24)
Can’t test with: 0.51.0-preview.32, 0.51.1-preview.21 (2020.3.43f1, 2021.3.16f1), 1.0.0-pre.12 (2022.2.2f1, 2023.1.0a24) (Errors in the Console)
Reproduced on: macOS 13.0.1 (Intel)
Note:
- This issue does not occur when the GameObjects start disabled, or when using one obstacle per NavMesh
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
- "IndexOutOfRangeException" and "NullReferenceException" are thrown and Element disappears from UI Builder when undoing rename of element in "Open Instance in Context" menu
- Select Scriptable Object window freezes and becomes unresponsive when currently opened UXML Template is selected for binding's Data Source
- [Linux] “ReleaseButton expects buttonId >= 0” error is thrown when importing Assets via drag and drop
- Asset gets unselected and added Subgraphs list item is not undone when performing Undo in Heatmap with Default Values asset Inspector
- Black square “shadow” artifacts visible when using Screen Space Reflections without maximum smoothing
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.0.X):
There are no fixes planned for this Bug