hornblower793

That is because those do not need separate downloads - once you have registered the licences in the Vaicom config their functionality will become available to you Sent from my SM-T835 using Tapatalk

It sounds like Vaicom maybe looking in the wrong place for your DCS install. Please could you turn on Vaicom debug (open VoiceAttack, press Lctrl+Lalt+C, go to the Config tab, tick the first option - Run in debug mode). Then restart Voiceattack / Vaicom and stop it again. Post the Vaicom log file on here and we will take a look at it. The log file can be found in \apps\vaicompro\logs. Sent from my SM-T835 using Tapatalk

There is normally one called dcs.log - I think yours might just be dcs (the text document)

Do you have a DCS log to help track this down? Found in your Saved Games\DCS.openbeta\logs folder

Not in my version of the manual

If you look in the Vaicom install folder (for me it is E:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO) you should find a Vaicompro.exe in there. Run this and it will launch VA / Voiceattack for you and will then relaunch it automatically if it exits. If you want to close VA down you will need to close the tray app by right-clicking on it and then choosing Exit. If you just close VA it will restart

Retrain the recognition- it will be a new voice database and engine Check that it is using the correct microphone if you have more than one - I use a headset mic and Windows sometimes decides that I want to use my VR mic Check you are using the correct speech recognition engine

And a whole load of threads on this forum

Glad it is working now

Fixing the registry with the custom path does this, which is what I was trying to ask (admittedly in a very bad way :-)) Sent from my SM-T835 using Tapatalk

When you reply there should be a Drag files option under where you are typing your response (see attached - I have dark mode on)

Have you changed the OB / Stable slider in the Vaicom config to the correct value before running which ever version is not working?

I certainly haven't had this in the test flights I have done. What plane are you flying and when does the error message appear in the logs? Have you tried closing everything down and then running a DCS repair? If this doesn't work please could you turn on Vaicom debug and post either a screenshot of the log showing the error message or a copy of the log file

Wexler - what is your native language as there may already be a Vaicom translation for it? Sent from my SM-T835 using Tapatalk

Enjoy - I took the Spit for a spin last night (literally at one point) and the new prop effects were amazing. Loved the glistening as the sunlight hit the props and moved as I turned the plane. Great job ED Sent from my SM-T835 using Tapatalk

It looks very good to me in my initial flights in the Jug and Spit - using an Oculus Rift S. Great job ED

I don't think I can fix this for you - I am pretty sure it is not Vaicom (although I am only a user of it so cannot say with 100% certainty) because I don't think Vaicom generates messages like that and certainly knows nothing of other players. I think it is therefore something on the DCS or MP side with your setup that is interfering with the setup (given that the DCS log shows the messages going over TX2) and I do not run MP. It might be worth asking in the general DCS bugs section of this forum (given it affects both your aircraft) about the message to see if anyone knows what program generates it (I did an Internet search this morning but could not track it down) and this will give a clue. There are also discord servers for SRS and others which might be good places to ask to see if anyone can help you. I will keep thinking and sorry I cannot be of more help at the moment. I really hope you can get it fixed

I don't know about that message but am pretty sure that is not from Vaicom since Vaicom does not know about other players. Does Vaicom work correctly in SP (i.e. Comms on both radios)? I wonder if it is something to do with DCS voicechat - do you have that configured in DCS options? Sent from my SM-T835 using Tapatalk

Which of these is the message you are talking about? If it is the SRS message then something is not set up correctly in SRS. I know that you are not using the Vaicom SRS integration because you have not set this up in the Vaicom settings Sent from my SM-T835 using Tapatalk

You need to have EasyComms on for the warbirds at the moment to make it work. It will be fine on the ground otherwise, but not when you are in the air

Hopefully, because your screenshots showed no columns for Joystick and Throttle command mappings. It might also be worth checking the DCS SRS special settings (I cannot do this as I don't have SRS)

They all seem OK, but I don't run Voice chat or the Switch commands so do not know how they might affect behaviour Looking at your DCS settings screenshots from earlier in the thread I notice that you are running vjoy. What control devices are you using and how are they mapped into DCS? The screenshots you have shown don't seem to have separate columns for either a joystick or throttle so wondering whether it might be something in vjoy. All your logs say that Vaicom is working correctly Sent from my SM-T835 using Tapatalk

I understand what you are seeing, what I am trying to do is work out why the problem is happening. Have you tried swapping the TX1 and TX2 mappings around in Voiceattack to see whether the problem stays the same or reverses so that only Comm 2 works. If the log is showing the correct TX button being pressed and released then there is something elsewhere in the system causing issues and it is not necessarily Vaicom What settings do you have on the Preferences, MP, EX and Config pages for Vaicom? Also, have you tried using Norm instead of Multi on the PTT dial?

Glad it is sorted - we have all fallen into that trap at some point (and occassionally still do :-))

@Weegie I have just had a quick play and managed to get Batumi to pick up (once I had used Chuck's guide to remind me how to tune both the transmitter and the receiver in the Mig-15) so I think it must be something in the setup. Do you have Force ATC Names checked on the Preferences tab? I have turned on Select Tunes Radio and have confirmed it tunes both the transmitter and receiver. To get Batumi recognised reliably I do find I have to slow down and break it into clear syllables Ba-tum-i