社区问答

欢迎来到 Audiokinetic 社区问答论坛。在此,Wwise 和 Strata 用户可互帮互助。如需我们团队直接提供协助,请前往技术支持申请单页面。若要报告问题,请在 Audiokinetic Launcher 中选择“报告错误”选项(注意,问答论坛并不会接收错误报告)。我们内部设有专门的错误报告系统,会有专人查看报告并设法解决问题。

要想尽快得到满意的解答,请在提问时注意以下几点:

  • 描述尽量具体:比如,想达到什么样的目的,或者具体哪里有问题。
  • 包含关键细节:比如,Wwise 和游戏引擎版本以及所用操作系统等等。
  • 阐明所做努力:阐明自己为了排除故障都采取了哪些措施。
  • 聚焦问题本身:聚焦于问题本身的相关技术细节,以便别人可以快速找到解决方案。

0 投票

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!

分类:Feature Requests | 用户: Mingze C. (100 分)

Please sign-in or register to answer this question.

...