When you are ready to upgrade to a new major version of Wwise, you need to follow a coordinated protocol to ensure that your projects created in the previous version are migrated smoothly to the newer version. The goal is to avoid putting any aspect of your game at risk, so you need to examine the changes in the new version and selectively and systematically implement any modifications to your game code.

The protocol for upgrade and migration may vary depending on the number and configuration of users working with Wwise and the following conditions:

  • Projects under source control: The project will need to be checked in at key points.

  • Multiple users: The upgrade and the project migration need to be completed for the project and the SDK before multiple users can all upgrade on their workstations.

  • Integrated game project: The game code needs to be modified for the changes in the upgrade.

The migration team, composed of one or two designated individuals, should first upgrade and migrate to a local system for the authoring application, and simultaneously upgrade and migrate to a local system for the SDK and the game code as needed. After the team has carried out their respective tasks, all other users can safely upgrade their Wwise installations and access the migrated projects.

For an overview of the upgrade and migration workflow for a project under source control, consult the following chart:

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