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.

[Unity] How can I prevent the Wwise Application Path from being shared in version control?

0 votes
Hello everyone!

We are having an issue where two developers have different paths to their Wwise installation, causing a situation where they are having to constantly change their project settings, invalidating the path of the other developer each other. Is there a solution to this?

Thank you! :)
in General Discussion by Rafael D. (140 points)

1 Answer

+1 vote
 
Best answer
My team struggled with this a bit. Very bad design on Audiokinetic's part.

I ended up removing the WwiseSettings.xml file from the repo and adding it to the .gitignore file. I wrote a script so we have one WwiseSettings.xml in a config directory that gets copied into the project by the build machine before it builds soundbanks. All the developers just have to set up the path settings individually.

However, I do want to mention that eventually I ended up including our wwise install in the directory itself so that I could automate building soundbanks on our build machine. I didn't want to do this but Wwise is a pain to install via command line script. So if all your developers are working on windows machines it might be worth it to just have the wwise binary right in your repo.

Not a great solution but there ya go. If anyone has a more clever solution I'd love to hear it.
by Cory L. (460 points)
selected by Rafael D.
Powered by Question2Answer
...