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.

Unity integration 19 (wwise 2019.2) breaks Unity Cloud Build

0 votes
I've been getting this error in my cloud builds (windows/android)

`ShaderCompiler: failed to get available platforms. Likely the shader compiler crashed at initialization time. Will retry. Error: Failed writing data to socket`

This *only* happens when I have the Wwise unity integration installed in the project.  I've tried various versions, and anything before the 2019.2.0.7216 version (Unity Integration 19) has no problems, that one and anything after make the error happen.  Very weird because wwise doesn't do anything with shaders afaik!

I think I've also narrowed it down to the code (in the API or Components folder) and not a plugin/dll.  This is even stranger, but I'm now at the limit of what I can debug from my local machine - does anyone have any idea what might be causing this and how I can solve it?

 

Thanks,
in General Discussion by Chris M. (140 points)

1 Answer

0 votes
We started seeing something recently with wwise 2019.2.2 (Unity integration 2019.2.2.1749) in Unity 2019.416.

Thankfully, we stumbled upon this initial thread:

https://forum.unity.com/threads/no-explicit-failure-code-handling-for-error-of-type-22.1080176/

 

That pointed us in the direction of this thread which, albeit with a different error (too many open files) had a solution (Best Answer reply) that solved our problem

https://www.audiokinetic.com/qa/6932/unity-mac-integration-i-o-error-too-many-open-fiies

 

TLDR: System.IO.FileSystemWatcher causes issues when built on a mac, which most if-not all UCB mobile builds are, and that caused problems stemming from the AkWwiseXmlWatcher.cs file
by Ibs R. (150 points)
Powered by Question2Answer
...