Community Q&A

Welcome to Audiokinetic’s community-driven Q&A forum. This is the place where Wwise and Strata users help each other out. For direct help from our team, please use the Support Tickets page. To report a bug, use the Bug Report option in the Audiokinetic Launcher. (Note that Bug Reports submitted to the Q&A forum will be rejected. Using our dedicated Bug Report system ensures your report is seen by the right people and has the best chance of being fixed.)

To get the best answers quickly, follow these tips when posting a question:

  • Be Specific: What are you trying to achieve, or what specific issue are you running into?
  • Include Key Details: Include details like your Wwise and game engine versions, operating system, etc.
  • Explain What You've Tried: Let others know what troubleshooting steps you've already taken.
  • Focus on the Facts: Describe the technical facts of your issue. Focusing on the problem helps others find a solution quickly.

Wwise is unable to find associated Unity Project in Remote Connections on MacOS

0 votes

I am working on a game project and as of installing newer versions of Wwise, the program cannot find my Unity project when it's open on the same machine as a remote connection. I have seen several posts here that all describe similar issues to what I am having without good answers or answers that help my issue. The Unity project never appears in the connections menu, even after reinstalling, patching my version, and upgrading to 2024.1.1. You can see below the Remote Connections window is empty. On the recommendation of this thread, I used Terminal to look for connections related to Unity (`lsof -i | grep Unity` was my exact input) to get the connections seen below (and many more), and it so happens that the last "(LISTEN)" address in that set happens to work if I click "Connect to IP" and type 127.0.0.1:xxxxx and fill in whatever address comes up... Though if I am connected before hitting Play in the Unity Editor, it will become disconnected and I'll need to repeat this process. Every. Time. I. Hit. Play.

While it may be true that I have some way of profiling my game now, this process is ridiculous. I've used this software for years without issue and I don't understand how such a  standard setup like linking the profiler to a Unity project is causing such a massive headache. I'm happy to have a solution for now, but I really need the regular, intended behavior of the Remote Connections window to work.


image

Wwise Version: 2024.1.1 (same issue when using 2023, upgraded to try to solve)

Unity Version: 2022.3.9f1

in General Discussion by Sean P. (140 points)

1 Answer

0 votes

Hey! I just made a video about this issue.

You can watch it here. https://youtu.be/59Ku-N_VFsE

There's a TLDR in the comments, but basically you need to change the “Command Port” in Unity's Project Settings (wwise initialization) to something. And then the port will stay the same, so you can just connect via the history tab in the Remote Connections window.

by Julian Sarkissian (200 points)
Powered by Question2Answer
...