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.

AKMotion on Switch

+3 votes
We're using AKMotion running on Nintendo Switch. It works fine with using the Joy-Cons externally, but can't seem to get it working in handheld mode. The documentation mention what to send into MotionEngine::AddPlayerMotionDevice on most other devices, but not the Switch and my experimentation on what to send in there has been in vain. Any ideas?
in General Discussion by Jens A. (200 points)

1 Answer

+1 vote
I wanted to bump this questions as I am running into the same issue currently. I am setting up Wwise Motion on the Switch console. The joycons will vibrate as expected when separated from the tablet but cease to work when connected to the tablet. Nothing seems to change in the profiler while connecting/disconnecting the joycons and Wwise still seems to be sending signal to the Wwise Motion bus either way. Anyone else come across a solution for this? Running Wwise 2019.2.5.
by Chris L. (160 points)
I can't remember precisely, but I think my issues was resolved after a Wwise update. But that was an older version than your 2019 one.
by Jens A. (200 points)
bumping this again - on 2022.1.9
by Rob B. (130 points)
I also see this issue - any one found a fix for this yet? wwise: 2023.1
by Simon Kærslund (100 points)
moved by Alessandro Famà
Powered by Question2Answer
...