Search Issue Tracker
Won't Fix
Won't Fix in 1.19.X
Votes
0
Found in [Package]
1.19.3
Issue ID
BPSBP-216
Regression
No
Scriptable Build Pipeline results in null script and object references in prefabs loaded from Asset Bundles
Reproduction steps:
1. Open the "P3_pached.zip" project
2. Switch project to Tools -> Build Defines -> USE_SCRIPTABLE_BUILD_PIPELINE
3. (this step can be skipped if using "P3_pached.zip") Build asset bundles (Assets -> Bundles -> Batch Mode -> Run Auto Batch Mode Builder, in the pop-up, select "Include All")
4. Enable Asset Bundle use in the editor (Assets -> Bundles -> Open Asset Bundle Utility Window, and change "Asset Loader Mode" to Manifest)
5. Enter the Play Mode
Expected result: No errors in the Console
Actual result: Errors, related to Scriptable BuildPipeline, in the Console
Reproducible with: 1.2.1-preview (2019.4.32f1, 2020.3.23f1), 1.19.3 (2019.4.32f1, 2020.3.23f1)
Could not test: 2021.2.2f1, 2022.1.0a15 (errors in console and custom tools are gone)
Notes:
- Removing the Library folder causes the reported error to not appear and entering the Play Mode is stuck on Loading...
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
- Crash on PrepareDrawShadowsCommandStep1 when entering the Play Mode in a specific project
- Physics Layer Collision Matrix's Layer names, checkboxes and hover highlights become misaligned when the Editor's UI Scaling gets changed
- Light/shadow information on an edge of a Terrain tile creates a seam with an adjacent Terrain tile when baking a LightMap
- "Missing types referenced from component UniversalRenderPipelineGlobalSettings on game object UniversalRenderPipelineGlobalSettings..." warning is thrown after switching the Platform to tvOS
- “Metal: Error creating pipeline state (Universal Render Pipeline/2D/Sprite-Lit-Default): Vertex attribute BLENDINDICES0(5) of type uint4 cannot be read using MTLAttributeFormatFloat2 (null)“ when setting GPU Skinning to GPU after opening the project
Resolution Note:
Looks to be an issue in the user project and the integration of SBP.
I think the user project needs debugging to see why the bundle dependencies which are generated at build time are not present in the manifest data when loading at runtime.
Resolution Note (1.19.X):
This looks be a customer project issue not an SBP issue
I think the user project needs debugging to see why the bundle dependencies which are generated at build time are not present in the manifest data when loading at runtime.