I have given up trying to make voice attack work. I don’t have a background in computing and that means I need their help to the extent that they ignore me now. 3.3 broke it completely. “ I can’t make it work, tell me how?” I asked...”it’s only you” was the response. Sad really, was good for a while though but.
Going though all the debug files discovered a "corrupted heap" given I had uninstalled VA re-installed VA numerous times to try and fix my issues, to no avail
I went with a more complete solution, just for Voice Attack.
I used this Revo Uninstaller 2.0.6 Free to uninstall VA and used the advance mode to removed all the registry keys associated with VA.
Next step used Everything Search Engine to delete every folder belonging to VA, rebooted and then re-installed VA, ( you need to re-enter your license key)
Seems the VA uninstaller leaves stuff behind, which if corrupted, 'seems to be' reapplied. In any event doing all that has fixed my issues (I hope) for VA worked for hours without crashing and without a muted mic, and with my favorite plugin the G19 app for Elite dangerous running, the fault with VA was never my PC but with VA itself !
If anyone is interested in the Dumpfiles and Error logs associated with the drama I had with Voice Attack PM me.
Voice Attack was not interested in looking at these files, even after I asked repeatably asked for these logs to be taken and viewed to assist with a Fix and to help stop others from having problems in the future.
I had heaps of issues with the HCS plugin and Voice Attack, panels was apart of it and been slow responding to commands, that and the mic always been muted, had to keep saying "Wakeup" before each command, it nearly crashed me a few times.
Voice attack itself, keeps closing down, and HSC and Voice attack kept suggesting it must be other third party apps.. ( one of the most used ones) So I deleted / uninstalled that widely used app and the issue of VA closing down and the muted mic still kept happening. Finally I gave up on HSC and VA in Discord in trying to find the problem, as there was no real help forth coming, from either VA or HSC.
So posted in Voice Attack on steam asking if anyone else had the same issues I was having, to see if I could find the problem, only to have that Steam post "disappear". (got another thread going today)
So I decide to remove/uninstall the HSC plugin as that was the only plugin left ( which is a problem using VR now as I cant play without Voice assistance ) and all my binds in ED Options where wiped !.
it was a real mess, still sorting it out, even put in a tick to Frontier ( no help there either) So I went back to HSC Discord, an HSC said "impossible its not HSC Plugin" that could wipe your binds...whatever.
Fact is I deleted HSC Plugin and my binds go south, not making this nightmare up !.
So then I'm left with, no binds and no HSC Voice pack, and no other plugins just plain Voice attack, and still VA keeps shutting down, but at least the mic was no longer muted.... progress hahahaah !
Its clear this problem is seen as 'my fault' or the "PC fault" Yet Ive ran every scan on the system have a paid anti virus and this PC is a 2018 PC gaming build, has the latest of everything, its used for gaming nothing else, built for VR
Ive ran Windows 10 file checker 3 times now, had the Tech from the shop where we pick each part and who built my PC, come to my house ( paid for the service) to check nothing is wrong with my PC !
( bench marks where above avg )
YET STILL VOICE ATTACK KEEPS SHUTTING DOWN.
So in answer to your question is there anyone else having issues .. yes me .. the Question is are there any more players with issues ?
'
This is the error code for Voice Attack shutting down
Faulting application name: VoiceAttack.exe, version: 1.7.3.0, time stamp: 0x5bf1e60a
Faulting module name: ntdll.dll, version: 10.0.17134.556, time stamp: 0x319e0a75
Exception code: 0xc0000374
Fault offset: 0x000d8529
Faulting process id: 0x25c0
Faulting application start time: 0x01d4afbeb5f2c680
Faulting application path: C:\Program Files (x86)\VoiceAttack\VoiceAttack.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: e1feb26f-2ca9-4df1-aac1-b55e24453cdb
Faulting package full name:
Faulting package-relative application ID:
Thats a HEAP ERROR being reported by the Kernel. Without debugging the app with the source code- we can only suggest things to do to eliminate possible errors.
On assistance from VA, I had a short discussion (Programmer to Programmer) with one of their Developer Bods years ago and found him a pleasant helpful chap.
I'm going to ask some Idiot Questions - that means you are free to think me an Idiot for asking the obvious, but Eureka Moments come from the oddest places sometimes!
Are you running VA in ADMINISTRATOR MODE? (some years ago Win10 decided to remove elevated permissions from a plethora of Programming Libraries)
Is/Are your BINDS files in the place that VA and ELITE expects to find them?
Are any of your BINDS file READ ONLY?
Do you have the TARGET window in VA selected to ELITE Client or TARGET WINDOW?
Have you noticed when VA falls over, is it consistent at the same point each time?
Have you just "spoken" to or given VA Commands to see how it responds? (ie. set to target window, open notepad and give it focus....speak some commands to se if VA can comply)
There is the extremely small possibility of the ntdll.dll library being ugh! There are instructions online on how to replace it.
What Motherboard are you running? My current ROG ASUS Z270F sound chip isn't worth a diddly - just doesn't work with headsets properly. Gave up and run with a DAC USB Fob.....saves me loads of grief.
Finally, one of the worst things to consider is either dodgy RAM or Sector in your HD! Intermittent memory faults are a pure sod to tie down on occasions. Try one of the free online memory stress tests, see what they suggest if anything.
Don't get yourself griefed out over this. I spent over 3 decades in IT, sometimes the only way through these things is to treat them as a detective puzzle not a problem - if you can be arsed that is - the hardest puzzle for any developer to determine is the one he didn't look for in the first place!
Just a reminder to 'play the ball, not the player'. No need for name calling. Thank you.