One Minute Wwise | Understanding the Scope of Game Syncs
Learn about the scope of Switches, States and Game Parameters. Learn how to apply Game Parameters to individual game objects rather than globally. No commercials, no lengthy introductions.
Let's talk about Game Syncs. As you may know, you can use Game Syncs to handle changes to your audio during gameplay. But other than structural differences (like a Switch contains Switch elements and a Game Parameter represents a value within a defined range), why is it that when setting the MovementSpeed RTPC of an Evil Head, all Evil Heads are affected despite moving at different speeds?
This is where we'll have to consider the scope of the Game Sync. You see some Game Syncs, like Switches and States, can only be set locally or globally. For example, when you alternate between placing the left foot and the right foot, you can set a Switch for each, without affecting the other. Or when setting a State, you don't need to specify a game object, since it will change globally. Then what about Game Parameters? Well, they can be set both locally and globally. Let's go back to the Evil Heads. By using the .SetValue() instead of the .SetGlobalValue(), each Evil Head will have its own RTPC value, and hereby make the Evil Heads sound slightly different, based on what the RTPC influences.
That said, if you use the same Game Parameter globally, as well as locally on individual game objects, the local value will always override the global one. That's it!
Resources:
* Understanding Global and Game Object Scope: https://hubs.ly/H0rFxL10
* More on Game Objects vs. Global Scope: https://hubs.ly/H0rFxx40
* Wwise Adventure Game: https://hubs.ly/H0rFxLd0
* More about Switches: https://hubs.ly/H0rFxym0
* More on States: https://hubs.ly/H0rFxMS0
* More on Game Parameters (RTPCs): https://hubs.ly/H0rFxyw0