Timeline events?

I may be nothing

Again, thank you!!! The realisations your plugin gave me, and your way of explaining and showing things, were truly invaluable. THANK YOU!!!!

 

Here's my contribution to the cause - a port of the conditions UI from Mecanim into the timeline.

• The track binds to an animator and uses that to populate all the current Parameters.
• Each clip can bind to an object to receive events via ExecuteEvents/Interface.

https://github.com/imxzjv/UnityTimelineConditions

EDIT link to non-bad-quality video

Code (CSharp):

1. https://streamable.com/srxk8

 

@seant_unity

These are really great solutions so far, but is there any word on native Timeline Events yet? -- It is 2018.2.3 now and I've still not heard a peep from you guys about this...

I know it's not 2018.3 quite yet (and according to your post here, it's probably still coming), but I just wanted to be sure since it seems like other "lesser" features suddenly disappear from existence too -- and with no word from anyone @Unity about their disappearance either.

Are Timeline Events still headed our way, or has there just been some delay...?

 

Wow, what a delay indeed!

Thanks for the response on this though! -- I assume a lot of internal reworking to fit in better with the new ECS "performance-by-default" approach to make it perform better (by default)? -- Or am I waaay off on this?

 

Nice! -- That's great to hear events run directly through the graph at such a low-level. I was worried this was one of those features that "missed the bus" to be integrated into the first waves of the new "performance-by-default" paradigm.

Thanks again for the clarification on this! -- It's always great to hear when systems that can work together are actually being redesigned to do so!

 

Hello people!

I came here to look for an answer or a workaround for events in the timeline, but till I read all posts I found a way. This method/workaround for using events in timeline seems a little bit more clean without a need to write additional scripts for Playable, but the functionality that you need to achieve. So let me describe it for you:

