Search Issue Tracker
Fixed
Fixed in 1.20.2
Votes
1
Found in [Package]
1.19.6
Issue ID
BPSBP-335
Regression
Yes
Asset bundles lose reference to Prefabs when Scenes are built in a specific order (ScriptableBuildPipeline)
Reproduction steps:
1. Open the attached "1410524.zip" project
2. Delete the "scenes.bundle" asset in the Assets > StreamingAssets
3. In the Build Settings window make sure that the Scenes are in the order: MainMenu, LoadingScene, BoatTrip
4. Go to Asset Bundles > Build Asset Bundle
5. Open the "MainMenu" Scene and enter the Play mode
6. Observe the Console window
Expected result: Public link to a Prebaf called "Player" isn't lost and the "The bug hasn't happened\!" error message appears
Actual result: Public link to a Prebaf called "Player" is lost and the "The bug has happened\!" error message appears
Reproducible with: 2021.1.0a7, 2021.2.16f1, 2022.1.0b12, 2022.2.0a9
Not reproducible with: 2019.4.36f1, 2020.3.31f1, 2021.1.0a6
Note: The issue is not reproducible when Scenes are in the order: MainMenu, BoatTrip, LoadingScene
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 1.20.2):
Fixed an issue where Scene build ordering would cause Scenes to not load.