2024.1.6.8842
2023.1.14.8770
2025.1.0.8897
2022.1.19.8584
2021.1.14.8108
2019.2.15.7667
2019.1.11.7296
2018.1.11.6987
2017.2.10.6745
2017.1.9.6501
2016.2.6.6153
2015.1.9.5624
In Wwise, you can create and edit Auxiliary Busses with Effects and define which object is sending to them. Auxiliary sends can be defined programmatically to sounds based on game object positioning. The following steps describe how a development team can implement game-define auxiliary sends:
The sound designer defines Auxiliary Bus objects corresponding to environments in the game, such as small room, church, and cave.
The sound designer makes sure all sounds that are to be affected by the environment acoustics have the option Use game-defined auxiliary sends enabled.
The game developer maps the Auxiliary Busses to the environments as they appear in the game geometry.
The game developer creates a mechanism for reporting the real-time calculation of percentages of environments to the sound engine.
The sound engine calculates which Auxiliary Bus applies to the sounds triggered by each game object.
| info | Note |
|---|---|
|
To audition and tweak game-defined auxiliary sends, you must either connect to the game and tweak your Effect in real time, or apply the auxiliary send as a user-defined send temporarily. You may also want to try the SoundFrame Test tool (SFTest.exe), which is installed as part of the Wwise SDK. This tool allows you to remote-control Wwise and retrieve data from the project. You must attach an Event to a game object, play it, and then edit the game-defined auxiliary sends by pressing the Edit Sends button. This will allow you to control the various levels of your game-defined sends. |
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageRegister your project and we'll help you get started with no strings attached!
Get started with Wwise