Bug Reporting > PlayMaker Bug Reporting

Can't see FSMname when using Get/Set Property on an FSM Component

(1/2) > >>

Codybean1:
When you use Get/Set Property on an FSM component, it will tell you the object the FSM is a component of, but it won't give you the same of the FSM. This can make programming very confusing if an object has multiple FSM components as you can't tell the difference between them when using Get/Set Property. The ability to see the FSMname when accessing an FSM using these methods would greatly improve workflow.  :)

Fat Pug Studio:
I'm with you on this one, it could really be handy! I was having a situation with lots of gets/sets today (2-3 per state) and i was really losing what was where.

Gustav:
That's true.

For the moment I would edit the title of the action and append the name of the targeted FSM for example.

djaydino:
Hi,
Just a notice, you should always try to avoid using get/set properties actions.

You can find many custom actions on the Ecosystem

Arnoob:
Hi Djaydino!

Just for the record, why should we try to avoid them? I find this action very useful when you need to get or set a value on a particular component from an asset for example...

Navigation

[0] Message Index

[#] Next page