Search Issue Tracker
Fixed
Fixed in 1.2.0-pre.12 - Entities
Votes
1
Found in [Package]
1.2.X
Issue ID
ECSB-946
Regression
No
"HasSingleton" and "GetSingleton" are not consistent with each other
How to reproduce:
1. Open the user’s attached “SingletonIssue.zip” project
2. Enter Play Mode
3. Observe the Console window
Expected result: Logs are: “HasSingleton says True” and “GetSingleton returns 1 which is expected to be 1”
If GetSingleton is supposed to work in a Query context, respecting enabled states.
or
“HasSingleton says False” and “GetSingleton throws”
If GetSingleton is supposed to work only in a World/Archetype context, disregarding enabled states.
Actual result: Logs are: “HasSingleton says True” and “GetSingleton returns 0 which is expected to be 1”
Reproducible with: 2022.3.20f1, 2023.2.10f1, 2023.3.0b7
Could not test with: 2021.3.35f1 (Errors after project downgrade)
Reproduced on: macOS 14.2.1 (Intel)
Not reproducible on: No other environment tested
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
- Any small change in UI Builder Inspector refreshes Editor Inspector
- Inaccurate Box Collider boundaries on a rotated child Cube when the parent GameObject Scale is non-uniform
- [Android] "SHADOWS_SCREEN" set as shader Keyword when no "_ShadowMapTexture" is bound leads to freeze on a build on some Mali GPU devices
- The global scene list is overridden in a project built with command line when the Override Global Scene List setting is disabled in the build profile
- Global Scenes are not included in the Build when building multiple Build Profiles at the same time
Resolution Note (fix version 1.2.0-pre.12 - Entities):
Fixed in: 1.2.0-pre.12