fixed ME Frequently Removes Sound File from Actions Trigger Section

[GeoS72]

I updated my squadron's base capture map after the Christmas (12/24/2024) DCS update. Before I saved the mission file, I checked the sound files on specific trigger mechanisms. Everything looked great. Mission saved without issue. Uploaded the map for play. Wouldn't you know: no sound was played when that specific trigger was activated. I then went back into the ME to investigate.

Here is the problem that I've tolerated for a while: ME will frequently remove the sound file name from the Actions section of the trigger. The block that would display the file name is missing; like it never existed. When I open up the affected MIZ file using WinRAR, the sound file is not listed. If you just read the line item for the Sound to All/Group/Coalition, you wouldn't suspect there is a problem; until you click on the action to reveal the details. Here are some screenshots of the issue. As you can see, multiple triggers use one specific sound file are gone; the details for that function are missing.

Spending time in the ME trying to reconnect all the broken sound files will quickly become a full-time job! My workload just doubled because of this bug.

What causes this phenomena? More importantly, is there a fix for this?

[rob10]

Do you have any SPACES in the name of the sound files?  That can cause issues.

NVM, I see from the upper part it has the name and it doesn't.  I might try and take out the dashes too, but I don't think that matters.

Edited January 5 by rob10

[GeoS72]

@rob10,

Thanks for looking. The problem isn't just with this sound file that uses hyphens. It happens randomly to different sound files. This is just one example.

[TOViper]

This is a very old bug, it exists since years, but I think it hasn't really been reported.
I stumpled over it from time to time. It must have to do with switching between trigger action SOUND TO ALL and trigger action SOUND TO COALITION, or something similar.
IIRC the most problems I had was with the trigger action SOUND TO COALITION.

[GeoS72]

If this is an old bug then let's elevate it so it can be fixed.

I've seen this not work for Sound To Coalition and Sound to All.

[Flappie]

Issue reported.

[TOViper]

Thank you flappie!

[Flappie]

You're welcome.

All mission designers, me included, have been struggling with how the ME handles sound files. It's time for a change. I took the opportunity to ask for a combo list showing all added sounds, something like this:

[GeoS72]

@Flappie, thank you for reporting the problem. I'm curious: How would changing the field to a combo box fix the problem? Perhaps the question to ask: How does the ME handle external files, such as running a a LUA file with the "Do Script File" command? Does the Sound To... function identical to the Do Script File command?

Something causes the ME to delete that sound file from the l10n\default subfolder in the MIZ file. I suspect it happens during the save function.

[Flappie]

I think the current version of the ME works approximately like this when it comes to sound files:

1. You create a SOUND trigger and pick an audio file for it:
   • the file is put into the .miz file
   • the trigger has a relative link to the sound file (e.g.  MY_TRIGGER(./my_sound.wav, ..., ...).
2. You change your SOUND trigger to another type:
   • the sound file is still contained in the .miz
   • however there's no trigger that refers to it anymore, therefore this sound file is not referenced in the ME anymore
3. You save your .miz: since no trigger refers to this sound file anymore, the ME ignores the sound file and only saved the rest. The audio file is then lost.

We need the ME to keep an index of each sound files contained in the .miz independently of the triggers, so even when all SOUND triggers are deleted, you can still pick any sound contained in the .miz file.

And I think the ME handles Lua script files exactly the same way.

[Flappie]

A fix is coming with the next core update: whenever you will change a "SOUND TO x" action to a "SOUND to y" action, the sound file path will stay the same.

That's all I could get for now, but it's a good thing.

[GeoS72]

Thanks for the feedback, Flappie! I'll be curious to see how the next update addresses this sound problem.

[Flappie]

5 hours ago, GeoS72 said:

I'll be curious to see how the next update addresses this sound problem.

Well, I've just told you.

Example:

1. You change an action from "SOUND to COALITION" to "SOUND to ALL": the sound will be kept so you don't have to look for it. That's a very small fix but that's a good fix.

2. You change "SOUND to ALL" to "DO SCRIPT" or any other action which does not start with "SOUND to...", the sound path will be lost, and you won't find it back by re-selecting a "SOUND to" action (the file is still in the .miz file but the ME has no access to it). In this case, you don't want to save the mission otherwise you will lose the sound file for good (as usual).

 

Edited March 4 by Flappie

[Flappie]

@GeoS72 The update is live, you can now satisfy your curiosity.