Audiokinetic's Community Q&A is the forum where users can ask and answer questions within the Wwise and Strata communities. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

Wwise Can't See Unity in Remote Connection on Mac with Wwise Picker Connected, SoundBanks Working

0 votes

Wwise and Unity Remote Connection Troubleshooting Checklist

Environment & Versions

  • Unity version: 6000.0.23f1

  • Wwise version: 2024.1.0.8669

  • macOS: Running locally on a single machine

  • Wwise Unity integration installed via Wwise Launcher: Yes

Wwise Launcher Setup

  • Wwise 2024.1.0.8669 installed

  • SDK (C++) installed

  • macOS deployment platform selected during install

  • Integration path matches Unity project root

  • Correct .wproj file selected during integration

  • Wwise Launcher shows green checkmark and “Operation completed successfully”

  • Mac platform added in Wwise Project > Platform Manager

  • SoundBanks generated for both Mac and Windows

  • GeneratedSoundBanks appear in Unity at /StreamingAssets/Audio/GeneratedSoundBanks

Unity Project Settings > Wwise

  • Wwise Project path: Correct

  • Wwise Application path: Correct (/Applications/Audiokinetic/Wwise2024.1.0.8669/Wwise.app)

  • SoundBanks path: Audio/GeneratedSoundBanks

  • "Connect to Wwise": Enabled

  • WAAPI port: 8080

  • WAAPI IP address: 127.0.0.1

  • WAAPI enabled

  • "Load Sound Engine in Edit Mode": Disabled (intentionally)

  • "Add Listener to Main Camera": Enabled

  • "Auto-delete WwiseObjectReferences": Enabled

  • "Show Spatial Audio Warnings": Enabled

Unity Project Settings > Wwise Initialization

  • Root Output Path points to correct GeneratedSoundBanks directory under StreamingAssets

  • SoundBank folders set for both Mac and Windows

  • “Copy Streamed Files” checked for both platforms under Post-Generation Step

  • WAAPI communication settings:

    • Pool Size: 262144

    • Discovery Broadcast Port: 24024

    • Command Port: 0

    • Initialize System Comms: Enabled

    • Comm System (Mac): Ak Comm System_Socket

Wwise Preferences (User Preferences Dialog)

  • WAAPI enabled

  • Allow connections from: 127.0.0.1

  • WAMP port: 8080

  • HTTP port: 8090

Testing and Validation

  • Unity is running in Play mode during remote connection attempts

  • Unity Console shows no major Wwise or SoundBank errors

  • Wwise Picker in Unity shows green "Connected" status

  • SoundBanks generate successfully

  • Project refreshed in Unity after SoundBank generation

  • Remote Connections window in Wwise remains empty (no Unity instance appears)

  • Console logs in Unity and Wwise include error:

    • Cannot execute call because Wwise has an exclusive lock.

    • WAMP CALL error 'ak.wwise.locked' invoking 'ak.wwise.core.object.get'

  • Process list confirms Unity is running with proper -projectpath and WAAPI arguments

Outstanding Issue

  • Despite confirmed integration, correct configuration, and functional WAAPI port, Unity does not appear in Wwise Remote Connections

  • WAAPI connection is established, but exclusive lock prevents remote interaction

  • Unity is active and in play mode, but Wwise continues to report WAAPI lock errors

  • Wwise logs confirm session attempts, followed by repeated WAAPI lock errors

in General Discussion by Forrest Hurd (140 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...