Version
After your project has been divided up into Work Units, you may want to unload some of these Work Units, keeping only those that you are working on. The main reason for unloading Work Units from a project is to speed up project load times, reduce memory usage, and improve overall performance. If your project is very large, you can improve performance significantly by unloading one or more Work Units.
The following types of user-created Work Units can be unloaded from a project:
Actor-Mixer Hierarchy Work Units
Interactive Music Hierarchy Work Units
Event Work Units
Note | |
---|---|
Default Work Units are critical to the project, so they can never be unloaded. |
Note | |
---|---|
Nested Work Units can't be unloaded individually, but they will be unloaded if you unload their root Work Unit. |
When Work Units are unloaded from a project, they will appear “ghosted” in the Project Explorer. You will not be able to work with them until they have been loaded back into the project.
You can continue to work with the objects and Events within the loaded Work Units. You may, however, discover that some of these objects and Events contain references to objects and/or Events that have been unloaded. For example, you may have references to unloaded objects or Events in the following project elements:
Dialogue Events
Events
Music Stingers
Music Transitions
Queries
SoundBanks
Soundcaster and Mixing Sessions
In these cases, the unloaded elements will be marked as [Unloaded]
and will be highlighted in yellow.
You can still add/remove objects, modify property values, generate SoundBanks, and so on, but you won't be able to play back these objects and Events in Wwise.
When you unload a Work Unit from a project, it doesn't get unloaded immediately. The Work Units you have selected for unloading are only unloaded from a project when the project is closed. The next time you open the project, Wwise will not load the Work Units that have been unloaded. If you need to access the contents of an unloaded Work Unit, you can easily load it back into the project at any time. If any changes are made to the project that affect the objects or Events within the unloaded Work Unit, these changes will be listed in the Project Load Log when the Work Units are loaded back into the project.
Note | |
---|---|
When Work Units are unloaded from a project, Wwise can't distinguish between source files that are not being used and those that haven't been loaded into the project. As a result, all source files that don't appear to be used by the project will be marked as “Unknown” in the Usage column of the File Manager until all Work Units are loaded back into the project and Wwise can perform a complete verification. |
To unload a Work Unit from your project:
In the Project Explorer, select the Work Units that you want to unload.
Right-click the selection and select Unload Work Unit (at next project load) from the menu.
Save your project by pressing Ctrl+S.
Re-open the project by clicking Project > Project Name.
The Work Units you previously unloaded are no longer loaded when the project opens.
To load a Work Unit back into your project:
In the Project Explorer, select the unloaded Work Units that you want to load back into the project.
Right-click the selection and select Load Work Unit from the menu.
The Work Units are loaded back into the project.
Note | |
---|---|
If any changes were made to the project that affected the objects or Events within the unloaded Work Unit, these changes will be listed in the Project Load Log when the Work Units are loaded back into the project. |
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