Search Issue Tracker
By Design
Votes
0
Found in [Package]
1.5.1-pre.3
Issue ID
1299875
Regression
No
Listeners are not triggered when SignalReceiver is added in runtime
How to reproduce:
1. Open the user's attached project ("CinemachineSignalCrash.zip")
2. Remove the "SignalReceiver" component from "Cube (1)"
3. Enter Play mode
Expected result: When no Signal receiver is attached the script adds the component. This SignalReceiver should then act the same as the SignalReceiver added in the inspector. The listeners added in runtime should be triggered when the signal emitter is reached in the timeline.
Actual result: The listeners added in runtime are never triggered.
Reproducible with: 2019.4.17f1, 2020.1.17f1, 2020.2.1f1, 2021.1.0a10, 2021.2.1.0a1 (Timeline 1.2.17 - 1.5.1-pre.3)
Could not test with: 2018.4.30f1 (Errors downgrading)
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
- Font character thickness does not adjust properly in UI Toolkit text when changing Bold Weight in Font Asset
- Multiple "[...] is inaccessible due to its protection level" errors are thrown when opening project with Unity Version Control installed
- Sorting icons are tiny and misaligned in Import Activity window
- The Undo system does not record HideFlags.HideInHierarchy changes
- [Linux] Bug Reporter window is in Light mode when the Editor theme is Dark mode
Resolution Note:
Signal receiver discovery is not automatic, as it has a cost.
You need to call RebindPlayableGraphOutputs (https://docs.unity3d.com/ScriptReference/Playables.PlayableDirector.RebindPlayableGraphOutputs.html) in order to bind the new signal receivers