menu
Version
2016.2.6.6153
2024.1.4.8780
2023.1.12.8706
2022.1.18.8567
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
2024.1.4.8780
2023.1.12.8706
2022.1.18.8567
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
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
info | Note |
---|---|
Nested Work Units are stored on disk at the same level as their root Work Unit. |
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