Search Issue Tracker
Fixed in 2019.3
Fixed in 2018.4, 2019.2
Votes
0
Found in
2017.4.12f1
Issue ID
1087082
Regression
No
Video Clip fails to upload to Cache Server when upgrading an old project to a newer version of Unity
Steps to reproduce:
1. Open user attached project
2. Enable cache server in Preferences settings
3. Right-click on the clip in the Assets folder -> Reimport
Expected result: the clip is reimported without error, and relevant files are cached on the Cache Server
Actual result: the clip is reimported with the console error, and no files are cached on the Cache Server
Reproduced in 2017.4.14f1, 2018.1.9f2, 2018.2.14f1, 2018.3.0b8, 2019.1.0a6
Note: You can fix the issue by enabling and disabling transcoding.
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
- [Linux] Unity licensing command on Linux pops a progress bar when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
- Frame Debugger doesn't work when using Camera.SetTargetBuffers
Resolution Note (fix version 2019.3):
Clips with transcode disabled (the default state) failed to upload to cache server if they have not been transcoded at least once. Removed this unwanted requirement.