Version

menu_open
Wwise Unreal Integration Documentation
Known Issues

Implementation Notes and Known Issues for Wwise Unreal Integration

Cooking and Packaging

Iterative cooking is not supported in 2023.1. Unreal doesn't support our particular use case, and we are working on mitigating this issue. For now, the simplest solution is to manually delete the staged files. See https://issues.unrealengine.com/issue/UE-167603.

There is currently no automated way to separate assets by package. It is not possible to split languages into different optional packages, or make particular assets loadable independently. Although these features are planned, we need your feedback on your particular use cases so we can develop the most appropriate default feature set. Remember, it’s always possible to overwrite the different libraries in order to adapt the cooking functionality to your particular needs. You can also write specific rules directly in Unreal's Game - Asset Manager project preferences that would encompass the different Wwise assets in the Staging folder.

Multi-Process Cooking

Wwise 2023.1 does not support Multi-Process Cooking in Unreal. If the option is enabled, Wwise will not be cooked in the build. To disable the option in Unreal, set CookProcessCount to 1. For more information, see Multi-Process Cooking.

Support for Multi-Process Cooking will be added in a future version.

Partial Support for No Threading Mode

The Wwise Unreal Integration partially supports the -nothreading Unreal command-line parameter with the following limitations:

  • Partial support is only available for Unreal 5 or later.
  • The Wwise sound engine creates three additional threads even when -nothreading is set.
  • Slowdowns and sound problems will occur. Crashes and other problems might also occur.

Minimal testing has been done in No Threading mode, and it is therefore not appropriate for production environments.

In addition, we recommend that if you run -nothreading, you also run -nosound to completely disable the Wwise sound engine.

Known Issues

  • WG-44750 Physical Material Override on the Mesh cannot be used for Acoustic Texture assignment with an AkGeometryComponent.
  • WG-52497 The Unreal Editor might hang when modifying the Spatial Sound option on the current audio device. For example, this could occur when changing from Windows Sonic for Headphones to Off. Users who encounter this issue can disable UE Audio to prevent this hang. For more information about how to disable Unreal audio, see Combining Unreal 5 and Wwise Audio with AudioLink.
  • WG-69181 When applying "Fix issue" to a Wwise Niagara module, a crash might occur. A similar behavior occurs when using Unreal audio.
  • WG-69640 The Unreal Editor can crash if Niagara modules are loaded from a disabled plug-in. This also affects Wwise Niagara.
  • WG-69735 Only the top-most "Post Persistent Event" Niagara module plays audio.

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