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.

0 votes
Hello,

For context, we've been working on a Unity that is soon to be released. However, some new console SDK forces us to switch Wwise version right now. Here's a few info:

Unity version: 2021.3.28f1
Current Wwise version: 2022.1.3
Target Wwise version: 2022.1.9
The project works and plays as expected.
The project is under version control on git.

I followed the Upgrade Wwise integration in the Audiokinetic launcher (using the recommended temp package) and the process carried through until the very end when it executes Unity to validate the integration. It ends with "Executing Unity To Complete The Installation. This May Take A Few Minutes, Please Wait...". It then crashes.

The log doesn't mention much, except:
"Got a UNKNOWN while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application."

Here's the things that I tried:
- Took the Unity project as is and tried to upgrade;
- Removed an error that was in the project by removed a package with a missing link;
- Stashed all changes under source control;
- Tried upgrading to Wwise 2023.1.also, with the same result.

Anyone have had this issue while updating the Wwise integration?

Thanks!
in General Discussion by Dave G. (100 points)

1 Answer

0 votes
Try deleting the Library folder, it helped when we upgraded to 23 as well.
by Gucci (320 points)
...