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.

+2 votes
Hi, We are currently using Perforce as our primary source control solution.

We have been banging our heads up against a wall on this one, it didn't happen in our previous source control system (bitbucket).

I check out the full depot / workspace and integrate wwise into unity using the launcher. All scripts, soundbanks, integration works fine, everything is ready to go.

I submit this project and all containing files (tried in unity and P4V client) and the other team members (with matching wwise versions installed) go to the launcher as a different team member (different PC) and it still wants to integrate wwise into unity.

You can go around and around with submits and it seems like EVERY user has to conduct this integration.  Any ideas on what we are doing wrong here, i am very capable using wwise but getting this integration to stick is becoming a nightmare.

Cheers!
in General Discussion by TAFENSW (270 points)

2 Answers

+1 vote
Forgot to post my answer :)

So if you are integrating wwise into unity and perforce and have an existing wwise integration:

1. check out assets\wwise folder under the unity project

2. check out the projectsettings\projectsettings.asset file (and meta)

3. When integrating choose 'integrate directly into unity project'  (for some reason perforce has issues using the temporary folder option and skips some files when creating a changelist).

Pretty much same deal for a fresh project.  Has worked each time.
by TAFENSW (270 points)
+1 vote
I had the same exact issue with Unreal, Wwise, and Perforce! I just figured it out.

Somehow the actual Wwise plugin folder wasn't pushed through perforce when I submitted everything.
In case anyone has the same issue with Unreal and Wwise integration, in Perforce:
go to (yourprojectname) -> plugins -> wwise and make sure that the whole folder is pushed through. also make sure that (yourprojectname) -> content -> WwiseAudio folder is pushed too.

cheers(:
by Meg M. (170 points)
...