This method will apply if:
-
The game has a large number of in-memory media assets.
-
The media requirements are difficult to predict in advance by the sound designer.
-
The project uses switches and states to determine which sound or motion FX will play for a specific event.
-
Sounds and motion FX can't easily be split into defined sections.
Games can be very complex and the triggering of sounds and motion can be based on a variety of different factors, including game textures, the time of day, the movement of game objects, and in some cases the actions of other players for online multiplayer games. In an event-based or object-based environment, sounds and motion FX could, for example, be loaded into memory based on the proximity of some other game objects. Every game object could have a list of banks that must be loaded when they are within a given range or simply because they exist.
Also, switches and states can determine which objects are played. When an event playing such objects is added to a bank, all possible media is automatically added to the bank as well. For example, you may have a single event called “Play_Footstep”. This event will play the appropriate sound based on the current texture of the ground, which is specified by changing the switch. Although this works well, it can be a waste of memory keeping the sounds “footstep_sand.wav” or “footstep_winter.wav” ready in memory when the gameplay is happening inside a building in London.
To avoid wasting memory in this case, you can add events and/or object structures to a bank and then specify which corresponding objects will be included in the bank. For example, let's take footstep sounds on different textures. In this case, we could create the following banks:
-
The “EventBank”, which would contain the “Play_Footstep” event and structure.
-
The “Winter_Footstep_bank”, which wound contain the media for the footsteps that only occur in some part of the game (winter).
-
The “Desert_Footstep_bank”, which wound contain the media for the footsteps that only occur in some part of the game (desert).
-
The “Common_Footstep_bank”, which would contain the media for the footsteps that can occur anywhere (wood, concrete, and so on).
Let's say you have three different textures in your game (snow, sand, and concrete). In Wwise, you have a switch container, that plays one of three random containers, based on the switch “ground_texture”. Each of the three random containers has four variations of the footstep sound on a given texture.
To create banks in Wwise that micromanages your media:
-
Create a bank called “EventBank” and load it into the SoundBank Editor.
-
Drag the “Play_Footstep” event to the Add tab of the SoundBank Editor.
-
Deselect the “Media” check box for this event, but leave the Events and Structures check boxes selected.
-
Create the three other banks, one for each texture.
-
In each bank, drag the random container associated with this texture.
![[Note]](/images/2015.1.9_5624/?source=Help&id=note.png)
Note It would work as well if instead of drag and dropping the random containers we would drag and drop each of the sounds individually. But the advantage of using the containers is that all the sounds in the container will automatically be added in the bank instead of having to make all the changes manually if the container's content changes.
-
Deselect the “Events” and “Structures” check boxes for each of the three texture banks, leaving only the Media type checked.
-
Generate the banks and copy the generated bank folder to the game application.
At this point, we have four banks, one that contains the event and the structure data related to the audio that is to be played, and three others that contain only media associated with a particular ground texture.
To integrate banks in game using the micromanaging strategy:
-
In the game, load the common banks at the beginning of your game and then simply load the other banks when they are required. For example, the game could load the event bank and the common footsteps bank at the beginning and then load the other banks based on the player's actual location in the game.
The following sample of code gives you an idea how these banks can be loaded in game.
This was only a very specific example of one of many possible things that can be done using this technique. Since it is possible to decide object by object and event by event what will be included in every bank, you have complete control over the contents of each bank. Although you could create a separate bank for each object in your game, this would be very difficult to maintain as every new sound or motion FX would require new code to load the bank at the right place in the game. The goal for each game is to try and find a good balance between granularity and ease of integration in the game.
|
Note |
|---|---|
|
If you are interested in a sound by sound loading scheme, you may want to prepare events instead of loading entire banks. For more information on preparing events, refer to Method 4: Preparing Action Events. |
The following table lists the pros and cons of the “All-in-one” bank method.
|
Pros |
Cons |
|---|---|
|
The best option to optimize memory usage. Gives you full control over what media is loaded at any point in the game. |
Requires a lot of communication between the sound designer and the game developers to determine which bank must be loaded, and when. |
이 페이지가 도움이 되었나요?
작업하는 프로젝트에 대해 알려주세요. 언제든지 도와드릴 준비가 되어 있습니다.
프로젝트를 등록하세요. 아무런 조건이나 의무 사항 없이 빠른 시작을 도와드리겠습니다.
Wwise를 시작해 보세요