La section Questions et réponses de la communauté Audiokinetic est un forum où les utilisateurs de Wwise et de Strata peuvent poser des questions et répondre à celles des autres membres de la communauté. Si vous souhaitez obtenir une réponse de la part de l'équipe de soutien technique d'Audiokinetic, veillez à utiliser le formulaire de Tickets de Soutien.

Script compiling errors when integrating into Unity 2017

0 votes

I'm trying to integrate Wwise into a Unity 2017.1.0f1 project, but it consistantly fails and brings up the following script compiling errors:

 

  1. A script compilation error occurred during the execution in Unity. Please click Open Log to review the Unity log.

  2. Assets/Wwise/Editor/WwiseMenu/Common/AkExampleAppBuilderBase.cs(109,45): error CS0619: `UnityEditor.BuildTarget.iPhone' is obsolete: `Use iOS instead (UnityUpgradable) -> iOS'

  3. Assets/Wwise/Editor/WwiseMenu/Common/AkExampleAppBuilderBase.cs(142,45): error CS0619: `UnityEditor.BuildTarget.iPhone' is obsolete: `Use iOS instead (UnityUpgradable) -> iOS'

  4. Assets/Wwise/Editor/WwiseSetupWizard/AkWwisePostImportCallbackSetup.cs(217,57): error CS1061: Type `AkWwiseProjectData' does not contain a definition for `CurrentPluginConfig' and no extension method `CurrentPluginConfig' of type `AkWwiseProjectData' could be found. Are you missing an assembly reference?

  5. Assets/Wwise/Editor/WwiseSetupWizard/AkWwisePostImportCallbackSetup.cs(219,33): error CS1061: Type `AkWwiseProjectData' does not contain a definition for `CurrentPluginConfig' and no extension method `CurrentPluginConfig' of type `AkWwiseProjectData' could be found. Are you missing an assembly reference?

  6.  

  7. The project was not modified.

 

Integration worked fine with Unity 5, and it's necessary for the current project to use 2017 so there's no choice of going back. 

Any help to fix this issue?

demandé 3-Jul-2017 dans General Discussion par twombly (140 points)

1 Réponse

+2 votes
 
Meilleure réponse

As said here, juste update the #if UNITY_5 to #if UNITY5_3_OR_NEWER should fix the issue. But i totally agree it should be fixed in the base package as it's not the first time we get such basic issue.

répondu 13-Jul-2017 par Sébastien C. (760 points)
sélectionné 14-Jul-2017 par twombly
Whoops, never managed to find that previous thread.

Thanks for your answer though. An annoyance but at least there is an easy fix.
...