Difference between adding behaviors to an actors
HappyKat78
Member, BASIC Posts: 173
Hi all,
I was wondering if someone could explain the difference between adding behaviors etc. to an actor by double-clicking it on the 'actor' screen vs double-clicking on the actual actor in the scene? I noticed that some commands i.e. collide only work when you set the behavior to the actor in the scene, not when you set the behavior to the actor in the section at the side (where all of the actors are listed).
I think I'm not understanding the difference. When should I set behaviors to the actor by clicking on it at the side, and when should I apply behaviors by clicking on it in the game scene?
Would love it if someone could clarify?
Many thanks!
I was wondering if someone could explain the difference between adding behaviors etc. to an actor by double-clicking it on the 'actor' screen vs double-clicking on the actual actor in the scene? I noticed that some commands i.e. collide only work when you set the behavior to the actor in the scene, not when you set the behavior to the actor in the section at the side (where all of the actors are listed).
I think I'm not understanding the difference. When should I set behaviors to the actor by clicking on it at the side, and when should I apply behaviors by clicking on it in the game scene?
Would love it if someone could clarify?
Many thanks!
Comments
First lets give some names to the faces , the "actor from the actor's list" is called prototype , and an actor that you drag to the scene is called an instance.
Now ,i made a little search for you and i think this video can explain the differences very good :
Cheers.
Roy.
Welcome to GameSalad!
all of @tatiang videos are great! … he uses them in the classes he teaches
http://www.youtube.com/user/SaintMarksTech/search?query=Gamesalad
and, of course there is the GameSalad Cookbook Channel
http://www.youtube.com/user/GameSaladCookbook#p/
and, lots more for more advanced help/how to
Enjoy yourself!
@};- MH
when/why you should/should not lock/unlock the actorInstance behaviors:
myTake:
when your game/app loads … the Prototype actors loads
when your scene loads:
-the actors load …
--if locked, the behaviors do not get reloaded … this saves on loading-time
--if unlocked, the scene will load them … virtually handling them as new
on your actorInstance … all that is on the left side of the Editor … your actor's attributes … are easily edited
ones that are greyed-out contain values passed from the prototype …
you can change them as you like … without adding significant time to scene-load time
you will eventually learn to add attributes and behaviors (that use/reference those attributes) to the Prototype …
so you do not have to unlock your instanceActors
if you are new … don't worry about this! … do things that make it easier for you to understand behaviors and get the results you want!
@};- MH