Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.1p2
Issue ID
920288
Regression
No
Having two scenes with the same filename in one bundle would cause errors when building the bundle (Fix suggested)
Open the attached project:
1. Open the attached project.
2. Go to Bundles > Build.
3. Check the Console:
Assertion failed: Assertion failed on expression: 'srcFileInfo.temporaryObjectIdentifier.localIdentifierInFile == localIdentifierInFile'
UnityEditor.BuildPipeline:BuildAssetBundles(String, BuildAssetBundleOptions, BuildTarget)
Reproduced with:
5.5.0f1, 5.6.1p3, 2017.1.0b9, 2017.2.0a3
Notes:
- To avoid the issues go to Test > Run (Windows).
- Check the user patch (attached in this case) (1:50 AM).
- Full paths are always checked first to avoid a short name blocking a scene. For
example if you have in your build settings:
A/A.unity
A.unity
The latter couldn't be loaded. With this change, "A" will load the second, and only
"A/A" will load the first.
- Having two scenes with the same filename in one bundle would cause errors when
building the bundle.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment