PlayMaker stats

[jeanfabre]

Hi,

 Started a small editor window to output general statistics about the fsms. Drop this file in a "Editor" folder in your project folder. Then it will be available in the menu: "PlayMaker/Editor windows/stats"

 I started this because I desperately need to have a more general overview to find potential functions duplicates and other things to improve.

  It's only started, so don't expect anything useful, but it's already fun that's why I am sharing this so soon. If you have ideas on what would like to see in this stat window, just shout oud enough

 Right now it outputs the number of fsms, the total number of variables, total number of events, and total number of states. But the plan is to mimic the fsm component "Info" section and basically extract as much as I can with the current available api. I want to check for duplicated events, duplicates variables, biggest fsm, external calls, etc etc. The global stats will also output more granular on top of the general numbers ( like numbers of fsmInt, Fsm Vector3 etc etc, global variables, global events, etc.

The biggest project I have so far has the following:

73 Fsms
678 States
202 variables
1324 events

 now, I feel better invoicing 

What are your stats? would be cool to see this kind of stats we get from the community. The winner ( no cheating please, ) ) will get..... our empathy...

 Bye,

 Jean

[qholmes]

How do i rate?

115 FSMs
546 States
313 variables
580 Events

Q

[jeanfabre]

nice

 I have to do more work on not counting unused events I think.

Bye,

 Jean

[speedything]

FSMs : 99
States: 327
Variables: 248
Events: 273

I better make my next FSM a good one (and not the boring 2-state one I had planned!) 

[brendang]

Wow...complex.  And would projects with this many FSMs run on mobile platforms like iPad?

[jeanfabre]

Hi,

The number of fsm components or indeed scripts running isn't generally the problem on mobile, it's more what you do inside it and how efficient is it, for example, don't check for a variable on each update, instead work out a solution to inform about a change of value. Don't do complex manipulation every update when you can do it once when necessary, things like that.

 and most likely you will struggle with the meshes, materials, textures and physics ( if there is). This is where the real optimization and potential show stopper are really, especially on mobile.

Bye,

 Jean

[brendang]

Great info, Jean...thanks.

I had just read somewhere in the Unity forum about some other non-visual FSM plugin that mentioned things could get heavy. Good old project optimization can absolve a myriad of sins.