2024.1.4.8780
2023.1.12.8706
2022.1.18.8567
2021.1.14.8108
2019.2.15.7667
2019.1.11.7296
2018.1.11.6987
2017.2.10.6745
2017.1.9.6501
2016.2.6.6153
2015.1.9.5624
Before you upgrade to a new version of Wwise, you need to prepare your projects for the upgrade, particularly if your Wwise project has been integrated into a game. Repeat the procedures in the following sections for all projects that you want to migrate.
The migration team should carry out the following tasks to prepare projects to be migrated to the latest version.
Commit all projects:
For projects under source control, ask the other members of your team to commit all their changes.
This will avoid merge problems later.
Get the latest version of all projects to be migrated:
For projects under source control, import all the projects locally to your system.
Ensure that all project files have read and write permissions.
| info | Note |
|---|---|
For projects under source control, you may need to check out the project file (WPROJ) and all Work Unit files (WWU) from the various subfolders. |
Validate projects to be migrated:
Open each Wwise project that you plan to migrate in the current version of Wwise, and save.
If the Project Load Log dialog box displays messages and suggested fixes, accept these fixes, save the changes, and close the project. Repeat this procedure until there are no such messages. Your goal is to remove any project errors to simplify the upgrade.
Tag projects to be migrated:
For projects under source control, commit and tag or label this as the last version of the project prior to the upgrade.
Committing the project at this point will record all the changes up to the migration process. Any other changes will be directly associated with the migration in the source control history.
Des questions ? Des problèmes ? Besoin de plus d'informations ? Contactez-nous, nous pouvons vous aider !
Visitez notre page d'AideEnregistrez votre projet et nous vous aiderons à démarrer sans aucune obligation !
Partir du bon pied avec Wwise