indeed if playmaker could be be trialed, it would be great
Playmaker as a complete series of actions that allows you to easily deal with sounds: in your particular case, if you'd watch the main video cast from the site, what wou will simply add to the door fsm is this action:
https://hutonggames.fogbugz.com/default.asp?W463 ( triggers to open close doors). ON both state ( "close" and "open"), you would simply add this "play sound" action to them state and fill the details ( essentially telling which sound to play, and that's it).
And you would be done with it!
I think playmaker is the near perfect blend between visual description of a flow (or process) and scripting, because it actually relies on scripts all the way for the actions, while giving you an easy way to build the process flow. Ideal if you ask me
If you don't find the action you want, just build one, it's very easy if you have some basic knowledge of c#, else ask the community, you'll sure get help.
There is no turning back as far as I m concerned and I don't see myself starting any projects without playmaker. To be fair I am not seeing in Antares and uScript what I want: I don't want to replace scripting, I want to better describe complex flows and processes, that's the big difference. Therefore, I am not saying that playmaker is a total replacement and that everything should be done with playmaker and you'll never have to script anything again. I do an will keep script some absolute critical functionalities with normal scripts ( think Inverse Kinematics stuff, complex and performance critical operations, that last 10% of your project basically).
Bye,
Jean
