Some custom animation sounds not triggering

[MSFS 2024] Bug Reports Sound
1

Attempting to sort out why some animation sounds are not triggering, even though they are listed/programmed correctly in the behavior dialogue.

These same animation sounds work fine in MSFS 2020, but are NOT working at all (or registering a trigger in Wwise) with MSFS 2024.

We migrated to the new Wwise version, and it did not solve our issue. There seems to be a disconnect between the sim and Wwise.

This also appears to happen in a few aircraft. Boris (Boris Audio Works) has also said that he had an issue with none of his panel switches are working when attempting to port his 172 sound package from FS20 to FS24.

See photos. Thanks!

transall_issue
transall_issue2209Ɨ304 82.3 KB

2

Hey @FlyingRaccoon

Can you provide some clarity or insight into this? Iā€™ve had this happen on a few aircraft are we are stuck without a working solution at the moment.

3

Hello @Tyler

The bug report template is not here just to be an annoyance.
For us to be able to diagnose the problem, we need to know what package produces the problem, get a version of it if itā€™s not on the marketplace, and get details on the problem itself.
Are all the sound shown in your picture not playing? 100% of the time?
Is this a problem when you build your package on 2024 or also when mounting the 2020 version in 2024 as is?

Regards,
Sylvain

1 Like
4

I definitely have an issue in MSFS2024 with multiple sound.xml <SimVarSounds> entries ceasing to function during a flight, and not working again until the next load of the plane (or sim). Iā€™m currently on the SU1 beta which updated (for me) today.

An example entry is

<SimVarSounds>
...

<Sound WwiseData="false" WwiseEvent="STALL_WARNING" FileName="click" ViewPoint="Inside" NodeName="gauge_radio" LocalVar="SOUND_CLICK" Continuous="false" BreakOnStop="true"> </Sound>
...
</SimVarSounds>

The sound (click.wav) is triggered entirely in XML flipping local var ā€œL:SOUND_CLICKā€ between 0 and 1.

The sound generally plays ok, but sometimes during a flight the sound will no longer play when triggered, although I can see the ā€œL:SOUND_CLICKā€ simvar changing between 0 and 1 in the Behaviours Tool.

I first noticed this issue with another sound, configured in the same section of sound.xml, triggered by an L:var modified by a html/js gauge, but as that sound was triggered by a more complex formula it took me a while to confirm it wasnā€™t a bug in the corresponding html/js gauge.

As of today Iā€™ve discovered when that original problem occurs, then this unrelated simple SOUND_CLICK triggered WAV isnā€™t working either, so possibly none of the SimVarSounds are actually triggering.

To be clear, these sounds play ok at the start of the flight, but at some point Iā€™ve noticed these event-driven sounds arenā€™t playing when they should be later on in the flight.

The continuous sounds for the aircraft (like wind, and in my gliding case, the audio vario) seem unaffected, so itā€™s slightly tricky to detect this issue occurring. The vario sound pitch and volume vary according to L:var values which continues working ok, but theyā€™re not ā€˜triggeredā€™ to play like the SOUND_CLICK example which fails.

Now Iā€™ve got more of an idea whatā€™s happening, next time Iā€™ll try and check all my SimVarSounds local var triggered sounds.

These sounds are essentially unchanged from the same plane in MSFS2020 (the JS3 glider) and the same code is in most of the other gliders, it seems most likely itā€™s a more recent sim issue.

5

This particular issue was resolved by adding a separate Sound XML inside the ā€œinteriorā€ part container for modular builds. I donā€™t remember seeing anything in the SDK about needing this for behavior-related sounds to work. I tried searching but could not find an entry on this.

If you or someone could elaborate on this in the SDK and highlight it, Iā€™m sure someone else may find this helpful information.

6

Hello @Tyler

This is in fact the expected behavior and a constraint of the Modular SimObject design.
AnimationSounds must be declared in a sound.xml thatā€™s located in the SimAttachment theyā€™re used in.
We will review the documentation to make sure this is clearly stated.
@Nocturne FYI

@B21 Regarding SimVarSounds, this is a different issue I think.
Please replace the LocalVar attribute by a LocalVarEX1 and see if it keeps happening.

Regards,
Sylvain

7

okeydoke, will do.