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.

Problems with Unity integration using version control (SVN)

0 votes
Hello. My team wants to include Wwise into our current Unity project and we are having some problems. The first being that if one of the computers adds the Wwise-Unity integration and commits the changes to our repository, random things happens in our project; for example: game objects are missing some built-in scripts like Slider, networking components, etcetera. How should we integrate Wwise to Unity in a way that works for any other computer using the Unity3D editor?  Are there specific considerations to be taken for each operative system? We are using Windows, Mac and Linux computers and they need a fully functional version of the Unity project.

Thanks in advance,

Mauro.
in General Discussion by Mauro A. (160 points)
We solved the "random missing things" problem. Our Windows PCs are using TortoiseSVN, which is, by default, set to exclude important files by extension, such as *.so, *.libs... It seemed that when applying the integration package some of the modified files got left out unversioned because of this filter.

Apologies for thinking it was a Wwise Integration issue.

Now we have our Windows and Mac machines running Unity with Wwise without any issue. Awesome.

Nevertheless, we couldn't get our linux machine working. This is what we get on the console after opening the project:

Assets/Wwise/Deployment/API/Generated/Common/AkDeviceSettings.cs(102,10): error CS0246: The type or namespace name `AkThreadProperties' could not be found. Are you missing a using directive or an assembly reference?

And

Assets/Wwise/Deployment/API/Generated/Common/AkInitSettings.cs(179,10): error CS0246: The type or namespace name `AkAudioAPI' could not be found. Are you missing a using directive or an assembly reference?


Any clues?


I forgot to add that we are using the latest available Unity3D (5.1.0f3) and the latest Wwise and Wwise integration (2015.1.2).

Thanks for your support,

Mauro.
by Mauro A. (160 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...