Wwise Help

The Perforce Source Control plug-in was built using the Perforce SDK version 2018.1, but should work with most versions of the Perforce servers. If you are using a different version of Perforce that is not compatible with the Source Control plug-in, you can use the sources in the Wwise SDK to rebuild the plug-in with the version you are using. For more information about the Perforce plug-in, refer to the Wwise SDK documentation.

The Subversion Source Control plug-in was built using Subversion version 1.8.5. If you are using a different version of Subversion that is not compatible with the Source Control plug-in, you can use the sources in the Wwise SDK to rebuild the plug-in with the version you are using. For more information about rebuilding the Subversion plug-in, refer to the Wwise SDK documentation.

	Note
	Subversion's bin folder, which by default is located in C:\Program Files\Subversion\bin, must be in the system's PATH environment variable. Subversion installers normally add it to the PATH, but if Subversion is installed manually from the ZIP file mentioned above, for example, then you must add the bin folder to the PATH manually.

The following sections describe how to manage your assets using a Source Control plug-in. Although they primarily focus on the Perforce Source Control plug-in, a similar workflow exists when using Subversion.

	Tip
	Perforce, Subversion, and other Platform SDK updates are announced in our SDK Documentation's Release Notes.