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
- "Microsoft Visual Studio Community" module appears checked in Add modules when it was not installed
- Editor window is not opened when launching the project with 2021 or 2022 streams
- Any Unity Editor version is not uninstalled when trying to uninstall it through Unity Hub
- "Trying to access the DPI setting of a visual element that is not on a panel." warning thrown when entering/exiting Play Mode with new Hierarchy not displayed
- Transparent geometry does not render in Built-in Renderer Deferred mode when a custom post-processing effect is enabled on Mac with Metal API
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (1.0.X):
There are no fixes planned for this Bug