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.

0 votes
Hi, we are using Wwise with unity 2017. As Unity will always recompile all code in the main assembly, and the Wwise folder is currently NOT inside the Plugins folder, Wwise integration costs us compilation time as we code. We work around this by moving specific folders into extra Plugins folders, so that it stays in the plugins assembly. But it would be much better if Wwise could do this by default. Thanks.
in Feature Requests by Damian C. (100 points)

1 Answer

0 votes
Hi Damian

I don't have an answer for you, sorry, but just like you, we noticed slower compilation after integrating Wwise into a project in Unity 5.6.3f1. What specific folders did you move into a plugins folder to help with this?

Cheers,
Simon
by Simon S. (280 points)
Currently I am using an assembly definition file inside the Wwise folder and another one inside inside Wwise/Editor checked for editor only. This makes wwise scripts a separate assembly like Plugins. But this is only available in unity 2017.x
...