Comm Menu Insists on Popping Up

[Jarhead0331]

There is a thread about this somewhere else in the forum, but it belongs in here since its clearly a VAICOM issue. The Comm menu just keeps popping up, closing and then a few seconds later, popping up again.

 

This problem is driving me up a God damn wall. I have tried EVERYTHING. Resetting lua, deleting export file, shutting down DCS and VA and reloading, rebooting, checking to make sure no keys or buttons are assigned to mic transmit commands, repairing DCS...nothing works, even if I disable menus in the config, it still happens!...what the hell????

Edited May 8, 2021 by Jarhead0331

[sthompson]

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.

[Jarhead0331]

Before I do all that, let me note this for the record. When I tried to install vaicomPro, the install file could not detect my installation of voice attack, which is the steam version. In order to get Viacom to install I had to install the free non-steam version of voice attack and then redirect the install location to my steam directory. Why was it not able to locate my voice attack install in my steam directory? Could this have something to do with my issue?

 

also, I think once installed, I may have loaded the .vap. Before enabling plugins in settings. Could 5is have something to do with my issue? 

 

Thanks. 

[Jarhead0331]

One more question...does VAICOM look for any files in the DCS users/saved games folder?

 

I have a new rig and for some odd reason I have a duplicate user folder in there on the C drive. I've never seen that before. One folder is my user name and the other is my user name with the name of the desktop pc. It is that second one that is set as my DCS saved games folder.

[sthompson]

7 hours ago, Jarhead0331 said:

Before I do all that, let me note this for the record. When I tried to install vaicomPro, the install file could not detect my installation of voice attack, which is the steam version. In order to get Viacom to install I had to install the free non-steam version of voice attack and then redirect the install location to my steam directory. Why was it not able to locate my voice attack install in my steam directory? Could this have something to do with my issue?

 

also, I think once installed, I may have loaded the .vap. Before enabling plugins in settings. Could 5is have something to do with my issue? 

 

Thanks. 

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.

[BoFrost]

Looks like you are logged in to your computer with an temporary windows profile. If it does not disappear after an reboot, you should remove it. Google how to delete windows profile. Just deleting the folder is the wrong way. 

 

[sthompson]

3 hours ago, Jarhead0331 said:

One more question...does VAICOM look for any files in the DCS users/saved games folder?

 

I have a new rig and for some odd reason I have a duplicate user folder in there on the C drive. I've never seen that before. One folder is my user name and the other is my user name with the name of the desktop pc. It is that second one that is set as my DCS saved games folder.

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.

 

[Jarhead0331]

I think I may have discovered (and hopefully solved) the problem. I was looking through the Vaicom config options and saw the one to set a custom DCS folder path. I read further about this in the manual and saw that sometimes the registry location is incorrect. I recently transferred my DCS installation from a mechanical drive to a new SSD. So I figured, maybe the registry got borked when I did the transfer. So I set the custom path to the new drive location and loaded up. No comm menu!

 

does this make sense? Is there anything else I should do? What about using the fix registry option? This makes me a little nervous though. 

Edited May 8, 2021 by Jarhead0331

[sthompson]

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.

 

 

 

 

 

7 minutes ago, Jarhead0331 said:

I think I may have discovered (and hopefully solved) the problem. I was looking through the Vaicom config options and saw the one to set a custom DCS folder path. I read further about this in the manual and saw that sometimes the registry location is incorrect. I recently transferred my DCS installation from a mechanical drive to a new SSD. So I figured, maybe the registry got borked when I did the transfer. So I set the custom path to the new drive location and loaded up. No comm menu!

 

does this make sense? Is there anything else I should do? What about using the fix registry option? This makes me a little nervous though. 

 

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.