Can I avoid calling LogTransition?

[yamada]

Hello

Is there a way to not call LogTransition?

Currently, when the state transitions, the DoTransition method is called, and I think there is a LogTransition method in it.

The processing load of the LogTransition method is heavy and troublesome.
If you change the state to one frame, it will be quite heavy.

Is there a solution for this?

Also, is the LogTransition method heavy only in the editor and not in the package that was built?
For example, iOS, Android

[jeanfabre]

Hi,

 Are you sure you are on the right forum? Playmaker doesn't have any such thing as LogTransition.

Bye,

 Jean

[yamada]

Hello

Thank you for your reply.

As in the attached image, there is an Fsm.ProcessEvent method in the Fsm.Event method, and there is an Fsm.DoTransition method in it.

FsmLog.LogTransition method is included in Fsm.DoTransition method.

You can see that the load of FsmLog.LogTransition is high.
Could you tell me how to reduce the load or how not to execute the Log function?

[jeanfabre]

Hi,

 ok, thanks for clarifying

 You should be fine indeed when built, this is only for editors.

Bye,

 Jean

[yamada]

Thank you for your reply

Is there a way to make it lighter on the editor?

[jeanfabre]

Hi,

 When I want to test as close as possible to the build perfs, I have a special layout with just the gameview, nothing else, then Playmaker Editor runs less stuff.

there are also lots of preferences for you to turn off, like "Error Checking", "Debugging", that's where you can turn off logs for example.

in the "General" prefs, you can also choose which editor windows gets disabled when playing, this also helps a lot.

Bye,

 Jean