Community Q&A

Where Wwise users help each other out!

Audiokinetic's Community Q&A is the forum where Wwise users ask and answer questions within the Wwise community. Contact Sales if your project requires a support plan.

Integration failed Unity 2018.1

+1 vote

Hi,

I'm trying to integrate Wwise 2017.2.2.6553.1015 in a Unity 2018.1.0b12 project.
It fails when trying to open Unity because of the following error:

-----CompilerOutput:-stdout--exitcode: 1--compilationhadfailure: True--outfile: Temp/Assembly-CSharp-Editor.dll
Compilation failed: 2 error(s), 4 warnings
-----CompilerOutput:-stderr----------
Assets/Wwise/Editor/WwiseSetupWizard/AkBuildPreprocessor.cs(2,22): warning CS0618: `UnityEditor.Build.IPreprocessBuild' is obsolete: `Use IPreprocessBuildWithReport instead'
Assets/Wwise/Editor/WwiseSetupWizard/AkBuildPreprocessor.cs(2,22): warning CS0618: `UnityEditor.Build.IPostprocessBuild' is obsolete: `Use IPostprocessBuildWithReport instead'
Assets/Wwise/Editor/WwiseSetupWizard/AkBuildPreprocessor.cs(2,22): error CS0535: `AkBuildPreprocessor' does not implement interface member `UnityEditor.Build.IPreprocessBuild.OnPreprocessBuild(UnityEditor.BuildTarget, string)'
D:\Program Files\Unity\2018.1.0b12\Editor\Data\Managed/UnityEditor.dll (Location of the symbol related to previous error)
Assets/Wwise/Editor/WwiseSetupWizard/AkBuildPreprocessor.cs(2,22): error CS0535: `AkBuildPreprocessor' does not implement interface member `UnityEditor.Build.IPostprocessBuild.OnPostprocessBuild(UnityEditor.BuildTarget, string)'
D:\Program Files\Unity\2018.1.0b12\Editor\Data\Managed/UnityEditor.dll (Location of the symbol related to previous error)
Assets/Wwise/Editor/WwiseSetupWizard/AkWwisePostImportCallbackSetup.cs(125,33): warning CS0618: `UnityEditor.EditorApplication.hierarchyWindowChanged' is obsolete: `Use EditorApplication.hierarchyChanged'
Assets/Wwise/Editor/WwiseSetupWizard/AkWwisePostImportCallbackSetup.cs(125,33): warning CS0618: `UnityEditor.EditorApplication.hierarchyWindowChanged' is obsolete: `Use EditorApplication.hierarchyChanged'
-----EndCompilerOutput---------------

I can manually open the project and fix the scripts (as well as changing the import settings for the DLLs in Deployment) but the Wwise launcher tells me that the integration has failed and I can't figure out how to make it resume its integration.

Any idea?

asked Mar 26, 2018 in General Discussion by Clement L. (160 points)

1 Answer

+1 vote
 
Best answer
I've hit this as well and have done some debugging and wanted to share my solution. Starting from the start.

The error in the log is saying the the execution of WwiseSetupWizard.RunSetup is failing because it doesn't exist. Quickly looking at the script, it's there, so I poked further by launching Unity.

First, it seems the x86 dlls are set to load on both x86 and x86_64 which is causing conflicts.  I manually fixed those. The majority of the errors in the console went away after this.

After that, it seems that Unity deprecated the UnityEditor.Build.IPreprocessBuild and UnityEditor.Build.IPostprocessBuild interfaces for the UnityEditor.Build.IPreprocessBuildWithReport and UnityEditor.Build.IPostprocessBuildWithReport interfaces.  I manually swapped those in the AkBuilPreprocessor and restarted Unity just to be safe and it seems to launch with not errors. The methods did not need to be edited which is nice.

RunSetup still hasn't been executed though, so I quickly whipped together a script to add a menu option to manually run it. You'll know it works when Unity turns off (it's the last line of the wwise script, comment it out if you like).

After relaunching everything looks good? I will post again if something is broken but I have my fingers crossed I won't need to come back.  Hopefully this helps some people while wwise updates the integration tools.
answered May 4, 2018 by Andrew C. (460 points)
selected May 7, 2018 by Clement L.
...