Shane45

Some of you guys who are still having problems with getting VA / Viacom to work may want to to try this, If you've read through the posts you'll know I was losing the will to live :) with some help from Hollywood , Greyman, to name but two I eventually got it working, When I said I had done everything as was explained in the Viacom manual and followed it all to the letter, that was just not true although I thought at the time it was, However having installed / uninstalled numerous times, I decided to Repair DCS World 1.5, and lo and behold, it worked. So if you have done everything as instructed and it's still not working, try repairing DCS , it worked for me, it might for you. Big thanks again to Hollywood and Greyman for their input and patience,

A picture paints a 1000 words, and will make much more sense than me trying to sound like I know what I'm talking about, Start Mission worked with the 1.5.8 VA, as said in pm, I then got dumped on the tarmac and no further comms. I really don't believe I'm doing anything wrong but then I'm no expert by any means, Thanks for our help HW

That didn't work, getting nowhere fast.

I'll give that a go das, thanks, Believe it or not I've spent the best part of a week trying to get this working,I've installed and uninstalled so many times I've lost count. I think ! the main problem is the fact that I'm not getting these beeps we should hear to confirm that the command / msg has been copied, the only time I get beeps is while I'm in the VA Log window prior to going to the pit, I get static at the start and finish of the call and also a beep if the command has been interpreted correctly , but as soon as I go in the pit I get diddly shit, I'm at a loss as to what the actual problem is and how to work it out. Davidson's Youtube vid was good but Hollywood has made the whole thing better since that was recorded, I think it would be really helpful and useful if someone who has this VA / Viacom program working as good as it should be, to make another vid , with screenshots so us not so computer savvy users can actually see what our folders / files should look like, If anyone out there would be willing to do this, I for one would be extremely greatfull as would so many others.

Hi GM, I've wiped everything to do with VA / Viacom and reinstalled with the appropiate Mods My radios are behaving as they should within the VA Log, I'm still getting static and the odd beep whilst resetting profile, running thru a few keywords before going into the mission. The one I've used tonight is the Instant action / East Georgia, no comms what so ever. Thanks mate

Thanks GM, I'll post one here shortly, for some reason, of my own making, I've run into another problem, and they just keep coming :)

This is seriously pissing me off, I have checked and treble checked, everything is good in the VA Log, ie static / beeps, key words being recognized etc etc, however Ramp start free flight mission, start mission, negative, any comms at all ? negative, the only thing I do get is the F menu when I call Menu options, and that is that. Would someone who has this working kindly take some screen shots of various files from start to finish, alot of you guys on here are very puter savvy, some of us are not and a picture makes more sense than trying to find a file and then interpret it, if that makes sense. with my limited knowledge on how this all works I am finding it extremley frustrating to say the least, cheers ta thanks

Start mission has never worked for me, I've reset profile whilst in the pit, etc, I have had the occasional beep, as you say when I've mentioned an Airbase or so, THE BEEPS After speaking your command with PTT, listen for soft beep sounds. These will give you feedback on how your command was processed. Note: VAICOM 2.0 has a slightly wider range of beeps than version 1.1. Blip 1 and Blip 2 : Confirmation beeps. If your command was successful, these two beeps will be heard in rapid succession (< 1 sec.). The first beep indicates start of command execution, the second beep means execution complete. Don’t release the PTT key before you’ve heard the second beep: releasing too soon may mean the command doesn’t get properly executed. Note: Some special commands such as ATC Select produce a single confirmation beep. Note: For some special commands you may hear a sequence of beeps. Reply Beep: You will hear this single beep to confirm a Reply statement such as ‘Roger’. Error Blip: No one said it would be easy  If there is something wrong with your command you may hear the Error blip before or after you release PTT. Retry your command. An error can have lots of reasons, you may need to check the VA log to identify the issue. Some examples: • Unrecognized or misinterpreted command • Wrong recipient / command combination e.g. call ATC, request picture • Flow error, e.g. calling JTAC playtime 15 while you are checked in already Note: If you think you can do without the beeps (ehm, are you sure?) , it is possible to switch them off. See Advanced Settings section. I have yet to get a reply from my wingman or even be able to execute a JTAC command, I have however managed once to get startup and taxi from the tower at Beslan ( Smerch Hunt Mission ) but that was it, the bastard left me on the runway with no throttle movement :)

