Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.2, 2019.3
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.1.1f1
2019.2.0a1
2019.3.0a1
Issue ID
1152507
Regression
No
Asset bundles which include VideoClip have different CRC values when built from a different directory
How to reproduce:
1. Open the attached project ("case_1152507-CRC_2019_2.zip")
2. Build asset bundles (Toolbar -> Bundles -> Build)
3. Check CRC value inside "\Assets\Bundles\videobundle.manifest"
4. Move the project to a different location and delete "Library" folder
5. Repeat steps 1-3 and then compare the CRC values
Expected results: Both bundles have the same CRC value
Actual results: The CRC values between bundles are different
Reproducible with: 2017.4.27f1, 2018.4.0f1, 2019.1.3f1, 2019.2.0b2, 2019.3.0a2
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
- [Windows] The Unity import progress is not shown in the Windows taskbar
- Custom shader creation APIs are missing the AssetImportContext and thus can't handle includes correctly
- 2019.4: PackedMemorySnapshot: nativeObjects.gcHandleIndex contains -1 always
- [Hub] Project "Remove from list" option is behind notifications when selecting the most bottom project in the list
- [Android][Vulkan] Black Screen renders on devices with Adreno 640 and Mali GPU's
Resolution Note (fix version 2020.1):
VideoClip will now only store paths that are relative to the project root. Fixed in 2020.1.0a17
Resolution Note (fix version 2019.3):
VideoClip will now only store paths that are relative to the project root. Fixed in 2019.3.0f5
Resolution Note (fix version 2019.2):
Fixed in: 2019.2.19f1
Resolution Note (fix version 2018.4):
Fixed in 2018.4.18f1