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
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
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