VoiceAttack won't start

[Megnin]

I have VoiceAttack installed through Steam.  It won't launch from the Steam launcher or by directly double-clicking the VoiceAttack.exe file, with it set to run as Administrator or not.  When attempting to launch it from Steam, the Launch button just returns to "Launch."  When double-clicking the file, the UAC prompt pops up and when I click "Yes", the prompt goes away and nothing happens.  There are no error messages in either case.  I found the VoiceAttackFault.txt file, but it did not help me.  Maybe it will give you some information.  It's attached.

Thank you.

[Pfeil]

There does not appear to be any useful information in the fault log, unfortunately. The third-party EDDI plugin crashed twice, but that's when VoiceAttack was already shutting down, implying it started correctly at that time.

Though, it is possible that a crash on shutdown may have damaged something.


If you hold the Ctrl and Shift keys on your keyboard while VoiceAttack is starting, does the load options window show up?

[Megnin]

Well, it does launch after I restart my computer.  But, I have to restart my computer every time I relaunch VoiceAttack.  I just restarted my computer, so VoiceAttack did launch. 

The VoiceAttackFault.txt file doesn't appear to have any new entries now.  I'll check again when I try to relaunch it and I'll see what happens if I hold down Ctrl and Shift while it's starting.

[Pfeil]

If restarting your computer works, what's likely happening is that something is preventing VoiceAttack from shutting down completely.

When you try to start another instance of VoiceAttack, that will detect the instance that's still running, and shut itself down.


Given the messages in the fault log, it's quite possible a plugin is causing this. To rule that out, disable plugin support, close VoiceAttack, open Windows Task Manager, on the "Details" tab find "VoiceAttack.exe", right-click it and choose "End task", then try starting, closing, and starting VoiceAttack again, to see if the issue persists.

To disable plugin support, click the wrench icon on VoiceAttack's main window, and on the "General" tab of the VoiceAttack options window uncheck the "Enable Plugin Support" option, click "OK", click "OK", then close VoiceAttack as mentioned.

[Megnin]

It does seem to be failing to shut down.   When I close the VoiceAttack window, Steam never "releases" it.  Steam continues to say, "VoiceAttack - Running."

This time, when I clicked "Stop" in Steam, it shut down, the Steam button returned to "Launch" and VoiceAttack did restart.  It warned me that I "may" have to set it to run as Administrator again if commands don't function.  Is it recommended to have it set in VoiceAttack settings to run as Administrator?  Or, just in File Explorer?  Both, neither?  I think Steam also has a "run as Administrator" setting.

VA is currently running, so I'm going to fire up Elite Dangerous and see what happens.

I thank you for your help.  I'll report back when I have more information.

Thanks!

[Pfeil]

It warned me that I "may" have to set it to run as Administrator again if commands don't function.  Is it recommended to have it set in VoiceAttack settings to run as Administrator?

That message is informational, in case you're running another application as administrator and want VoiceAttack to be able to interact with it.
Windows does not allow applications that aren't running as administrator to interact with those that are.

Unless you encounter such a scenario, there should be no need to run VoiceAttack as administrator at all (and if you do, it's worth evaluating whether the target application actually needs to run as administrator in the first place).

[Megnin]

Gotcha.  I am trying to run the EDCoPilot plugin in VA.  I don't recall if I set EDCoPilit to run as Admin or not when I was installing EDCoPilit, or if it matters for the .vap plugin.

When VA started it didn't mention the loading an EDCoPilot plugin.  It did report that the OpenAI API Plugin initialized.

[Megnin]

I guess EDCoPilot plugin loaded okay because saying "Open EDCoPilot" to VA caused EDCoPilot to open.