On
this thread I started thinking about the benefits of using PlayMaker to manage and call AC's actions.
Since it wasn't the original focus of that thread, I've decided to move the discussion over here.
The following image is a repost of first design comparison I did between AC and PlayMaker. It seems to me that PlayMaker's state manager interface is really well suited to being able to visualize the branching interactions that occur between lists of actions.
This image has been resized to fit in the page. Click to enlarge.
Rather than reinventing the wheel, we could use Playmaker's state machine interface with AC's actions lists. To do this, we'd need a custom Playmaker action for each AC action:
With this approach, we'd get a high level overview of how action lists interact with conversations in a cleaner, clearer interface.
Comments
how does it feel, workflow wise? just so i understand, you add an AC action to every hotspot, interaction, cutscene, etc., which start a FSM (added to the same object?) ? Did you notice any delays or performance issues?
great work!
Will try next week.