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.

Capture Log filled with: Unknown game object ID

+3 votes
After recent update of my Unity integration I noticed several problems with audio - all environmental sounds collapsed to 0,0 and other problems. In order to figure out what's wrong I started profiling session. And my Capture Log started filling with Unknown game object ID. Make sure the game is registered...

I've commented out all AkSoundEngine calls and removed all objects with AK components in the scenes but still get those errors. This is pretty complex game and it's possible that I missed something but I have no way to figure out what's wrong. There's no information about the function called or anything.

Previous (i.e. 2016.2.0) integration worked fine, at least considering the audible part because I didn't used the profiler with it. The new one is sounding differently and the profiler is almost useless.
in General Discussion by Maciej M. (510 points)
I'm seeing the same problem, so I created a fresh Unity project, integrated it with Wwise, and I'm getting the same error messages and loss of 3D sound localisation.
by ciaran r. (110 points)
I'm having the same issue!!
by Jiyoung P. (120 points)

3 Answers

0 votes
I'm having the same issue. Worked fine with the previous integration, updated it and I'm getting my capture log filled with this error.
by Jason F. (140 points)
+1 vote
Sorry about that, a bug was introduced in the latest 2016.2.1 build. A fix will be available very soon. Stay tuned.
by Benoit S. (Audiokinetic) (16.0k points)
0 votes
 
Best answer

Today's integration update seems to solve the problems: positional localization is correct and the capture log is not filled with Unknown game object ID error messages anymore.

by Maciej M. (510 points)
selected by Noemie P. (Audiokinetic)
Powered by Question2Answer
...