sthompson

I don't think that's the problem. I've followed my progress against the waypoints on the kneeboard map and I do get the prompt to pop up and turn in just before waypoint 6. I am shielded from the ZSU's and Igla's at that point. It's in close right after I pass the last ridge where I start to get hammered. I tried again last night using rockets for the first attack instead of bombs and tried to jink more on the attack run. That helped and I was able to get over the ridge past the target and dive for protection. So I'm making progress. But when I turned back in for another run they took me down almost as soon as I cleared the ridge line. I'm still interested if you have any comments on the altitude issue, or what is the role of the detour out to waypoint 3. You didn't address those in your reply. BTW, I've now twice had an unusual experience where after being KIA I watched the other planes for a few minutes to see what they were doing and then paused the mission by opening the score page or the briefing. After looking at those I pushed the "Fly" button and immediately found myself back in the hangar at Krymsk sitting in a cold and dark undamaged plane, with the "Mission Complete" message in the corner of the screen. This resurrection and teleportation apparently increased my score to 100! But since I had not completed the mission to my own satisfaction I closed the mission without saving progress so that I can try again.

There is a thread on this bug here: A fix is posted in the thread, and @BigNewy has posted that ED is aware of the bug and working on it.

I'm puzzled by Mission 10. First, the briefing and waypoints in the ME tells me I should be flying the entire sortee at over 6,000 ft, but there are voice cues telling me to keep it low (1,000 ft AGL at WP 2, and to pop up at WP 6), and flying high seems to be asking for a SAM launch. The assigned altitude also seems to put me in the clouds a lot. I've been ignoring the assigned altitude as a result. Second, there is the weird path in the flight plan where I'm supposed to fly almost directly over waypoint 4 on my way to waypoint three, then do a 180 back to 4. I assumed that was to delay my arrival so I would be coordinated with the F-4s. What I find is that when I fly over 4 on the way to 3 I get a voice prompt to turn southeast (130 degrees) and follow the valley down to WP 5 and 6 rather than continue to WP 3. If I ignore that and fly to WP 3, then circle around to the north to go back to WP 4, 5, and 6, I'm quite late getting to the AO relative to the briefed TOT for WP 6. If instead, I turn as instructed and head for WP 6 I arrive at the target pretty close to the assigned TOT, but then find that the F-4s have not yet started doing their thing. Perhaps most frustrating is that when I pop up and then fly low and fast towards the target I'm getting Igla's (from Manpads?) and AAA from the multiple ZSU-23's right in the face and throughout the bombing run. So even when I successfully deploy some Paveways to take some of them out, the other ones get me before I can get over the next ridge and out of their line of sight. The briefing tells me that I should be coordinating the attack with the F-4s so that the enemy defenses are not totally focused on me, but that doesn't seem to be working. Also, my flight just follows me into the danger zone and either dies or bugs out without deploying any weapons. They do not engage or carry out the mission orders even when attacked. Any tips or suggestions welcome.

Yes, it's been noted before. I consider it a VAICOM bug. Hope Hollywood takes care of it some day.

I don't understand this description of the problem. VA would not hear a spoken command to "start listening" if it has already stopped listening. So you must mean something a bit different from what you wrote.

That is correct. This bug has been around for a long time. For me it's just a nuisance. When I want to make the menus appear (or more often to make them disappear) I press the communications key more than once as needed. It most often seems to need multiple presses when first starting a mission. I can see how this would be more of a problem if you are trying to press it via a VoiceAttack script. The problem is not the keystroke itself, but rather that somehow VAICOM is interfering with operation of the communications menu even when you do not have any of the special options (such as disable menus) selected. I could speculate about why this is happening, but without access to the code it's hard to know for sure, let alone to fix it. Perhaps you should PM Hollywood about it, or take it up through the official support channels.

The log says that the command is being sent to Overlord instead of Jester. Try using "Jester, Link Host Overlord." In general if a command is not working make sure you are specifying the correct recipient. Sometimes the recipient is identified by context and/or previous selection of a recipient. But in this case you only named one recipient in the command, namely Overlord.

I never saw a reply to these problems I've had getting started with the module. Can anyone provide some advice on how to get up and running?

You did not post the log. You posted a few entries from the log. And there should be additional entries if you had the debug feature turned on when the errors occured.

