Subfolders not being created.. I'm feeling stupid

[KiloBravo]

Hi. Any help would be appreciated.

 

Seems like this must be a common issue as it's in the FAQ. But I can't seem to get things working. I'm running an up to date Win10 version.

I have a registered copy of VoiceAttack, which I'm running as Admin.

I've enabled plugin support.

I've copied the VIACOM folder into the path C:\Program Files (x86)\VoiceAttack\Apps\VAICOMPRO

I've also tried using the .msi installer for Viacom

 

When I run VoiceAttack nothing happens. There are no subfolders created. I've check windows defender settings and allowed VAICOMPROM through. I'm not running any of the noted conflicting modules in DCS. I do use SimShaker for Aviators.

 

I've been trouble shooting this for a day now and am feeling like an idiot. Any help would be really appreciated.

 

Thanks

KB

[Olmba]

Maybe a blind shot, have you imported the VAICOM profile in Voiceattack? 

Edited July 5, 2021 by Olmba

[KiloBravo]

Thanks Olmba. There's no subfolders created so I can't find anything to import.

[Olmba]

Can you provide a screenshot of your "\VoiceAttack\Apps\VAICOMPRO " folder?

If you have done correctely it should contain one document folder and 2 files, like this:

  \VoiceAttack\Apps\VAICOMPRO\

                                                        Documentation

                                                        EULA.txt 

                                                        VAICOMPRO.dll                                               

 

Edited July 5, 2021 by Olmba

[KiloBravo]

Those are the three items that are in my that folder.

 

Thanks again.

[Olmba]

 

Then it seems to be a problem with voiceattack and beside from a reinstall of VA and VAICOM im out of solution.

[KiloBravo]

I tried an uninstall. Reboot. Repair DCS and then a reinstall. This time oddly, voice attack installed in the /program files/ folder rather than the /program files (x86)/ folder. 
 

I thought I may as well run with it and copied Viacom into the apps folder in that path and ... “voila”... VIACOM installed as advertised. 
 

I’ve yet to try it out. Hopefully the install path doesn’t matter too much. 

[hornblower793]

The install path will be because you have the 64-bit version of VoiceAttack and not the 32-bit one (64-bit is new)