Table of Contents
If you want to simulate different sounds in game, or want to profile and troubleshoot different aspects of your game on a particular platform, you need to first connect to the machine upon which the game runs. You can connect to any Wwise sound engine that is running and available on your local area network.
When profiling, it is recommended that you connect to the Profile build configuration of the Wwise sound engine, even from the Debug build of your game, because the performance of the Debug configuration has not been optimized.
To help you find the machine you are looking for, Wwise automatically searches for all PCs and game consoles on the same subnet of the network that are currently running a version of the Wwise sound engine. You can also connect to consoles or PCs outside your subnet by manually entering the IP address of the platform.
If your game doesn't appear in the Remote Connections dialog box in Wwise, refer to Troubleshooting Remote Connection Issues to troubleshoot the problem.
To connect to a local/remote game system:
On the toolbar, click the Connect to Remote Platform button.
The Remote Connection dialog box opens with a list of game systems on the network that are currently running a version of the Wwise sound engine.
From the list, select the platform to which you want to connect.
The status of the machine must be “Ready” before you can connect to it.
If you want to start capturing information from the moment you connect, select the Start capture on connect option.
Wwise connects to the local or remote platform. The name of the machine appears in the toolbar.
You can manually connect to a platform by clicking Connect To IP and then typing the IP address of the remote machine.
To disconnect from a local/remote machine:
On the toolbar, click the Disconnect from Remote Platform button.
Wwise disconnects from the machine.