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.

+6 votes

Hello,

I'm updating wwise unity integration from 2016.2.2 to 2017.1.3. After the update, I get this compile error

Assets/Wwise/Deployment/API/Handwritten/WwiseTypes.cs(6,14): error CS0101: The namespace `global::' already contains a definition for `AK'

The conflict come from Wwise_IDs.cs which has 

public class AK
{
    public class EVENTS
    {...}

}

I regenerated the header file Wwise_IDs.h with Wwise 2017.1.3, then regenerated Wwise_IDs.cs with Unity->Assets->Wwise->Convert Wwise SoundBank IDs but the conflict remains. 

What could be the problem?

Thanks

 

in General Discussion by Nam H. (380 points)
I just tested with an empty project with only wwise unity integration along with a new wwise project with a simple event. The bug is still there. The generated Wwise_IDs.cs still has a class called "AK" which is conflicting with namespace AK.Wwise in WwiseTypes.cs. This namespace was not present in the previous version we used.

3 Answers

0 votes
Is there any update on this issue? did you solve it?
by josh m. (150 points)
We ended not upgrading Wwise as it was not urgent and haven't tested newer Wwise since. We have no update on the issue. It seems like a basic issue when trying to use Wwise_IDs.cs with Unity so either we have a silly configuration problem in our project or there's an issue with Wwise Unity integration. Now that I see there's +3 votes, I know we're not the only ones with this problem.
0 votes
Same probelm here with latest wwise/unity integration
by Ruben R. (240 points)
0 votes

The workaround for this is to rename "public class AK" to "namespace AK".

It's supposedly been fixed in Wwise 2017.2.1 Unity integration but I haven't tested it myself. 

by Nam H. (380 points)
...