Search Issue Tracker
Fixed in 1.4.1
Votes
0
Found in [Package]
1.2.0
Issue ID
1257208
Regression
No
[Timeline] Timeline Signal gets called twice when the Signal is in frame 0
Reproduction steps:
1. Open the attached project "TimelineSignal.zip"
2. In the Project window under "Scenes" open "SampleScene.unity"
3. Enter Play Mode
4. The Signal track will activate and a message is printed out in the Console window
5. Press the Button in the Game view to see the same message being printed out again
Expected result: Timeline Signal does not get called twice when the Signal is in frame 0
Actual result: Timeline Signal gets called twice when the Signal is in frame 0 (See attached TimelineSignal.mp4)
Reproduces on: Timeline 1.2.0 (2019.3.0a1), Timeline preview.2 - 1.5.0 (2019.4.2f1, 2020.1.0b14, 2020.2.0a16)
Could not test 2018.4 (No Signal Track)
Notes:
-Issue is still present if Emit Once property is checked
-Issue does not reproduce if Signal gets called in frame 1 and above
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Add comment