The audio listener is simply a component, so use the action "set property" drag the audiolistener component ( not the gameObject, really drag the audio listenre component itself), then select the "enable" property and turn that on and off.

I just tried this and, oddly, it worked in the editor but not in my compiled game. I tried both "set property" and "enable behavior" actions. Both gave the same result. In order to mute all audio, I had to attach this script to my camera with the audioListener, and then invoke one of the two methods using the "invoke method" action.

#pragma strict

function muteAudio() {
AudioListener.pause = true;
}

function unmuteAudio() {
AudioListener.pause = false;
}

Thanks for the reply, Alex. Debug flow is very cool, but it doesn't solve the problem of tracking variables that are affected by numerous actions in the same state. That's why, in debug mode, it would be handy to optionally see the variables as they were when each action completed its task.

Another way to look at it is stepping through actions, not just states.

I'm experimenting with controls similar to the game Tilt to Live, where the player tilts the device to move objects on screen. I have it working, but the device needs to be parallel to the earth. I'd like to let the user hit a "calibrate" button that resets the neutral tilt of the device.

Would it be possible to write an action that does this? I can't quite figure out the math to do it myself yet, but I did find this good article about the subject.

http://www.paradeofrain.com/2010/07/lessons-learned-in-tilt-controls/

Thanks!

For what it's worth, copying the template file directly into another project's template folder worked fine for me. Brilliant!

I just submitted a bug report about the documentation link. Also, thanks for the replacement Send Event action, which solves the original problem.

Yikes! I just encountered this today, and I'm so glad this thread existed. Has Alex been made aware of it? Certainly multiple timers running concurrently is a bad thing. I agree that if you exit the state on another event, the timer should be destroyed.

I just noticed a "Kill Delayed Events" action exists. I suppose it's meant as a workaround for this problem, though its documentation link doesn't work.

Jean, just FYI that is the only error. If you don't import "pmtCreatePrefabPool.cs," no other problems appear to arise. I don't know how to fix the action bug, but creating pools manually is pretty easy... if you recently bought Pool Manager like me, don't be afraid to dive in.

EDIT: If I may add a humble request, please add "Use Owner" as an option to the "Pmt De Spawn" action for GameObject. This would make it a drop-in replacement for "Destroy Self."