Rgr that GM, REF Keyboard , yes I've switched it to US, I still can't seem to get these command confirmation beeps, I hear the initial beep when opening VA, but no matter how long I keep my PTT button pushed fwd.dwn. rear, I get no beeps

Thanks GM, Thats what I've been doing today , basically every key word, airfield etc etc. Most of the commands I use are being interpreted correctly as the log shows, every now and again it throws one out, I've just been on a Instant action mission, no comms with the wingman, prior to that I was sat on the ramp and on the command ' request startup ' it threw me out on to the tarmac, I'm still geting the static and the occasional beep which I understand means that the command was true and again this shows on the log, I've got easy comms on so I can use the F menu, to get this I have to use the backslash key, unlike in normal DCS a push on the Mic switch will bring up one of the three radios on the comms menu. just going to crack on and play around with it, I'll get there sooner or later. Thanks again

Went on a Smerch Hunt from Beslan, And for the very first time managed to ask Tower for startup, request taxi to runway, and that is where it stopped, frustrating as a big frustrated thing.

Greyman, quick one for you, I now have sound in my headset, ie static, but I'm not getting the confirmation beeps, to that end I am not getting any comms with anything or anyone, but am able to use the comms menu key. cheers

Hollywood, you sir are on my xmas card list, I deleted the Viacom package from VA program, opened up the Viacom package folder and just took the Viacom folder and placed it inside the VA / Apps folder, and hey freakin presto, Thank you and thanks to everyone who helped me out. Much appreciated

Losing it, how does this , C:\Program Files (x86)\VoiceAttack\Apps\VAICOM 2.0 package\VAICOM. Become this , 22:01:05 - Error accessing sound file - C:/Program%20Files%20(x86)/VoiceAttack/Apps/VAICOM/Sounds/UI/Radio_Noise.wav Answers on a postcard please :)

Cancel my last, they are .wav files, it says so in the VA Log , duh!

I have followed it to the letter GM, the Num 0, num 1 etc all pull up the same error, I've just gone on the VA website and it says on there that these sound files should be in .wav format, I've just picked a randon sound file in the chatter folder and it says it's an .aac file, are your sound files .acc or .wav ?? Thanks for all your help buddy

GM, I've just reinstalled everything and nothing has changed, it wasn't until I connected my throttle and then spoke into the mic, that , that particular file showed up. Windows is the normal home version Thanks

They have always been in there GM, it was the file within the VA Log that I was trying to find ie the sound file with the % within the file name, Thanks GM

I've tried to find that sound profile but to no avail, the sound files themselves are uneditable as such, I've downloaded Viacom from Hollywood's User Files 6 times and they are all the same, so something is happening when the Viacom is being unzipped. Can you confirm that the VA download goes into Program files x86, having said that I have put them into program files and I still get the same result. should there be sound files in the VA Sounds folder ? cheers Greyman

got the buttons sorted, can't figure out why I'm not getting any static etc in my headset.

Viacom Voice attack probs Just a quick one, should there be sound files in the VA Sounds folder ? Also whilst pressing either of the radio buttons , as soon as i press to speak it's released and I get what you can see in the VA Log and the headset icon shows Not listening.

Viacom Voice attack probs Cheers Greyman, Just sorted the press and release issue, went in the pit / air start and tried to chat to Kutaisi , no answer, but also lost all control of the a/c . ie no input from the stick, acted like it was on autopilot, I've just checked the Viacom folder, in the sub folder I have Docs, Profiles, Sounds, Tools, and Utilities, In the sounds folder I have Chatter and UI, within UI is a series of sound files, Blip's abd they all work, I take it those are the ones that I should be hearing when transmitting, ie the static on Press and release and the beeps to ackn that the call has been passed, Nothing in my headset though, Well at least I'm a little further ahead than I was yesterday :) many thanks

Viacom Voice attack probs I give up, the only thing I can seem to get working is the correct radio setup, No static, no beeps, no comms. I get in the pit, try and talk to the tower to request startup and find myself out of the aircraft on the tarmac staring at my a10c, very strange.

Viacom Voice attack probs Glad you got it sorted Unpilot, I'm losing the will to live trying to get this to work, :( Can someone have a look at these and tell me if they loook like they should look, still can't get static and the beeps when transmitting, and of course absolutley diddly shit whilst in game. cheers ta thanks