menu
版本
2024.1.4.8780
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
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
When you are ready to upgrade to a new major version of Wwise, you must follow a coordinated protocol to ensure that your projects created in an earlier version are migrated smoothly to the later version. The goal is to avoid putting any aspect of your game at risk, so you must examine the changes in the new version and selectively and systematically implement any modifications to your game code.
The protocol for upgrade and migration can vary depending on the following conditions:
Projects under source control: The project must be checked in at key points.
Multiple users: The Wwise upgrade, project migration, SDK upgrade, and game code update must be completed on a local system before multiple users can upgrade Wwise on their workstations.
Integrated game project: The game code must be modified as specified in the migration notes.
We strongly recommend that a migration team, composed of one or two designated individuals, perform the following tasks on a local system first:
After the migration team has carried out these tasks, you can proceed with:
有关处于版本控制之下的工程的升级和迁移工作流程,请参见下表:
Before you upgrade to a new version of Wwise, you must prepare your projects for the upgrade, particularly if your Wwise project has been integrated into a game. 具体来说,就是针对所要迁移的全部工程重复以下章节中所述的步骤。
The migration team must carry out the following tasks to prepare projects to be migrated to the latest version.
提交所有工程:
对于处于版本控制之下的工程,请求团队其他成员一并提交所有更改。
这样可以避免以后产生合并问题。
获取所有最新版本的待迁移工程:
对于处于版本控制之下的工程,将所有工程全部导入到本地系统。
确保所有工程文件均具备读写权限。
For projects under source control, you might need to check out the project file (WPROJ) and all Work Unit files (WWU) from the various subfolders.
验证待迁移工程:
In the current version of Wwise, open each project that you plan to migrate and save.
If the Project Load Log dialog displays messages and suggested fixes, accept these fixes, save the changes, and close the project. 重复这一操作,直到不再显示任何消息。这样做的目的是排除所有工程错误以简化升级流程。
标记待迁移工程:
对于处于版本控制之下的工程,提交并标记为升级之前最后版本的工程。
Committing the project at this point records all changes made prior to the migration process. 版本控制记录中,此后的其他更改都与迁移直接相关。
即便对功能集进行了重大更改,工程迁移流程也可确保迁移后的工程具有与之前工程基本相同的声音效果。有关这些更改的详细信息,请参阅当前 Wwise 版本的版本说明以及其中链接的对应重要迁移说明。
We recommend that the migration team migrates the Wwise project to the new Wwise version on a local system first. All other users must not modify the project until the migrated project has been tested and then committed by the migration team.
info | 备注 |
---|---|
Depending on the types of changes made to Wwise from one version to another, your projects might not need to be migrated when upgrading to a new version.
|
升级 Wwise:
Upgrade Wwise on your local system as described in Installing Wwise and Component Packages.
将工程迁移到新的版本:
确认当前 Wwise 工程中的所有文件均具备读写权限。
进行工程备份并将备份工程存储到系统或网络上的另一文件夹中。The project will be backed up automatically by Wwise, but it is good practice to create your own backup as well.
Open the new version of Wwise. In the Project Launcher dialog that opens, select the project you plan to migrate.
The Project Migration dialog opens prompting you to migrate the project to the later version of Wwise.
info | 备注 |
---|---|
The Migration dialog is only displayed when significant changes have been made to the project file between versions. 倘若工程不需要迁移,则 Wwise 会跳到迁移流程的下一步。 |
Click Migrate.
Wwise migrates the project. 在迁移工程之后,Wwise 会检查现有工程缓存文件夹是否与当前 Wwise 版本兼容。若否,则 Wwise 将删除工程缓存文件夹。When the project cache is deleted, the following message is displayed.
单击 OK(确定)。
在 Wwise 菜单栏中,依次选择 Views > Utilities > Logs(视图 >实用工具 > 日志)。此时将打开 Logs 视图。
在 Logs(日志)视图中,选中 Project Load(工程加载)选项卡。The Project Load log displays messages related to the migration and indicates if any files were created for the new version of Wwise.
info | 备注 |
---|---|
This information is stored in the file named |
若使用了版本控制系统,请将迁移过程中创建的所有新文件添加到版本控制系统。
关闭 Logs(日志)视图。
生成 SoundBank(音频包):
针对已迁移的工程生成 SoundBank 以便用来测试。
In addition to upgrading the Wwise authoring application, carry out the following tasks to upgrade the Wwise SDK and update the game code.
升级 Wwise SDK:
Confirm that your system meets the Wwise SDK Platform Requirements.
Optionally, uninstall the earlier version of the Wwise SDK.
It's good practice to also manually remove any temporary files created by the sample C++ projects.
Install the later version of the Wwise SDK. Refer to Install Wwise through the Launcher and select SDK (C++) under Packages.
Verify that the WWISESDK environment variable points to the installation folder of the later version. (有关如何设置环境变量的详细信息,请参阅选用多个 Wwise SDK 版本)。
Update the game code for the later version of the Wwise SDK:
Refer to the migration notes in the Wwise SDK documentation to familiarize yourself with the modifications you will be making.
To migrate the game code, you must port the existing functionalities of the C++ project from the earlier version of the Wwise SDK to the later version. This task might include modifying or refactoring code in different modules. Changes to the following modules might need to be addressed to update the game code:
Sound Engine(声音引擎)
Memory Manager
Stream Manager
Communications Module
info | 备注 |
---|---|
To ensure that your game is not adversely affected by some of the new features in the later version, we recommend you first upgrade the components that you need for your game. 在确保游戏比较稳定后,则可根据需要集成这些新功能。 |
根据需要修改代码。
check_circle | 技巧 |
---|---|
It's good practice to rebuild the C++ project often when you are modifying the code. |
构建游戏。
Before you can complete the upgrade and migration, you need to test the migrated game. To augment any testing protocol you might already use at your workplace, we have included a procedure. We recommend these tests are carried out by the migration team in both the Wwise authoring application and the game.
测试已迁移的游戏工程,然后提交:
在游戏中,确认声音和音频行为。确认事项可能包括:
基本的音频播放。
受代码更改影响的行为。
平台行为。
与 Wwise 设计工具的通信。
将已迁移的 Wwise 工程和代码更改提交到版本控制系统。
在完成测试后,倘若对结果满意,便可指导其他用户升级到最新 Wwise 版本。
After Wwise has been upgraded, the project has been successfully migrated, the SDK has been upgraded, game code changes have been made, and testing is completed on a local system, you are ready to advise other users to upgrade Wwise on their workstations.
此次升级必须在使用 Wwise 的所有工作站上执行,其中包括:
编译机器
声音设计师所用工作站
开发人员所用工作站
所有其他 Wwise 用户工作站
Ensure you have identified all the workstations that run Wwise so that you can upgrade them all.
在所有工作站上升级 Wwise:
可选择卸载所有 Wwise 组件。This might include:
Wwise 设计工具
Wwise SDK
For more information on uninstalling, refer to Uninstalling Wwise.
info | 备注 |
---|---|
并不一定非要卸载 Wwise。在必要时,可在同一工作站上保留多个 Wwise 版本和内部版本。 |
Install the later version of Wwise. This might include:
Wwise 设计工具
Wwise SDK
Wwise Game Simulator
For more information about installing, refer to Installing Wwise and Component Packages.
Access the migrated Wwise project on all workstations:
After you have installed the later version of Wwise, retrieve the migrated Wwise project.
打开 Wwise。
此时将显示 End-User License Agreement(最终用户授权协议)。
仔细阅读协议。若接受,请点击 Accept(接受)。
此时将打开 Project Launcher 窗口。
打开已迁移的工程。
info | 备注 |
---|---|
If some users have Work Units in the Wwise project that have been saved locally and are not under source control, a message appears prompting them to accept that these Work Units will be migrated when the project opens in the new version of Wwise. |
在加载工程之前,Wwise 会检查并确保工程缓存文件夹与当前版本兼容。若否,则 Wwise 将删除工程缓存文件夹。在删除工程缓存后,会显示以下消息框。
单击 OK(确定)。
在删除缓存后,便会将工程加载到 Wwise 中。