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.

the wrong project() is open in wwise

+1 vote
When integrating a project in Unity, everything seems fine with the initial process, but we get the message "the wrong project() is open in wwise" in the unity wwise window, next to the green "Connected".  The project in both wwise and unity is opened from the wwise launcher, so it is definitely the correct project.  What is the cause of this issue?

Using wwise 2021.1.7.7796 and unity 2020.3.26f1.

Thanks!
in General Discussion by Jean-François P. (150 points)
I'm facing the same problem
by g.O. (100 points)
moved by Samuel L. (Audiokinetic)
Hello, have you found a solution to this problem? I am having this issue rignt now and none of the answers bellow have worked. Any info on this would be helpful!
by Sandro Kurkhuli (100 points)

3 Answers

0 votes
Actually, for that error the solution was to change the access path in the wwise project settings.  However, now it cannot find the init.bnk, so still no sound.  I'm on macos 11.6.4, and I have a vague feeling it has to do with permissions... Any help is appreciated!
by Jean-François P. (150 points)
0 votes
In my case it was a wrong path configuration in Assets/WwiseSettings.xml file the at the <WwiseProjectPath> tag
by Luis Zoran R. (140 points)
0 votes
I had this bug since I forked a master branch in GitHub. The path was a reference to the ancient relative path "/.../Your Wwise project path" (Both Unity and Wwise projects were in the same drive) so I modified it to a regular path "D:/Your Wwise project path"
by Christophe M. (190 points)
Powered by Question2Answer
...