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.

Unity no longer loads soundbanks after recent integration update [closed]

+1 vote

I'm working in Unity 2017.1.1f and just upgraded my project to the most recent Wwise-Unity integration. Without changing anything in my project, I now cannot post any events or load any soundbanks in my project for that matter. I just get tons of errors "Could not post event ID ..." and "WwiseUnity : Bank <bankname> failed to load (AK_FileNotFound)"

I've also noticed something odd which is that now in the debug logs, it seems like Unity is looking for my soundbanks in the WwiseIntegrationTemp folder, which I assume is the auto-generated copy of my project when I'm updating the integration. However, that file doesn't exist.

Here's an example of that happening as it looks for a plugin:

Wwise: Plug-in not registered: 32837795
AkCallbackManager:PostCallbacks() (at C:/Users/<path-to-project>/<project>_WwiseIntegrationTemp/Assets/Wwise/Deployment/API/Handwritten/AkCallbackManager.cs:309)
AkSoundEngineController:LateUpdate() (at C:/Users/<path-to-project>/<project>_WwiseIntegrationTemp/Assets/Wwise/Deployment/Components/AkSoundEngineController.cs:78)
AkInitializer:LateUpdate() (at C:/Users/<path-to-project>/<project>_WwiseIntegrationTemp/Assets/Wwise/Deployment/Components/AkInitializer.cs:113)

I've tried re-installing the integration, deleting the Assets/Wwise folder and installing it again, restarting, resetting...

This is a huge blocker as it means I am no longer able to work on this project, and my team is getting flooded with errors. And for some reason there's no way to revert Wwise-Unity integration...

If anyone's run into this I'd love to hear your solution.
closed with the note: After a few installs without creating a temporary copy of my project it seemed to work
asked Jan 10 in General Discussion by Blake J. (760 points)
closed Jan 11 by Blake J.

Could you go into a little bit more detail on how you fixed this?

Are you saying you just went back to BEFORE the Unity Integration upgrade and installed without copying the project? (the default recommended setting?)

Currently getting failed Unity builds as well do due the 'Could not post even ID' issue. Can't even backtrace that event, doesnt seem to be in the project OR wwise ><

Let me know! This has been crazy frustrating :(

Hi there craigz,

I'm afraid I'm not sure why it was fixed, but I can tell you that I did not revert changes to previous versions but just deleted the Assets/Wwise folder and re-integrated Wwise but did not make a copy of the project this time.

I don't know if this had anything to do with this issue, but also be sure to check if you have multiple WwiseGlobal objects in your scene, or if you're additively loading scenes in Unity make sure only one of those contains a WwiseGlobal object. That's been an issue for us lately since those (annoyingly) do not check to see if the sound engine has already initialized. Not sure if any of this helps but fingers crossed you've solved it already!