Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.4.X, 5.5.X, 5.6.X
Votes
0
Found in
5.5.2p4
Issue ID
895452
Regression
Yes
Some Asset Bundle components have different m_PathID compared to new Asset Bundle with deleted Library
1. Open project attached(AssetBundleRebuildTest1.zip)
2. Click "BuildTools/Build/Build AssetBundles for Win64" in the menu to build Asset Bundles.
3. Quit the Unity and Rename the folder of bundles what was build on the previous step.
4. Delete the Library folder and reopen the project.
5. Repeat step 2 and compare "copy_3v3_publish" of both folders.
Expected result: They will be identical.
Actual result: m_PathID is different in some places.
Reproduced on: 5.50f3, 5.5.2p4, 5.5.3f1, 2017.1.0a6.
Works fine on: 5.6.0f3.
----------------------------------------------------------
Fixed on: 2017.1.0b5, 5.6.1p1 and should also be fixed in 5.5.3p4.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mouse inputs cannot be inputted when searching the Shortcuts Menu by type "Shortcut"
- "Debug Assertion Failed!" error when launching Windows Dedicated Server Player with Script Debugging enabled
- [Cinematic Studio][3D HDRP] Shader warnings thrown in the Console window when creating a new project with Cinematic Studio template
- Autoplay is triggered on Audio Assets when changing Asset Bundle tags
- Inspector Asset Bundle section has no indication for Variants, AssetBundle is written without a space, and Variant dropdown menu is available without setting the Asset Bundle first
Add comment