hornblower793

Sorry - I goofed (comes of trying to answer too many things at once and not paying attention). It is definitely something specific to your setup since I have not seen this before on these forums, and I fly both the F-18 and the F-16 and have TX1 and TX2 working. If you swap the TX mappings over so TX1 is button 5 and TX2 is button 6 does the issue stay the same, or does it change round so that Comm 2 works and Comm 1 doesn't?

Looking at the log file it says that AWACS responded to your transmissions on TX2 TX2 | COMM2: ARC-210: [ AWACS ] , [ Request Picture ] Constructing message... Done. AWACS (Overlord1-1): 112, Overlord1-1, BRA, 073 for 150, at 25000, cold - this is the response message from DCS so you should hear this (and see the text at the top left hand of the screen if you have not turned this option off) and ATC on TX1 TX1 | COMM1: ARC-210: [ Air Traffic Controller ] , [ Inbound ] Constructing message... Done. ATC (Kutaisi): 111, Kutaisi, fly heading 192 for 70, QFE 29.77, runway 07, to pattern altitude According to the log, AWACS responded both times you called it on TX2. There is also a response from AWACS after you called inbound on TX1. Please could you turn on the debug option in Vaicom (top option on the Config tab) and then post another logfile - this will give additional diagnostic information that may help. I don't fly Multiplayer at the moment so don't use the VOIP Switch commands - does Vaicom work correctly in a single player mission? I am wondering whether it is something to do with how long you are holding the PTT down to talk to other players as you have turned on the option to queue the AI transmission so it will only send once you have released the PTT

Has this fixed the issue?

I think you are releasing TX1 too early after saying go to tanker so it is processing go to tanker as a standalone command which defaults to the whole flight

That is a Voiceattack question - might be better to ask on the voiceattack support forums or their Discord Sent from my SM-T835 using Tapatalk

Looking at the logs, it looks like you have a Steam install of stable (the custom path you have set), but the log also says it cannot find a steam version. On the config page where you set the custom path there are also some sliders to say whether you are running standalone or steam, and whether it is the stable or openbeta version. Do you have these set the right way? Sent from my SM-T835 using Tapatalk

We could do with a lot more information to help you - best thing to do is open this as a new thread in the Vaicom section of the forum. In the post please could you post screenshots of your Vaicom config PTT and Preferences tabs. It would also be useful if you could turn on Vaicom debug (first option on the Config tab), restart VA and then post the Vaicom log to the thread (the log can be found in <your Voiceattack install directory>\apps\vaicompro\logs) Do you have any daisy-chained profiles (e.g. Bailey's) and do you run with other DCS add-ons such as Tacview or SRS? Do you use external programming software for your HOTAS - what set-up are you running,

Do you have the licence for the kneeboard extension and have you registered it in Vaicom? Are you running any daisy-chained profiles (e.g. Bailey's)? Sent from my SM-T835 using Tapatalk

I don't think you need to do that - what frequency is the CV tuned to? The log file shows no tuned units on the frequency you are using. I am rusty in the F-18 but will hop into mine tomorrow for a launch and see what happens. Try using TX1 rather than TX5 Sent from my SM-T835 using Tapatalk

Which plane are you in, and are you hooked up on the bar with afterburners fired up? Sent from my SM-T835 using Tapatalk

Lucky you - good luck with the flying

Looking at the log file I think there is an issue with the path you have set for your OB install (I am guessing this is therefore the one you are running). You have set the path to point to F:\DCS World OpenBeta\bin - it should actually be pointing to the root folder for the install (F:\DCS World OpenBeta). Without DCS running, change this path in the Vaicom config (including fixing the registry) and then close down VA. Run a quick repair on your DCS OB installation (checking changed files only), rename the Export.lua in Z:\\DCS.openbeta\Scripts and then restart VA / Vaicom once the repair has completed. You should have a new Export.lua in the folder. Before running DCS, try pushing / holding your PTT button and saying Inbound to check that it comes up as recognised in the log (see the attached for my log) - As @Monkwolfhas said, check that the correct microphone is being used as windows or software updates can sometimes change it around - every now and then mine changes from my headset mic to my VR headset mic.... If Inbound is recognised then start up DCS and load one of the instant action free flight missions for your plane (if not, then there are VA / Vaicom set-up issues we need to troubleshoot). As soon as you are in the cockpit open the Vaicom config screen and see if the airframe is now showing. SRS and Tacview also place lines in the shared Export.lua and can be a bit picky about their lines either being first or last in the file. I don't run SRS but do have Tacview. My export.lua entries are as follows: local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]]) local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua')

Do you have any radio control mappings set up in DCS? Have you mapped the TX2 button to anything in DCS? If so, clear this and see if it helps Sent from my SM-T835 using Tapatalk

Please could you turn on Vaicom debug (I think you already have this enabled looking at the screen shots), restart VA and then post your Vaicom log file here. The logfile can be found in <your Voiceattack install directory>/apps/Vaicompro/logs Also, are you using any other DCS add-ons such as Tacview or SRS? Sent from my SM-T835 using Tapatalk

What different commands have you tried? If you try Inbound as a command what happens? Try them without DCS running and see what the log file says Another thought that occurs to me is how many keywords are in the VA profile (the pencil icon). Have you pressed the Finish button on the Vaicom Config Editor tab to copy the keywords? Sent from my SM-T835 using Tapatalk

Please could you also check your c:\users\Jose\Saved Games folder and see if there are any DCS folders other than DCS and DCS.openbeta.

Not sure about AOCS, but you can have the menu up in NORM mode as well. On the Vaicom config > Preferences tab don't check Disable Menus. This should mean the menus appear when you press the PTT buttons

As @Weegie says, the AutoBrowse is an option so that you don't have to say Page after the tab you want to view, but does mean that the Kneeboard will change back to the appropriate Vaicom tab when new information is received. If you don't have Autbrowse enabled then you need to say <tab name>....Page to switch to the corresponding tab on the kneeboard

A couple of thoughts: 1. This sounds like a similar issue to the WW2 birds 2. As it is not an official module it might not be structured the same way for radio comms because they don't have access to the DCS SDK.@Hollywood_315 might not, therefore, be able to do this Sent from my SM-T835 using Tapatalk

I don't have the campaign so cannot look at the mission construct, but it is possible that there are several ships with the same frequency, hence using Marking Moms as it normally forces the carrier to be the one that responds

Just checking you have bought the realistic ATC extension licence for Vaicom and installed it? What happens if you try Marking Moms rather than inbound as the first call? Sent from my SM-T835 using Tapatalk

Yes - that definitely doesn't look right. Make sure you have the OB slider checked, select the custom path option and point it at the root install folder for DCS OB (not the saved games) and then check fix registry. Hopefully on restart this should have sorted it Sent from my SM-T835 using Tapatalk

Have you set the sliders the right way in the Vaicom config window to point to the version of DCS you are running. Also, the logs you have attached are just extracts - please could you start up VA / Vaicom with Vaicom debug turned on and then close it down again and attach the log file (found in the logs folder in the Vaicom install directory) Sent from my SM-T835 using Tapatalk

yes - that is the Vaicom version of the Heatblur Wheel (there is some technical reason why they cannot both work at the same time)

I just copy the whole file back - if that doesn't work for you then keep the new Vaicom line and copy the SRS and Tacview lines back (keeping the lines in the same order) Sent from my SM-T835 using Tapatalk