Performance : 'event' vs 'go to'

[Broken Stylus]

Assuming you don't need to pass any data through an event, which one works faster in Playmaker, to communicate between different game objects or between two FSMs on the same object?
Send event or Go to actions?

[Thore]

I have the feeling you worry about the wrong things  but I am curious to learn what you mean by "Go To" actions. What are they?

[LordHorusNL]

Are you talking about the Goto State actions?

There shouldn't be much of a difference in performance i would think.

But seeing that the Event System is the backbone of unity, this should really be your default means of communicating between FSM's and GameObjects.

I don't really use Goto State between FSM's because it just seems more messy than Send Event, but that's just me.

[djaydino]

Hi.
Go to state is perfectly fine to use and can be easier to use in some cases.
Performance should be on par (or so small of a difference that you would need 100.000 of these actions working at the same time to see a difference)

[Broken Stylus]

Okay, I was just being curious. I rarely use this goto action but it's an interesting way to drive a FSM to a specific point too without cluttering the events database.

[djaydino]

Hi.
Just a extra :

With animation events you can use 'Set State' which seems to work better than send event.

[jeanfabre]

But seeing that the Event System is the backbone of unity, this should really be your default means of communicating between FSM's and GameObjects.

The two event systems are totally different, so perfs are not linked.

Bye,

 Jean

[jeanfabre]

Hi,

 Goto will probably have an edge in perfs because it's a direct order to go to a specific state.

But still, to got to that state, the algorythm has to iterate the list of states in the fsm, and to send and event is also iterating through the state and checking if it has this event as a global event to enter.

So in the end, go with what feels right for you, both are fine.

Bye,

 Jean