Is it possible to have 2 event ticks?
I am using an event tick for my movment... How can I Use another event tick for other things? Is it possible to have multiple ticks for one event? I can't fork an event tick.
You can create multiple tick events by creating custom events like so:
I don't know if that's the most efficient way to do it, but it does the trick!
answered Apr 24 '14 at 06:22 AM
what that function called???
in the top pict.. i want to create Tick > for new 2 tick..
what the function??
answered Dec 23 '15 at 09:26 AM
You can't have multiple tick events and you cant multithread it aspecially in blueprint. There is Sequence node which will call one segment of the code after another, but you need to decide the order of execution
Not only should you not want 2 Ticks, you should never want ANY Ticks.
Check out Timelines. These are what you use when you need a perpetual process. Why? They can be started and stopped at any time, meaning you can save processing when their corresponding functions aren't needed.
Also, they're AWESOME! You can set the length of the Timeline you create to anything, or you can set it to loop so it goes until it's stopped. You can even create graphs and set specific times for new events to fire off within the Timeline editor and output those values from it! If that's not enough, you can stop and start again where it left, start from the beginning, reverse it from the point it stopped, or do a pure reverse from the beginning. They're incredibly useful.
Save your Tick for printing string values of input and stuff like that. Even when you're testing new mechanics, though, use Timelines instead of Tick. It'll be more frustrating to go back later and change your systems when you're optimizing for performance. Do it now, learn it now, and build everything with solid foundations.
Trust me on this. We gained huge performance boosts by eliminating literally all instances of Tick and replacing them with event-triggered Timelines.
Here's a link to the Timeline documentation:
You could also use a Sequence node that you connect to (the single) tick. It can execute multiple things one after the other. So you don't have to do ugly things like connecting them one after the other or using custom events, which will have the same effect as a simple sequence node.
answered Oct 02 '15 at 05:28 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here