GIJoe

I ended up creating symbolic links as well. My attempts to fix the registry did not work. I also seem to be unable to get the custom path option to work as well. Manual installs do work, but symbolic links added the auto-install functionality back for me. YMMV

Experiencing a similiar issue as above after today’s update. Only with the F/A-18C, at least for me. The commands will pass through only after I press any of the active PTT keys a second time. Tried the A-10C and commands go straight through to DCS with no additional PTT presses required. May try rebinding my keys, but this is a real nuisance issue right now. Edit: This is with 2.5 Open Beta. Update: After going into my VA setup and doing the unassign/reassign joystick thing, all commands are going through to DCS with one PTT press and release on the Hornet. Tested the other modules just to be sure. All good. Might be a coincidence but I am a happy camper again. Love this software!!

I believe this same issue with the update broke my VAICOM setup as well. PTT buttons are activating comms menus even if you clear all PTT key binding assignments (and apparently only when using easy comms). EDIT: Appears I had an issue with my setup not caused by the update. Good to go now with VAICOM.

From a former USN Officer of the Deck qualified on carriers, that is exactly how we did it. Maneuver the ship to place winds straight down the angle. I concede that with no true wind, you probably set up somewhat of a crosswind situation with own-ship driving the winds over deck.

Same here! Probably some of the best money I have spent in this hobby.

Been using these profiles with 1.5.8 for a while. Much appreciated! Any chance this can be updated for 2.5? I tried the current version in 2.5 and some of the ATC tower calls are not working.

I like the whole VR only concept. I am mainly an A-10C flyer in 1.5, but will do 2.5 if that is where the crowd is. Have Harrier, and looking forward to the Hornet module! Will be keeping my eye on this effort and hope it takes off (pun intended)!

Did the same. Jury is still out on performance, as I haven’t had time to test fully. Cockpit lighting is still an issue for me, especially in the A-10C. Cockpit is still very dark with almost pitch black consoles. Some over saturation in the colors as well going on from my point of view. Just look at the ECM system console lights on the right panel. Outside world looks pretty good! Nevada and Caucasus especially.

All, Hollywood got me straight with this issue by helping me deconflict some programs I had installed! BT New question. Does anyone know if 2.5 Pro works in 1.5.8? Does it require a manual install? I have Pro running just fine in 2.5, but wanted to see if I could get it going in 1.5.8.

I am having issues with getting it to work in 1.5.8 as well. I had it working before, but maybe an update changed some things? Really would like to get this going again because I prefer 1.5.8 over 2.5 right now. UPDATE: Got it working. Had to repair my 1.5.8 installation.

VA crashing when opening plugin configuration window Just purchased and downloaded 2.5 Pro. Everything appears to be working, however, I get consistent (100% reproducible) VA crashes when pressing LCtrl+LAlt+C to open the the plugin configuration window. When VA restarts, it prompts me to try disabling plugins as a possible solution and suggests that an individual plugin may be causing the crash. As I said, I am running the latest version of VAICOM 2.5 and using the latest plugin as far as I can tell. Trying to register my program and chatter license. Any assistance is greatly appreciated!!

I have tried both, and have had more success with VAC recognizing my voice. Probably something that varies depending on the individual. To me, the price of either was reasonable enough to try them both.

Got it! Thanks!!

Wolf, I have been searching the forums to find this answer, but must be missing it somehow. How are you disabling the clouds in DCS? Probably a noob question for sure.

+2 for this solution!!

You have to leave it open for the settings to remain in effect. You can miminize it if needed, but keep it running.

Single mission only in 2.0. Nevada takeoff I believe is the name of the particular mission. I thought it might be a problem with the fetch cmd as well, but I followed all the instructions on how to modify the file to point properly in 2.0. Tried Hollywood's testing suggestions as well. No joy. Funny thing is when I did the same thing for 1.5(made modifications to the fetch file), everything worked just fine. Been enjoying that so much, have not given much time to continue to troubleshoot 2.0. Probably get back at it this weekend. I hate having an unsolved issue.

I believe so. Just purchased it the other day. Will confirm, and thanks for the insight on the messages. I have yet to get any indication that my setup is right, however. No responses from my wingman ("2") to any commands, but I do hear the response beep from VA. Still working the problem to get up and running.

Voice Attack Errors All, Getting the below errors when loading the A-10C profile in VA. Read here from Davison that a possible fix was to run VA as administrator. Tried that, but still getting the errors on load. Any assistance is greatly appreciated. Joe 02:32:37 PM - Listening suspended 02:32:37 PM - Ready for commands. 02:32:37 PM - Unable to get value from URI - Could not find file 'B:\VoiceAttack\Apps\VAICOM\Tools\TEMP\mission.lua'. 02:32:37 PM - Unable to get value from URI - Could not find file 'B:\VoiceAttack\Apps\VAICOM\Tools\TEMP\mission.lua'. 02:32:37 PM - Easy Communications is True 02:32:37 PM - Unable to get value from URI - Could not find file 'B:\VoiceAttack\Apps\VAICOM\Tools\TEMP\options.lua'. 02:32:37 PM - 'B:\VoiceAttack\Apps\VAICOM\Tools\VAICOM_fetch_data.cmd' completed 02:32:37 PM - Launched 'B:\VoiceAttack\Apps\VAICOM\Tools\VAICOM_fetch_data.cmd' (hidden) (waiting for exit) 02:32:37 PM - Fetching settings data.... 02:32:36 PM - Initializing.... 02:32:36 PM - ---- VAICOM 2.0 for DCS World ----