I suggest you turn on debug mode and then post what is showing up in the VoiceAttack recognition log when you give these commands. Debug mode will show more information about how VAICOM is interpreting the commands. Also, show us what your VAICOM PTT, Preferences, and Config tabs look like. Make sure you are still flying when you take a screenshot of the PTT tab. Also, is VAICOM PRO working properly otherwise?

Also, given that you reinstalled DCS on a new rig and are having an issue with multiple Saved Games folders I recommend logging into the account you use to run DCS and posting the contents of the following registry keys if they exist. Computer\HKEY_CURRENT_USER\SOFTWARE\Eagle Dynamics\DCS World\Path Computer\HKEY_CURRENT_USER\SOFTWARE\Eagle Dynamics\DCS World OpenBeta\Path (and the corresponding Steam version key if that is the version you are using) Also Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders\{4C5C32FF-BB9D-43B0-B5B4-2D72E54EAAA4} That last one identifies the Windows Saved Games system folder for that user. Yes, if it is working use the fix registry option. Your registry keys apparently are not pointing to the correct folder, or perhaps are not present. This would happen if you copied DCS to a new rig rather than reinstalling it from scratch.

That is very likely the problem. VAICOM definitely looks for files in the saved games folder. It both saves files there and modifies files that are there. If you post the requested information we can sort that out. But you should provide some details about your various Saved Games folders. In general a Windows PC should only have one Saved Games folder per user because it is a system folder. If you have more than one for the same user account then you didn't set up your new rig properly.

I don't use Steam, but my understanding from reading other posts is that you cannot use the VAICOMPRO install application with the Steam version of VoiceAttack. Instead you should download the ZIP file version and then unpack it into the Apps folder of your VoiceAttack installation. But I doubt if that is the problem if VAICOMPRO initializes when you start VoiceAttack.

This is a classic symptom of an incorrect installation where VAICOM is not updating files properly. It's sometimes caused by a non-standard or incomplete installation of DCS itself, and none of those steps will work if DCS itself is installed in such a way that VAICOM can't find the right files to update. If you want help in this thread then calm down and do the following, exactly, in this order: 1. Turn on the debug option in VAICOM. (It's on the config tab.) 2. Shut down DCS and VoiceAttack. 3. Repair DCS. 4. Restart VoiceAttack, then DCS. 5. Start flying a module and give one VAICOM command. 6. While still flying, take and save screenshots of the VAICOM PTT and Config tabs. 7. shut down DCS. Note the time you do so. 8. Expand the VoiceAttack window enough so you can copy everything in the log window. Save it to a textfile VoiceAttack.log. 9. Find DCS.log file. It should be in Saved Games\DCS\logs, or Saved Games\DCS.openbeta\logs depending on your version. (I'm not sure where it lives if you are using Steam.) 10. Verify that the dcs.log file has a time stamp matching step 7 shutdown time. This verifies that you found the correct file. If the time stamp does not match, look for a copy of dcs.log in other Saved Games folders until you find the one that matches. 11. Post a followup message here that includes all of the following info: a. post which version of DCS are you using and what is the full path to its root folder. b. post in which saved game folder did you find the dcs.log file (provide the full path). c. post your screenshots from step 6. d. post the Voiceattack.log file you saved in step 8. e. post the VAICOM.log file (Usually saved at "C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO\Logs\VAICOMPRO.log") f. post the dcs.log file you found in step 9. g. post whether there is a file dcs_variant.txt file in your DCS root folder and if it is there post that file too. Otherwise let us know it is not there. That should give us enough information to tell what is wrong with your installation.

Did the "End Mission" button take you back to the main Campaign page? There is currently a bug that causes End Mission to not work correctly sometimes. There is a fix posted in another thread. Look here:

Atlantic Wall mission for the P-51 on the Channel Map. (See the original post.) However I've since learned that there were other versions of "Atlantic Wall" for the Spitfire and P-47 that had the same issue. I haven't tested to see if those were fixed since I'm not really competent in those aircraft.

Seems to be fixed in the latest update. However whomever created the mission messages and voiceovers should be told that a right turn is a turn to "starboard" not "port."

How do you manage to drop just three in ripple mode? For me all five come off before I can react. And what interval? I've found that if I use the smallest interval then I explode no matter how high I am. Tacview indicates that the bombs are exploding while still in the air. Or are you not using ripple mode? And do you really mean 100 mil depression? That's even more than recommended with dive bombing. I'm having trouble finding recommended parameters for the snakeyes.

