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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note (fix version 1.2.0-pre.12 - Entities):
Fixed in: 1.2.0-pre.12