Search in

Sort by:

Everything Bug Reports

Current Space

Question Status:

All Questions With Answer With Accepted Answer

Quick results

Search help

Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both.
Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.

You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with
each other. Examples

Thanks for the report! I wasn't able to find any reason Timelines can't exist in a Script Component Blueprint, so I've entered a bug report (UE-14962). I'll let you know when I see any update. Thanks again!

Well, I am trying to build reusable components to manipulate parent actors in UE4... ;) That's what they intended for, aren't they? As blueprints itself still aren't composable, that's pretty much the only way without C++, I fear. I really can't see the reason why asynchronous operations like timelines shouldn't work in principle, at least for actor-, or scene Blueprint scripts.

Sounds more like an internal problem with the architecture of the engine to me. I don't have the necessary background knowledge but I really don't think this restriction is only a matter of logic?

I spoke with one of our Sr Programmers about it some more. He told me it's "mostly a matter of plumbing":

"Components are special in our hierarchy, in that they're Objects, but they inherit a bit of functionality from Actor.

"Timelines are components, and can now be added to other components, but this isn't set up in Blueprints yet. It's a matter of making sure that the two different attachment / ownership paths (actors owning components, and components owning other components) both work.

"The second part of the issue is that components aren't ticked the same way that Actors are: they get their tick from their parent. So, we'll have to do a bit more plumbing to make that work.

"Not that any of this is impossible, it just needs a bit of reworking to make it happen.

"As a workaround, he could use the component's tick function to manipulate it's parent function per-frame to the same end. He just won't have the nice curve editing tool in the timeline unless he uses an external curve."

Seven versions and year and a half later, still no timelines in components. Can we please have an update on the issue? It's one of the first things I've ran into by trying to keep things modular. Thank you.

So the issue was just deleted? I'm not upset so much about the object/timeline thing (although... 3 freaking years... shiny features are shiny, but Tech Debt deserves some love too), but more about the fact that we can see in this thread a user who abandoned the engine after 40+ bugs were accepted and never updated, and that the issue you posted is no longer valid.