tpisko

Track has been attached for a while but a fix was actually needed for Vaicom as per Discord..fixed in next release.

Ok, after uninstalling, removing Vaicom/Voice attack and restarting the Ekran sound warning is working. Would like to start using Vaicom again, so hoping it can be fixed. TRK files attached. Mig29 Sound issue-broken.trk Mig29 Sound issue-working.trk dcs.log

Yes I do. But tried to run without the plugin and it was the same. I'll try to save a track file when I get back from work.

Yes, same for me. After restart it is back to no sound.

Fantastic. Fixed. Quick repair didn't do it. Slow did fix it. thanks. I keep forgetting how good the repair can be with these "bugs".

As the title says, I have no sound from Ekran or voice warning system. Have no issues with these in other modules, including Ka50. During start-up the test button of the voice warning system produces no sound. No Ekran sounds during flight, no gear or low altitude warnings, nothing. all muted.

That was it! Thank you. Though why are these not available in historical missions? I tried years from 70s to 00s and it doesn't work in any.

Hi, no matter which map, era I cannot get these units to display on the list? Removed mods, no change. They dont appear under unarmed at all. Any ideas? EDIT: When I open MIG29 "Final approach" quick mission in ME, I can see the cars and edit them. though they still not appear on the list. When one car is selected, only that type (of the three) is visible. trying to add new one to another airfield is not possible, they don't show up in the list.

Hi, as the subject line suggests. RNW32 is not being used by AI under any circumstances - unless I am doing something wrong. All flights diverted or start from RNW30. No matter where they are parked. In addition, in IFR you get clearance to land at RNW32 (ILS) but RNW30 lights up. Is this a bug or am I doing something wrong?

FYI: The new update messed up my F14 Jester menu again. Back to exactly where it was before reinstalling. At least I know it is a module delete, reinstall. I think it it might be a good idea to a complete DCS reinstall soon. Not sure how a DCS update can mess up F14 Jester menu. Something developers might be able to answer.

After recent updates the intercom only works for me when I mute the intercom by pushing the volume knob down. Only then the crew responds. If I unmute half way through, I can hear rest of the command being spoken. Without muting it no response from crew at all. With open canopy they respond well.

Fixed! Deleting, reinstalling module did it. Should have thought of that rather than looking for a culprit in settings. @rustbelt - legend. Thank you all again.

Thank you again, that posts indicated that Vaicom might be the culprit as well. I will uninstall and test. Otherwise full reinstall it is. Major pain if you have all modules.

Hi mate, thanks for checking, legend. See attached. Menu even looks strange - it doesn't have the transparent background. Have no issue with other planes, F4 works beautifully. My PC is dedicated to DCS, no other apps, games on it. Have latest drivers, tried older ones, or studio drivers as well, no change. I use standard nVidia settings for DCS, really out of ideas. I use Open track for head tracking.

No I ran the clean, default DCS profile without Simapp, no change.