Search Issue Tracker
By Design
By Design in 1.21.X
Votes
0
Found in [Package]
1.21.1
Issue ID
ADDR-3086
Regression
No
Scene is in Hierarchy but not visible in Game view when loaded with “Addressables.LoadSceneAsync”
Reproduction steps:
1. Open the attached “AddressablesLoadScene.zip“ project
2. Open “SampleScene” scene
3. Enter Play Mode
4. Observe Game window
Expected result: “AddressableScene” is visible in Game view and Hierarchy
Actual result: “AddressableScene” is visible in Hierarchy view but is not visible in Game view
Reproducible with: 1.18.19 (2020.3.42f1), 1.19.19 (2021.3.14f1, 2022.1.23f1), 1.21.1 (2022.2.0b16, 2023.1.0a20)
Reproduced on: macOS Monterey 12.6 (Intel)
Note: Also reproducible in 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
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
There is no issue here. The LoadSceneAsync method is being called using LoadSceneMode.Additive, this means that the scene is loaded in addition to any other loaded scenes. If the user wants to only have the new scene to be active. Then LoadSceneMode.Single (or nothing passed) is needed
Resolution Note (1.21.X):
There is no issue here. The LoadSceneAsync method is being called using LoadSceneMode.Additive, this means that the scene is loaded in addition to any other loaded scenes. If the user wants to only have the new scene to be active. Then LoadSceneMode.Single (or nothing passed) is needed