I have an animation driven by an EX1 template:
<Component ID="STICKER">
<UseTemplate Name="ASOBO_IT_Simple_Interaction_Template">
<IE_NAME>STICKER</IE_NAME>
<IN_BASE_NAME>Sticker</IN_BASE_NAME>
<ON_EVENT>
(L:PietSticker) ! (>L:PietSticker)
</ON_EVENT>
</UseTemplate>
<!-- STICKER ANIMATION //////////////////// -->
<UseTemplate Name="ASOBO_GT_Anim_Template">
<ANIM_NAME>Sticker</ANIM_NAME>
<ANIM_CODE>(L:PietSticker) 27 *</ANIM_CODE>
<ANIM_LENGTH>27</ANIM_LENGTH>
<ANIM_LAG>27</ANIM_LAG>
</UseTemplate>
</Component>
I have added a sound in Wwise (2024 native project) that I know works, because I originally had it set up to play when (L:PietSticker) was equal to 1. I would like to go the AnimationSound route in hopes that the sound would play on every trigger of the animation, instead of needing to write additional update code to reset the Lvar back to 0 on every use.
Since my aircraft is a modular project, I have added a sound.xml to the model part containing this “Sticker” part and animation data. I have also tried it in the main sound.xml, even though I didn’t expect that to work - just to say I tried it.
Part Attachment sound.xml:
<AnimationSounds>
<Sound WwiseData="true" WwiseEvent="sticker" NodeName="Sticker" Animation="Sticker" Model="Interior"/>
</AnimationSounds>
(The rest of the sound.xml is set up correctly, just not pasted here.)
I figured this should work, but it doesn’t. I have also tried adding the following attributes to both the Simple Interaction template and animation template, just to cover all of the bases:
<WWISE_EVENT>sticker<WWISE_EVENT>
<WWISE_EVENT_1>sticker<WWISE_EVENT_1>
<WWISE_EVENT_2>sticker<WWISE_EVENT_2>
I already do something similar for some switch code templates, which work, but these are also the 2020 templates: ASOBO_GT_Switch_Code. The Sound string is much more stripped down though, with only the WwiseData, WwiseEvent, NodeName, and ViewPoint attributes. The switch code template itself uses <WWISE_EVENT_1> and <WWISE_EVENT_2>.
Is there something I am missing in the 2024 EX1 setup, or is this worthy of a bug report?
Cheers!