Table of Contents

Troubleshooting Your Project

Wwise has two primary ways to discover problems within your project:

Using the Logs View

You can quickly see messages, warnings, and errors that appear in your project from the Wwise toolbar's logs indicator. Hover over the indicator to get more details.

To fully view the listed log entries, click the indicator to open the Logs view. Its five tabs cover all the places you could encounter an issue with your Wwise project.

Each tab with log entries will have an icon corresponding to their highest severity level. Errors must be addressed because they impact the integrity of the operation and, for fatal errors, will even impact the completion of the operation. Warnings may impact the integrity of the operation, but not necessarily, so they should be evaluated. Messages should not be problematic, but they can provide invaluable information for understanding what's going on in your Wwise project. If there are no entries in a log, then the tab will have no severity icon.


[Tip] Tip

All the Logs view tabs' column headers can be clicked to organize the entries in a logical way. The Severity column, for example, can be ordered by highest severity level (fatal error, error, warning, general message) or lowest severity level (general message, warning, error, fatal error).


Using the Integrity Report

You can check the status of your project by generating an integrity report that displays information about platform, audio file, SoundBank and plug-in issues. By examining this report, you can deal with project issues such as:

  • Missing media files

  • Missing sources, such as missing language versions

  • Plug-in problems

  • Missing objects in SoundBanks

  • Rendering and bypass effect issues for SoundBanks

  • Rendering and RTPCs for SoundBanks

In addition to displaying the project issues, the integrity report also provides information about the issue including the following:

  • Platform: The platform on which the issue occurs.

  • Type: The type of object that is affected.

  • Object name: The name of the object or element that is affected.

  • Status: The description of the issue.

  • Comments/Suggestions: Information and suggestions about how to deal with the issue.

  • Hierarchy: The location of the affected object in the hierarchy.