Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
2018.4.0f1
2019.2.0a1
2019.3.0a1
2019.3.0b4
2020.1.0a1
Issue ID
1186280
Regression
No
Custom Timeline Tracks with class name different than the file name loaded from AssetBundles show up as "Track cannot be loaded"
How to reproduce:
1. Open attached project
2. Open "Assets/Player/Player" Scene, check CopiedDirector Timeline
3. Enter the Play Mode
Reproducible with: 2018.4.10f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a6
Not reproducible with: 2017.4.32f1(due to different Prefab system)
Expected results: The tracks are loaded properly.
Actual result: The tracks are not loaded and an error "Track cannot be loaded" is shown
Reproducible with all Timeline Package versions
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
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
- Shortcut Manager shows empty conflict filter when resolving runtime conflicts involving different contexts
Resolution Note:
The class name of any scriptable objects (this includes custom tracks and custom clips) needs to match the file name in Unity to be serialized correctly. This is a requirement of Timeline, because it is a general requirement in Unity.