mods conflict After 3/12 update no entity sounds when using COMMS Menu on user missions made prior to update

[RickJamesBish]

I cannot say this happens on every user mission. 3 systems and after update, entities such as awacs and tower are not audible in any of our user made missions. Pressing the appropriate F key, for example request taxi progresses to the next option, request takeoff but you never hear them. Awacs also is not audible. Created a new mission and it works. Tutorial missions it works.

Edited April 13, 2024 by RickJamesBish

[Flappie]

Please attach your dcs.log (from Saved Games/DCS.../Logs). Most often, missing sounds are caused by mods.

[RickJamesBish]

I do have vaicom / voice attack, but it happens without these running. It also worked yesterday and we played into the morning hours. It stopped when we all updated.  Log is attached.

It may not be the update but its the only common factor we know of that changed. Also missions created after the update do not have the issue.

dcs.log

Edited April 12, 2024 by RickJamesBish

[Flappie]

Thank you. I don't know what these are:

2024-04-12 17:28:24.215 ERROR   ED_SOUND (Main): source_add(host:MAIN_16787713/main, proto:empty, alt_proto:): can't find proto
2024-04-12 17:28:24.215 WARNING LOG (17220): 2 duplicate message(s) skipped.
2024-04-12 17:28:24.215 ERROR   ED_SOUND (Main): source_add(host:MAIN_16787969/main, proto:empty, alt_proto:): can't find proto
2024-04-12 17:28:24.475 WARNING LOG (17220): 2 duplicate message(s) skipped.

but I don't see any mod in your log.

[RickJamesBish]

13 hours ago, Flappie said:

Thank you. I don't know what these are:

2024-04-12 17:28:24.215 ERROR   ED_SOUND (Main): source_add(host:MAIN_16787713/main, proto:empty, alt_proto:): can't find proto
2024-04-12 17:28:24.215 WARNING LOG (17220): 2 duplicate message(s) skipped.
2024-04-12 17:28:24.215 ERROR   ED_SOUND (Main): source_add(host:MAIN_16787969/main, proto:empty, alt_proto:): can't find proto
2024-04-12 17:28:24.475 WARNING LOG (17220): 2 duplicate message(s) skipped.

but I don't see any mod in your log.

Not sure what that is. The entity sounds work in all the training missions and all missions created after the update, so somehow all user missions created before the update got broken. 

I have a friend who has not updated yet. He is trying a mission he created, and one we played the night before the update, to confirm sound still works. Then he is going to update and see if it breaks. That will tell us something. Will update post after he is done.

Edited April 13, 2024 by RickJamesBish

[RickJamesBish]

So this appears to be associated with Vaicom and / or Voiceattack in some manner. This is what we know to be a constant between the 3 systems we experience this on. The same user mission is being used between all the computers to test.

1. Prior to update entity voices such as AWACS could be heard when they responded to your voice command or F menu keys.

2. After update starting DCS only (VA/VC not run at all after update), entities can be heard responding.

3. After update starting DCS again but this time with VA / VC, Entity cannot be heard responding to your command by voice or F keys. Only hiss at start of what would be their response and another hiss at what would be the end of their response.

4. After trying 2 and 3 in order, then starting DCS again without VC / VA, issuing command with F key, same results as #3.. hiss.. nothing... hiss.

5. In DCS Scripts/Speech, two files are being altered by VA/VC... speech.lua and common.lua.

6. Running DCS Repair fixes these two files.

7. Running DCS after repair without VA/VC entity voices are heard.

8. Launching VA / VC results in the aforementioned two files being altered immediately.

9. Run DCS with VA/VC or without it, and entity is not heard.

Conclusion is that once VA/VC is run after the DCS update, something in the changes to the common. lua and speech.lua made by VA/VC is not compatible with the user made missions that were created prior to the DCS update. 

Edited April 13, 2024 by RickJamesBish

[RickJamesBish]

Last update.. Promise. We spent hours on this and narrowed down to a definite fix. It is unlikely the above fixed the issue, and more likely we made a change we were not aware of.

This issue IS, without doubt, related to the callsigns and VA/VC. If you have user mission and use any of these callsigns for a flight, you cannot hear the Entity response to your radio command/request. All of these result in hearing static at start of entity transmission then again at the end, but nothing in between. We edited all of our missions made prior to the last DCS update and changed them ones not in the list. 

If you use VA/VC, run DCS repair and do not start VC / VA AT ALL because it immediately modifies files. However if you wish to use VA/VC, modify your mission  to not use any of these callsigns.

viper 
jedi 
ninja 
wild
weasel
wolf
panther
venom
lobo
rattler
cowboy
python

Edited April 14, 2024 by RickJamesBish

[hornblower793]

This happened a few years ago to some of the A-10 callsigns and Hollywood had to make a change in Vaicom. Probably worth checking the Vaicom discord to see if this is already a known issue and if not log it

[RickJamesBish]

20 hours ago, hornblower793 said:

This happened a few years ago to some of the A-10 callsigns and Hollywood had to make a change in Vaicom. Probably worth checking the Vaicom discord to see if this is already a known issue and if not log it

Yes I went to dicord first actually and made them aware of what we found.