Search Issue Tracker
By Design
Votes
0
Found in
2019.2
2019.3
2019.3.0f3
2020.1
Issue ID
1214233
Regression
No
Timeline Signals are not received by Signal Receiver when TimelineAsset is loaded from an AssetBundle
Reproduction steps:
1. Open user's attached project "Timeline asset bundle bug" and scene "MyScene"
2. Enter Play Mode
3. Press "Load timeline from asset bundle"
Expected result: Timeline Signals are received by the Signal Receiver and logged
Actual result: No Signals are received by the Signal Receiver
Reproducible with: 2019.2.20f1, 2019.3.0f6, 2020.1.0a21
Could not test with: 2017.4.36f1, 2018.4.16f1 (project breaks)
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.1.X):
The signal asset loaded by the assetbundle is a clone of the one in the project. Thus the signal receiver, being part of the scene, is no longer linked to it. To maintain the link between the signal receiver and the signal, the signal receiver must be also added to the asset bundle, for example, as a prefab. Another workaround is to rebind the signal receiver to the signal assets loaded in the asset bundle using the signal receiver API.