Search Issue Tracker
By Design
Votes
4
Found in
5.6.2f1
Issue ID
929798
Regression
No
Dependencies in Asset Bundle Manifests are absolute paths
Asset bundle's dependencies are stored as absolute paths to bundles instead of bundle names.
Steps to reproduce:
1. Open User's project
2. In Menu Bar: Assets > AssetBundles > Build AssetBundles
3. Open Asset Bundle manifest file (for example "cube-bundle.manifest")
4. Locate line for Assets (notice: it's bundle name)
5. Locate line for Dependencies
Expected behavior: the address is bundle name.
Actual behavior: dependencies are stored as absolute paths.
Reproduced with: 2017.2.0b2, 2017.1.0f2, 5.6.1p2, 5.5.4p1.
Example:
Assets:
- Assets/AssetBundleSample/Assets/TestScene.unity
Dependencies:
- F:/Unity-Technologies-assetbundledemo-464697bcff9b/demo/AssetBundles/Windows/material-bundle
Comments (1)
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
- 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
Sam-DreamsMaker
May 30, 2018 18:02
Yes we can't make assetBundles with dependencies correctly xD