Audiokinetic's Community Q&A is the forum where users can ask and answer questions within the Wwise and Strata communities. If you would like to get an answer from Audiokinetic's Technical support team, make sure you use the Support Tickets page.

Unity Integration - Cannot upgrade due to namespace conflicts

+2 votes

Please use namespaces. The ErrorCode enum conflicts with the ErrorCode class from another plugin. This causes compilation errors and blocks the Wwise Launcher's upgrade process. Manually fixing the compilation errors and refreshing the launcher does not solve this issue. The launcher is stuck and will not proceed.

Installation incomplete - Code errors were found

Open your project in Unity and fix the compilation errors to allow the integration to complete. It is important that you do not modify your scenes, please only fix the code errors.

Assets/Wwise/Deployment/API/Generated/Common/ErrorCode.cs(11,13): error CS0101: The namespace `global::' already contains a definition for `ErrorCode'

 

 

We fixed this manually when we first installed Wwise but it's preventing us from upgrading now. 

asked Feb 8, 2017 in General Discussion by Justin R. (120 points)
Still need a solution for this.
Completely agree, I had to add a custom namespace to Photon's code in order to use Wwise. ErrorCode is so incredibly generic a name too. Photon shouldn't be doing this either.

1 Answer

0 votes
I completely agree. Why Wwise doesn't use a namespace is beyond me. Seems silly.

For me it was Photon that also had a global namespaced Class called "ErrorCode". So I had to make a namespace for that, and then re-integrate Wwise.

Also Wwise doesn't register that I reset my project through Unity Collaborate. I had to actually find the "InstallNotCompleted" file and delete it manually, which seems weird.
answered Feb 28, 2017 by Martin T. (140 points)
...