Search Issue Tracker
Fixed
Fixed in 1.19.2
Votes
0
Found in [Package]
1.18.2
1.19.0
Issue ID
BPSBP-106
Regression
No
Addressable Scenes in groups that are packed separately lose their references when they are loaded
Reproduction steps:
1. Open the User's attached "AddressableIssue.zip" project
2. Go Window -> Asset Management -> Addressables -> Groups
3. Ensure that Play Mode Script is set to "Use Existing Build" and go Build -> New Build -> Default Build Script
4. Open the "InitialScene" Scene and enter the Play Mode
5. Observe the shape in the Game View
Expected result: The shape is empty in the middle
Actual result: The shape is full
Reproducible with: 1.18.2, 1.18.11 (2018.4.36f1, 2019.4.29f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0a20, 2022.1.0a2)
Not reproducible with: 1.17.17 (2018.4.36f1, 2019.4.29f1, 2020.3.14f1, 2021.1.15f1, 2021.2.0a20. 2022.1.0a2)
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
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Resolution Note:
Fixed an edge case with NONRECURSIVE_DEPENDENCY_DATA in which Scene Bundles would be unable to load MonoScripts and log Missing Behaviour warnings at runtime.
Resolution Note (fix version 1.19.2):
Resolved previous to port addition.
Resolution Note:
Resolved previous to port addition.