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.

Using SetMusicState script when Player can teleport between music regions

0 votes
Hello! I have an issue using the SetMusicState script. In our game players can teleport, so when I teleport from Music Region A to Music Region B, those State changes (Exit A and Enter B) are incoming to Wwise in the EXACT same time (not even a 1/100 second difference, confirmed in Wwise Capture Log), which sometimes (randomly), puts them in the wrong order, triggering the Enter B trigger BEFORE the Exit A trigger, which puts the game in a "Nowhere" state, when it should be playing the Region Music B. Any idea how to solve this, so the EXIT trigger always get triggered first when teleporting to another region? The script works flawlessly when the player is walking/running between the regions, but this issue is when teleporting. Any suggestions would be appreciated! Thanks!
in General Discussion by Robert E. (550 points)

Please sign-in or register to answer this question.

Powered by Question2Answer
...