Version
Wwise SDK 2018.1.11
|
Prior to using the development tools, you must have either Python 2 or 3 installed.
To build the property help documentation, you need to install two Python dependencies:
You also need to have the build tools required by the platforms you want to target installed and in your PATH. Refer to Platform Requirements for more information on which build tools you need to install.
Caution: Make sure to select all of the platforms you want to target when installing the Wwise SDK through the Wwise Launcher. |
For a given version of the Wwise SDK, the plug-in developments tools are located under "%WWISEROOT%/Scripts/Build/Plugins".
A quick glance at the files in this directory will give you the following list of Python scripts that you have at your disposal:
Caution: These scripts generally assume that the current working directory is the root of your plug-in, so make sure to verify that you are in the right directory before calling them. |
Note: More information about how to use these scripts is available through either the -h or –help command-line flags. |
To create a new plug-in, simply run the following in a command-line:
This will create a directory named after your plug-in in your current working directory. You can now start writing your plug-in! Refer to Audio Plug-ins for information on how to write audio plug-ins.
Note: If you find yourself often generating plug-ins using the same settings or want to automate that task, the prompts can be pre-filled by passing them as command-line arguments. |
Target platforms can be added at any point during the development of your plug-in. This is done by premaking and building that platform.
For example, run the following in a command-line to premake and build both the Windows_vc140 and Authoring platforms:
The binaries will be output directly in your Wwise installation, ready to be tested:
Once your plug-in is built for all of your target platforms and configurations, you may want to package it for installation through the Wwise Launcher. This is a two step process:
For example, run the following in a command-line to package the Common, Documentation, Windows_vc140, and Authoring platforms:
Note: You may want to edit the bundle_template.json file before proceeding with the bundle generation. Refer to Packaging Plug-ins for the Wwise Launcher for more information on the plug-in packaging format and how it relates to the Wwise Launcher. |
Note: Additional files can be packaged with any platform using the –additional-artifacts flag. |
Note: The Documentation part of the plug-in is optional. |
Questions? Problems? Need more info? Contact us, and we can help!
Visit our Support pageRegister your project and we'll help you get started with no strings attached!
Get started with Wwise