Version
menu_open
Warning: you were redirected to the latest documentation corresponding to your major release ( 2022.1.17.8543 ). Should you wish to access your specific version's documentation, please download the offline documentation from the Audiokinetic Launcher and check the Offline Documentation option in Wwise Authoring.

Nested Work Units

Work Units can be nested inside other Work Units. When this is done, the content of the Work Unit is delegated to the nested Work Unit, instead of the parent Work Unit. This allows placing several Work Units under a common Actor-Mixer object, providing common behavior and mixing properties for the nested Work Units.

The nested Work Units allows a finer granularity in the file separation, reducing potential conflicts when merging.

Nested Work Units are saved in their containing Physical Folder. For Work Units, names must be unique across a single Physical Folder.

Nested Work Units can be created under the following object types:

  • Physical folders

  • Work Units

  • Virtual folders

  • Actor-Mixers

  • Audio Busses

[Note]Note

Nested Work Units are stored on disk at the same level as their root Work Unit.

Was this page helpful?

Need Support?

Questions? Problems? Need more info? Contact us, and we can help!

Visit our Support page

Tell us about your project. We're here to help.

Register your project and we'll help you get started with no strings attached!

Get started with Wwise