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.

+3 votes
I use unreal engine 5.1 in my project. the motion function work well until i met a issue. that is, if the gamepad did not connect to the game before i start the game.  the gamepad cann't rumble.  how can i solve this issue, If anyone can help?
in General Discussion by yanyu w. (130 points)
I've run into the same problem, did you find a solution?
Same here with wwise 2022.1.9 and UE 4.27.2

1 Answer

0 votes
Hello I come bearing answers. It's due to the GEngine not being initialized when the WWise module is loaded, you can resolve it by replacing the following in \Plugins\Wwise\Wwise.plugin:

Before:
```
"Modules": [
        {
            "Name": "Wwise",
            "Type": "Runtime",
            "LoadingPhase": "PreLoadingScreen"
        },
```
After:
```
    "Modules": [
        {
            "Name": "Wwise",
            "Type": "Runtime",
            "LoadingPhase": "PostEngineInit"
        },
```

You need to make sure that nothing in your code is trying to Get the AKAudioDevice or unwittingly causing Wwise to initialise earlier than PostEngineInit as it can cause your program to crash. I hope this helps, it was a real head scratcher
by Aishling M. (150 points)
...