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.