1. Write a public function that should do your functionality in a script.
2. Select the object you want to hold the Timeline. To be precise it will hold a Playable Director and an animator (you can delete the animator component, it won't be used).
3. Create a Timeline asset clicking "Create" while the recent gameobject is selected and the Timeline window opened. Name it whatever you want, I prefer calling it just Timeline.
4. Drag and drop the gameobject you want to trigger the functionality on to the timeline, when the menu appears choose "Add Animation Track". It will create an animation track in the timeline and will add the animator component to that object. Also add the script you recently wrote your functionality.
5. Open the animation window while the recent gameobject is selected. Click on "Create" to add an animation clip and name it whatever you want (prefer the action it's doing), an animator controller named same as the gameobject is also created.
6. Click on the created animation clip and uncheck the "Loop Time" property if it's not needed, in Inspector window.
7. Open the "Animator" window, click on the recently created animator controller in the "Project windows". Inside the animator window click on the animating state (the orange one by default, it's named same as the animation clip) and set the "Speed" to 0. If you leave it set to 1 it will play the animation when you click Play.
8. In the hierarchy windows again select the gameobject, while the animation window is opened. In the animation window select whatever frame you need to be the trigger on, click on the "Add event button".
9. In the inspector select the function you need to be triggered.
10. Let's go back to the timeline where your animation tracks are. On the track section underneath the time section right-click and select "Add From Animation Clip" and choose your animation clip.
11. The animation clip in the timeline will trigger the event.

So you can create an event trigger inside the Timeline. This method seems a good one for me, at least I can do the things I need this way. It would of course be a much more efficient way if there is an UI for this, but it's up to someones work to make that happen. I'm just sharing what I could do to make it happen. Sharing is caring Hope it will help ya'll.

 

Thank you for sharing this. It's a great implementation of the Event system. You would think Unity could build something like this pretty easily with all of the support they have. Not to mention it's essentially a critical feature for any timeline system.

 

when is 2019.1? A few people are asking me about my timeline events unity package. Don't want to get them using my system if it's not necessary.

 

(obviously in beta before these dates)
2018.1 was 2nd May
2017.1 was 10th July

So, one could assume around the same time next year for 2019.1

 

If anyone is interested, Timeline events are going to be included in the next public alpha of Unity 2019.1: 2019.1.0a10.

 

Woohoo! Thanks for the news. There are many third party solutions for this but an integrated one will be most welcome.

 

Looks like this thread was heavily "cleaned up". I distinctly remember some unhappy campers in this thread who were not pleased to have to wait till 2018.3... but now they won't even be in a 2018 release? Any technical reason why?

Also, some useful posts have gone missing here too...

 

Unity 2019.1.0a10 with support for Timeline Events is out.

 

Has anyone heard if Timeline Events will be backported to 2018 .3 or .4 as mentioned by @seant_unity previously?

 

Thanks for the clarity, @seant_unity.

Out of curiosity -- is there a technical reason for this particular decision, or is it just policy?

We had planned (for quite some time) to stick with 2018.3/4 (for LTS), aiming to have native support for Timeline Events (before starting heavy development in this area because we knew that 2019 would be a very rocky transition with the inclusion of nested prefabs and the universal transition to ECS + jobs system).

I imagine others here were thinking a similar thing, so I thought I'd ask. We clearly need to better-gauge our future development decisions on Unity's thinking in regard to its "in-development" features, as this is a point of mystery to most smaller developers I've talked to who aren't "in the know" with Unity itself. Some insight into your thinking process would be great.

 

That's fair -- I thought this was the case.

I've heard other users complaining about how slow things have been over the years, and as such, a so-called "simple feature" such as Timeline events was hard for me to justify its pacing without knowledge of the goals behind the feature.


That said, regarding future "in development" features, I think modifying the Roadmap might end up only being a "band-aid" to the larger problem of users not always knowing what direction their favorite features might take. Having a better (global) idea of the internal goals (and a clearer idea of potential roadblocks) of specific features might better-help users than an ETA or detailed-description of a "feature" might encompass. The new Input System is a great example of offering a better overview with potential roadblocks.

Just my two cents though!

@seant_unity -- Thanks for all your (and the entire Unity Team's) hard work on bringing Unity to modern times. It's really becoming the ultimate engine for realtime creation thanks to you guys, and it's a rewarding feeling to be part of that as a user too.

 

Will we be able to pass data through signal emitters? A value can be passed into method arguments via the signal receiver, but this means emitters of the same signal type will always pass the same value.

Basically I'd like to be able to define some set of variables for each signal, set their values for each emitter in its inspector, then pass these variables to methods in the signal receiver. This way we wouldn't have to create a separate signal/reaction pair for every possible value.

 

Might it be worth it to give an example of this?

Seems kind of convoluted, and to expect many users to figure this out without some explanation... D:

 

Excellent news!

 

Outstanding!

 

For people using versions below 2019.1, this may help:

Put this in a Script and attach it to a Gameobject you activate/ deactivate via Timeline (at least it's something):

using UnityEngine.Events;

Code (CSharp):

1.  
2.     [SerializeField]
3.     private UnityEvent onEnable;
4.     [SerializeField]
5.     private UnityEvent onDisable;
6.  
7.     private void OnEnable() {
8.          CallEvent(true);
9.     }
10.  
11.     private void OnDisable() {
12.          CallEvent(false);
13.     }
14.  
15.     public void CallEvent(bool _event) {
16.         if (_event) {
17.             onEnable.Invoke();
18.         } else {
19.             onDisable.Invoke();
20.         }
21.     }

You can actually create a List<UnityEvent> and handle an increment every Enable/Disable, so you have one Object, not thousands...

-> the only thing, you cant see it in the preview (only if you put more affort in it)
hope i could help

 

Hi guys,
some months ago I started my own Timeline events system for a commercial project I was working on.
Since it was the heart of the game I decided to make it solid and easy to use.
This system is capable of invoking custom functions and also passing scene objects to them.
It's 100% reliable therefore hicups or framerate drops won't prevent events from firing.
It doesn't use 2019 signals. (compatible with Unity 2017)

It's not free but maybe you could find it useful

https://assetstore.unity.com/packages/tools/integration/timeline-ez-events-126484

 

Please tell me this wasn't Timeline Signals... Or was it?

Are we looking at doing anything with Timeline and DOTS / ECS at some point?