Search Issue Tracker
Fixed in 2019.3.X
Fixed in 2019.1.X, 2019.2.X
[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
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.
- [Windows 11] Package Manager Features are displayed incorrectly after moving the mouse
- Android Install Location changes when Exporting Project
- [Silicon] Crash on ScriptableRenderLoopJob when machine is left idle while the Editor is in Play mode
- [Android] GraphicsBuffer.CopyCount does not work with Append Compute Buffer after Compute Shader Dispatch on some Android devices
- "DirectoryNotFoundException" error when building a project via script in one folder, then building via Editor in another, deleting the folder built via Editor and rebuilding via Script