The VAICOM PRO add on has a feature where such radio communications with the tower, or tankers, or AWACS (but not wingman) are copied to a dynamic kneeboard page. Unfortunately the 2.7 openbeta seems to have broken it. But perhaps this will get worked out before 2.7 goes to standard release.

You certainly can use different buttons for VAICOM. It's just a matter of changing the assignments in your VAICOM PRO profile within VoiceAttack. Review the manual instructions on initial setup for details. You don't say how you are communicating with your squad in MP. I'm guessing you are using the same buttons for radio selection in VAICOM and SRS. If you want to keep using the same buttons there are a number of options, including the SRS integration options built into VAICOM and described in the manual. But the solution I've found works best for me is to turn off the SRS option where a radio selection key also works as PTT, and then map a different button for SRS PTT. I use that same button for Discord and Teamspeak PTT in case I'm using one of those instead of SRS.

Open a cmd or powershell window and execute C:\Program Files\DCS-SimpleRadio-Standalone>DCS-SR-ExternalAudio.exe. It will give extensive help information about how to use it, including the new parameters. However I've never used it and can't offer additional suggestions. Cribob responds to queries on the SRS Discord channel.

I mean copy f:\saved games\dcs\config to f:\saved games\dcs.openbeta\config. Now that I think about it, you might want to copy other subfolders as well: Views, Scripts, Mods, MissionEditor, Liveries, Kneeboard, etc. Anything that has configuration information. As I mentioned, please backup first. As an alternative to all of that copying you could rename f:\saved games\dcs.openbeta to something else as a backup, and then rename f:\saved games\dcs to f:\saved games\dcs.openbeta.

Now we are making progress. I assume you mean that the dcs.log file was found at path F:\Saved Games\DCS\logs\dcs.log. If that is the case and you are sure that you are using DCS version 2.7 openbeta then it means your DCS installation is messed up, because the log file should be written in F:\Saved Games\DCS.openbeta\logs\dcs.log. Thus DCS is using the wrong Saved Games subfolder, and is not reading the export.lua file or VAICOMPRO files saved in the openbeta subfolder. Next step: Look in your DCS root folder for file G:\DCS World\dcs_variant.txt. It should be there with one line reading "openbeta" only (with no newline at the end). I'll bet it is missing or says something else. I just ran a test on my system and determined that a "Repair DCS Open Beta" run does NOT fix this file if it is missing or has the wrong contents. To fix DCS create or edit that file (or use the one attached) in your DCS root directory. That should cause DCS to start using the dcs.openbeta subdirectory of Saved Games. BTW, you will also want to copy your config files over from the dcs to the dcs.openbeta subfolders. BACK UP THE SAVED GAMES FOLDER FIRST IN CASE MY DIAGNOSIS IS WRONG! dcs_variant.txt

Debug is an options in the VAICOM configuration window. I believe you may have it turned on already based on the screenshot you posted. Let me suggest you double check all of the following, which includes detail about the DCS log: 1. Start VAICOM and verify that Debug is selected. Then shut it down. 2. With DCS and VA both not running, do a full repair of DCS, then restart VAICOM. Once it finishes initializing start DCS. 3. Enter a flyable module with supported radio and give a VAICOM command, then shut down DCS. 4. Expand the VoiceAttack window as needed so that you can see every entry. Copy and paste that to a text file. Call that VoiceAttackEventLog.txt. 5. Close VoiceAttack. Look in C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO\Logs. There you will find VAICOMPRO.log. 6. Go to Saved Games\DCS.openbeta\logs and look for the file dcs.log. MAKE SURE THAT THE TIME STAMP ON THIS FILE MATCHES THE TIME WHEN YOU CLOSED DCS IN STEP 3. If it does not then that is a clue that DCS is using a different Saved Games folder from what you are expecting. 7. Post VoiceAttackEventLog.txt, VAICOMPRO.log, and dcs.log here.

Perhaps you could post your VAICOM log (after making sure that debug is turned on) and also your DCS log. I'm wondering if DCS is showing any errors that might be related. Your symptoms suggest that DCS is not able to communicate with the VAICOM plugin. If you are running firewall software you might make sure that the ports used by VAICOM are not blocked. These are IP ports 33333, 33334, 33491, 33492, and 44111 all on UDP protocol.