Search Issue Tracker
Fixed in 2017.1.0f3
Fixed in 5.4, 5.5, 5.6
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
- Dynamic Clipping works poorly with large scenes / terrains with the pivot point is near
- [UWP] Deploying wrong architecture through device portal ends up running a different app
- [MacOS] Standalone build contains .meta files inside native plugin bundles
- Progressive lightmapper leaks memory upon subsequent scene switches and bakes
- [AssetBundle] "The referenced script (Unknown) on this Behaviour is missing!" errors when loading object from Asset Bundle
Add comment