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
- FP32 is used for a temporary when compiling a shader for GLES or Vulkan
- The highlight that was created with Highlighter.Highlight does not disappear when the window is closed with the element
- [URP] CommandBuffer warnings thrown while debugging Depth Overlays with Post-processing enabled in Rendering Debugger
- An Unhandled exception is thrown in the Editor.log and Console window when trying to build AssetBundles
- InterlockedExchange function throws an error when using floats as arguments
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.