A couple of annoying issues - voice control and fighters

[Filbert]

First up, please let me express my appreciation for the voice packs and all the work you do - I can't imagine playing Elite without them. I am, however, facing a couple of admittedly, fairly minor irritations and am hoping someone can shed some light on them.

First of all, I don't use a headset, I use a desktop mic on a stand and as such I have VoiceAttack set to only listen when I push a button. 99% of the time this is fine however occasionally, VoiceAttack decides to randomly start listening even though I have not pressed and am not depressing the push to listen button. It just happened now when I was tabbed out watching a Youtube video. The only notification I get is a voice suddenly says 'Voice control on' or 'Crewman Kate standing by' or similar. It then proceeds to execute a random command presumably that it picked up from the background noise. Usually this is turning the lights on (for some reason, Voice Attack seems to interpret just about any random noise or keyboard click as 'lights') but on one memorable occasion it tried to self-destruct my ship - luckily I was in supercruise and it couldn't execute the order. Once I notice VA is listening for no reason, I have to press the button to suspend listening. Please help, this is incredibly infuriating! I realise it is most likely a VA thing rather than HCS but I am hoping you will have greater insight than me.

Secondly, I love the red/yellow alert command as I can issue it in supercruise and it will execute when I drop out - handily, most pirate NPCs will tell me when they are about to interdict me. I have tried checking the option to deploy fighter on red alert but sadly, it tires to do this in Supercruise. Is there no way to have it deploy fighter on supercruise exit along with the rest of the red alert functions?

[TheThingIs]

sorry for the delayed response

firstly in the recognition tab of VA settings, set the command weight to 0. This is how hard it tries to match what it thinks you've said to a cmd in the profile. This should help with false triggers. You can play with the setting as you wish though.

When listening in VA is off, it's actually always still listening but only actions cmds which would turn the listening back on. We do have cmds in the profile to turn listening on and off which is what is happening here. The above should help with that. You could change the voice trigger in the editor in the customiser as well or set it to something unpronouncable to turn it off. Another option is to have your toggle actually switch off your mic instead of VA listening, although that wouldn't help if you are talking with someone as well.

It should deploy the fighter on supercruise exit, I'll check to see if something is out of plonk.

Thanks,

TheThingIs

[Filbert]

No probs, thanks for the advice. I hadn't realised that you could bind a key to turn a mic off so I will give that a go. I only play in solo mode so taking to others isn't a problem.

Re the yellow/red alert supercruise thing, I can't test it again as I am miles out of the bubble without a fighter bay to test with but I will give it another go when I get back. When I first tested it, VA opened up the panels to deploy fighter and was flicking through them. I don't think it did anything because the panel tab was out of order which is why I assumed if the panel had been in the correct location, it would have actually deployed the fighter. Does it issue the command to deploy (ie. flick through the panel and select to deploy the fighter) while is supercruise but the fighter doesn't actually launch until exit? Or should it be waiting to exit supercruise before even opening the panel?

[TheThingIs]

it should wait until supercruise exit before it does anything

[Filbert]

OK, got back to home station and tested the Red/Yellow alert whilst in supercruise and I can confirm it does try to deploy the fighter in supercruise immediately after the alert order is given. It can't actually complete the order because the fighter deploy button is greyed out. Everything else (pip management and hardpoints) is done once supercruise is exited.

[Filbert]

Just a quick response to this after the recent-ish HCS updates and after moving to my new PC - HCS no longer attempts to deploy the fighter in Supercruise so that bit is fixed, however, it is not deploying the fighter on exit of supercruise as it should. It does all the usual red alert stuff (pips, hardpoints) but no fighter launch.