Search Issue Tracker
Duplicate
Votes
1
Found in [Package]
1.0.0
Issue ID
ECSB-145
Regression
No
[DOTS] Sub-assets can't be accessed from WeakObjectReference when referenced by the main asset
Steps to reproduce:
1. Open the “retest1” project
2. Select “asseta” ScriptableObject in Assets folder
3. In the Inspector window change Sub property to “ “ ScriptableObject
4. Build and run the project
5. Close the built project
6. Observe Player.log file where the lines start with “Loaded component A”
Expected result: Both return loaded components as “non-null” true
Actual result: The first loaded component is “non-null” false, and the other one is true
Reproducible with: 1.0.0-pre.15 (2022.2.1f1, 2023.1.0a24)
Could not test with: 2020.3.43f1, 2021.3.16f1 (1.0.0 Entities package is not supported)
Reproduced on: macOS Monterey 12.2 (Intel)
Note: The issue is only reproducible in a build
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
- On Script import/reimport MonoImporter does not generate consistent results due to updating Custom packages
- [Entities Graphics] Size of the Content Update generated folder increases when changes are made to the Scene
- In Play Mode, an extra Sync Call is made every frame when a GameObject has a Rigidbody 2D component
- Crash on block_remove when a scene is opened in a specific project
- The GameObject with a Hinge Joint Component does not return to the initial position when the Use Motor property is toggled off
Resolution Note:
It's a duplicate of UUM-24989. It has been fixed already.
Duplicate of another internal issue: UUM-24989: Null reference when loading from Content Archives