VAM triggers:
Triggers are commands that perform an action on an atom's property.
that translates into:
something that does something on something
Triggers in VAM follow this basic structure:
this atom > this thing in the atom > to do this
Examples of triggers
example shown in MacGruber's guide to triggers linked below
Some examples people ask about a lot
Play music in a scene:
Audio can also come from assetbundles (audiobundles), not just from Scene Audio, but you'll need a plugin to play them (see guide below).
Some guides showing trigger uses
hub.virtamate.com
hub.virtamate.com
hub.virtamate.com
Using triggers in a scene
Please first check the above guides on how to make a trigger if you haven't yet.
Triggers allow you to execute actions on a scene when you use buttons, have animations that trigger the triggers (yes, get used to the verb+noun mix), plugins, etc.
An UIButton atom is probably the first atom you'll use when starting to peruse the world of triggers, just because it's so simple to add, put in a trigger in the button trigger tab, and click to see it working (hopefully).
If you never set a trigger in VAM, here's your first trigger exercise:
If you want to have the button turn the person On and Off, adapt your trigger to use the toggle option shown on "Examples of triggers".
Congratulations, you now know how to make triggers and deserve a biscuit. Treat yourself!
Triggers, triggers, triggers...
What's the difference between a trigger in a UIButton and a trigger in the Triggers track of Timeline?
Only their location, because the trigger system is a core VAM feature, not a property of an atom or plugin.*
*well... kind of
What's with some atoms/plugins having "start actions", "transition actions", "end actions" tabs for triggers?
Triggers in these actions act upon their moment. For example, in a collision trigger like shown in the image above:
The trigger system and atom properties
As you probably suspect already, each atom type will have properties that are different from other atoms. A person atom will have receiver targets for the head for example, but a UIButton won't because it has no head. Makes sense, right? Even with all their differences, they will still share many receiver targets between them, like the AtomControl that can turn the atom on or off.
There is no list of all the receivers and receiver targets for each atom type. Such a list would be really big for some, especially the person atom, and no one made one. Also, objects in an atom can expand that list. Clothing, hair, plugins, they will often include new trigger options that the base atom did not include earlier. A full list of triggers is in a way infinite because it depends on what's in the scene, where, and what else you have beyond the scene.
But fear not, there's method to the madness here. As you start exploring people's scenes, and you should because that's how you best learn about triggers and implementations, you'll notice patterns for the base and dynamic targets. Those patterns are the key to make your scene triggers and understanding how to find them.
How to learn about what triggers exist and how to use them
Open and explore scenes, break them down, see how things work. This is by far the best way to get acquainted to triggers and how to implement them to make your scene.
There are also plugins that expand the range of VAM's built-in trigger system, like MacGruber's LogicBricks, hazmhox's VAMStory, and many more. Start small, make simple triggers that perform some actions, learn and expand on that.
And the last advice about triggers:
K.I.S.S.!
Keep It Simple, Stupid!
Triggers are commands that perform an action on an atom's property.
that translates into:
something that does something on something
Triggers in VAM follow this basic structure:
a.k.a.
this atom > this thing in the atom > to do this
Examples of triggers
This trigger will turn OFF a person atom named "Person"
This trigger will turn ON a person atom named "Person"
This trigger will switch to ON or OFF the light in a light atom by switching to the opposite state of the current state.
example shown in MacGruber's guide to triggers linked below
Some examples people ask about a lot
Play music in a scene:
- add a music file to Scene Audio
- add an audiosource atom to the scene
- use an UIButton or other means to trigger:
AudioSource > AudioSource > Play(youroption) > URL > web > your music
- add your speech audio file to Scene Audio
- add a person atom to the scene if not present yet
- use an UIButton or other means to trigger:
Person > HeadAudioSource > Play(youroption) > URL > web > your speech audio
Audio can also come from assetbundles (audiobundles), not just from Scene Audio, but you'll need a plugin to play them (see guide below).
Some guides showing trigger uses
MacGruber's Video Tutorials - Guides -
This page will gather my hopefully growing collection of video tutorials about various VaM topics. "Pay after watching, IF you liked it!" Producing quality video tutorials consumes a LOT of time. Just producing 10min of video takes about 6-8...
hub.virtamate.com
Basics - Collision Trigger - Guides -
This is a basic "how do triggers work, in VaM, today" guide. I *was* going to put these steps in a larger gude of mine which is about creating a plugin that will enable you to trigger an action by moving to a predetermined are within your scene...
hub.virtamate.com
Audiobundles: assetbundles for sounds - Guides -
Audio assetbundle => Audiobundle But why put audio files into assetbundles??? Lightning fast loading Easy to reuse Tons of audio files can be loaded in a single assetbundle almost instantly; don't waste time waiting for the sounds in Scene...
hub.virtamate.com
Using triggers in a scene
Please first check the above guides on how to make a trigger if you haven't yet.
Triggers allow you to execute actions on a scene when you use buttons, have animations that trigger the triggers (yes, get used to the verb+noun mix), plugins, etc.
An UIButton atom is probably the first atom you'll use when starting to peruse the world of triggers, just because it's so simple to add, put in a trigger in the button trigger tab, and click to see it working (hopefully).
If you never set a trigger in VAM, here's your first trigger exercise:
- In a new scene, add a person atom and an UIbutton atom
- maybe some lights too to see anything
- Go to the UIButton options and select the "Button trigger" tab to add a new trigger
- Create a trigger with this format:
- Person (default name of the person atom) > AtomControl > On (change the checkbox to be unchecked)
- Click the button to trigger your new trigger
If you want to have the button turn the person On and Off, adapt your trigger to use the toggle option shown on "Examples of triggers".
Congratulations, you now know how to make triggers and deserve a biscuit. Treat yourself!
Triggers, triggers, triggers...
What's the difference between a trigger in a UIButton and a trigger in the Triggers track of Timeline?
Only their location, because the trigger system is a core VAM feature, not a property of an atom or plugin.*
*well... kind of
What's with some atoms/plugins having "start actions", "transition actions", "end actions" tabs for triggers?
Triggers in these actions act upon their moment. For example, in a collision trigger like shown in the image above:
Quote from MacGruber
The trigger system and atom properties
As you probably suspect already, each atom type will have properties that are different from other atoms. A person atom will have receiver targets for the head for example, but a UIButton won't because it has no head. Makes sense, right? Even with all their differences, they will still share many receiver targets between them, like the AtomControl that can turn the atom on or off.
There is no list of all the receivers and receiver targets for each atom type. Such a list would be really big for some, especially the person atom, and no one made one. Also, objects in an atom can expand that list. Clothing, hair, plugins, they will often include new trigger options that the base atom did not include earlier. A full list of triggers is in a way infinite because it depends on what's in the scene, where, and what else you have beyond the scene.
But fear not, there's method to the madness here. As you start exploring people's scenes, and you should because that's how you best learn about triggers and implementations, you'll notice patterns for the base and dynamic targets. Those patterns are the key to make your scene triggers and understanding how to find them.
How to learn about what triggers exist and how to use them
Open and explore scenes, break them down, see how things work. This is by far the best way to get acquainted to triggers and how to implement them to make your scene.
There are also plugins that expand the range of VAM's built-in trigger system, like MacGruber's LogicBricks, hazmhox's VAMStory, and many more. Start small, make simple triggers that perform some actions, learn and expand on that.
And the last advice about triggers:
K.I.S.S.!
Keep It Simple, Stupid!
Last edited by a moderator:
