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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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