Upgrading Wwise

The project migration process has been designed to ensure that your migrated project very closely approximates the sound of your previous project despite the significant changes made to the feature set. For more information about these changes, refer to the current version of the Wwise release notes, as well as the corresponding Important Migration Notes linked within.

The migration team should migrate the Wwise project to the new Wwise version on a local system first. All other users should not alter the project until the migrated project has been tested and then committed by the migration team.

[Note] Wwise Versioning

Depending on the types of changes made to Wwise from one version to another, your projects may not need to be migrated when upgrading to a new version.

  • Major Release: If the year number of the version or the first decimal point after the year changes, this is a major release likely involving several major changes. For example, 2016.1 and 2016.2 were both major releases. When opening a project saved in the former version with the latter version of Wwise, Wwise will automatically update it. After that, it will no longer be possible to open that project with the 2016.1 version.

  • Minor Release: If the year number of the version or the first decimal point after the year remain the same, but there is iteration of an additional decimal point, then this is a minor release. For example, 2016.1.3 and 2016.1.4 were both minor releases with only a few changes. When opening a project saved in the former version with the latter version of Wwise, no migration is necessary.

  1. Upgrade Wwise:

    1. Upgrade Wwise on your local system, as described in Installing or Upgrading Wwise and its Packages.

  2. Migrate a project to the new version:

    1. Verify that all files in the current Wwise project have read and write status.

    2. Perform a backup of the project and store the backed up project in another folder on your system or network. The project will be backed up automatically by Wwise, but it is a good practice to do your own backup as well.

    3. Open the Wwise project that you plan to migrate to the new version.

      A message is displayed prompting you to migrate this project to the latest version installed on your system.

      [Note] Note

      The Migration dialog box is only displayed when significant changes have been made to the project file between versions. If your project does not require migrating, Wwise will skip to the next step in the migration process.

    4. Click Yes.

      Wwise begins to migrate the project. After the project is migrated, Wwise checks to see if the existing project cache folder is compatible with the current version of Wwise. If not, Wwise deletes the project cache folder. When the project cache is deleted, the following message box is displayed.

    5. Click OK.

    6. From the Wwise menu bar, click Views > Utilities > Logs. The Logs view opens.

    7. In the Logs view, select the Project Load tab. The Project Load Log displays messages related to the migration and indicates if any files were created for the new version of Wwise.

      [Note] Note

      This information is stored in the file named projectname.wproj_migration.log in the project folder. If needed, you can also click Copy to clipboard to save this information for reference.

    8. If you are using source control, add any new files that were created during the migration process to your source control system.

    9. Close the Logs view.

  3. Generate SoundBanks:

    1. Generate SoundBanks for migrated projects that will be used for testing.

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