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 Wwise team, 

Proposal:
Please change the fallback transition Exit Source option for Interactive Music from “Exit Cue” to “Immediate”; or Add a setting to define the default transition behaviour (e.g., in Project Settings or via a ShareSet that can be applied at a parent level and inherited by children). 

Why this matters
I’m an interactive music designer working daily with large, layered systems—often multiple nested Music Switch Containers and numerous Switch Tracks. Because of the system’s complexity, it’s easy to miss defining a specific transition setting. When that happens, Wwise falls back to “Exit Cue.” 
In practice, this often looks like the music not switching at all during Soundcaster or runtime tests—even though the logic tree and conditions are correct. Sometimes it “magically” switches (depending on timing), but with multi-layer transitions, tracing that behaviour becomes time-consuming and frustrating. 
If the fallback were “Immediate,” the issue would be far easier to spot: the cut happens right away (too quick), making the missing transition setting obvious. That reduces debug time and avoids the false impression that something deeper is broken. 

Benefits:
Faster, clearer debugging in complex Interactive music systems 
Fewer false-positive “engine bug” moments for QA and designers 
Better iteration speed without affecting explicit, hand-authored transitions (which should continue to override any default) 

Implementation ideas 
- Project-wide default: Project Settings → Interactive Music → Default Transition (Fallback): Immediate / Exit Cue / 
- (optionally) Custom Template ShareSet-style default: A reusable Transition Default that can be assigned to a top-level object and inherited by descendants, with per-object override when needed 
- Bulk management: Tools to apply or update default transition settings across selected music objects; an inspector toggle like “Use Project Default” Safety & compatibility: Off by default or applied only to newly created objects unless explicitly enabled, preserving existing project behavior 
TL;DR 
Defaulting to Immediate (or letting us set a project/ShareSet default) makes missed transition setups obvious, dramatically reducing debug time for large interactive music systems—while keeping explicit transitions in full control. 

Thanks for considering this quality-of-life improvement!

in Feature Requests by Mingze C. (100 points)

Please sign-in or register to answer this question.

...