Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
Votes
0
Found in
2019.1.0a11
2019.1.0f2
2019.2.0a1
Issue ID
1148709
Regression
No
[Timeline] Changing the Emit Signal property of a Signal Emitter does not mark the Timeline as dirty
How to reproduce:
1. Open the attached "case_1148709-EmitSignalNoSave" project
2. Open the "New Timeline" in Timeline Window
3. Select the Signal Emitter marker and change the Emit Signal property from "Signal1" to "Signal2"
4. Close and reopen the project, then inspect the Signal Emitter again
Expected results: The Emit Signal property is set to "Signal2"
Actual results: The Timeline asset did not get marked as dirty, therefore the Emit Signal property did not get saved and is still set to "Sginal1"
Reproducible with: 2019.1.0f2, 2019.2.0a13
Note:
1. Could not test with 2019.1.0a10 and below as Timeline Signals were introduced in 2019.1.0a11
2. Changing anything else in the Timeline (f.e. adding a Track or another Signal Emitter) causes the changes in "Emit Signal" properties to be saved
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Surface Inputs are not rendering when using the custom BaseShaderGUI
- Reflection Problem custom Cubemap loses its reference when HDR is enabled and the platform is switched
- [macOS] "Add Component" button is broken when the Editor is moved to a different MacOS workspace
- Player settings icons are not retrieved when using "PlayerSettings.GetIcons" method on PS4, PS5, Xbox
- Changes of MaterialPropertyBlock via Script reset when Sprite Renderer.Color is changed in animation
Add comment