supercruise assist non fonctionning

[Serge]

Hello,

My configuration is :
* Elite dangerous Horizon
* HTC voicepack A.S.T.R.A
* Voice attack in the most recent update.

I have installed the package and everything seems to work fine in game except the "Engage supercruise assist" and "Disengage supercruise assist" commands which do not get any response in voiceattack. No error messages but no response either. I have tried/customised several triggering phases but none of them are taken into account.

Of course if I engage the supercruise assist manually from the game navigation panel it works.

I specify that I use the French trigger set (French Singularity - Custom.hcs).

Is this a bug? Do I need a special pack?

Thank you.

[Gangrel]

1) Is the command recognised in the VA log window?
2) Make sure that you have the target highlighted before you say the command.

[Serge]

1) no, the command do nothing in voice attack : no error, no warning, nothing. I've try severals triggers but none seems to be "listened"
2) i'm sure of that, and if i manualy engage de assist with the navigation panel, it works

[Serge]

the only reaction in VA is the icon at the top right which indicates that the command is not recognised

[Gangrel]

Huh. I am trying with the English voice trigger file, and it is being recognised by that. And the variable name (internally) is the same in both the English and French voice trigger file. In fact the whole entry is *identical* between the two.

Now, I do not have the french voice recognition language installed on my machine (my spoken french is very basic and broken), so the only thing that I can think of is that the *french* speech recognition engine is having issues with this phrase.

It is working in the English version of the voice trigger file, and as I said, the line in the voice trigger file is *identical* between the two languages. So it could just be the french recognition language having issues with the english works.

I will try to hammer down on this though, but I am not sure what the solution will be in the case for you. When you say you have tried several different triggers, are they in *english* or in french?

[Serge]

Hello, thanks for your answer and your research.

I don't think that's where the problem lies, here's why :

I reworked all the originals French texts to put triggers that suit me better (also in French). All my triggers are in French and my French speech recognition works well, I usually have a confidence index of >90% in VA.

Anyway, to be sure that I don't have a problem of comprehension, I did some tests with a simple word like "test":
* "test" as a trigger for "Engage/Disengage supercruise assist" = KO...
* "test" as a trigger elsewhere = OK without a problem.

I tried also to switch back to the English version of the triggers and the problem persists. In the English version, "test" (which is quite easy to pronounce, despite my French speech recognition) does not work on "supercruise assist" but works anywhere else.

nb: I also tested other words than "test

Can I email you my "French Singularity - Custom.hcs" file so you can see if there is a problem in it? if yes which email ?

I'd also be curious to know what command is called "internally" to activate supercruise assist, as there are no keyboard shortcuts for this autopilot in elite dangerous horizon.

Sincerely.

[Gangrel]

I am testing with the English spoken trigger file, and "Engage Supercruise Assist" is being recognised as a spoken command.

I use the voice trigger editor to make the changes (this is the recommended method), and added "Test" to the end of the line, and when I say "Test", it is picked up as such. Supercruise Assist is still recognised as a spoken command.

You can email me your custom voice trigger file to gangrel@theqnn.com.

Internally, it calls upon the command {TXT:hcsvtED_SuperCruiseAssistOn} or {TXT:hcsvtED_SuperCruiseAssistOff} depending on which command you are actually using. Yes, I know that the command is named funny, but this is how we deal with:

multiple difference voice trigger files, a single profile per game, whilst also locking the profile so that it is in a known state and able to be updated automatically via the plugin.

Note: So as to *why* it isn't picking up the change or even recognising the basic spoken version of the command is what is confusing me. If you have been manually editing the file directly, then I can see that causing issues, especially if you ended up making a mistake.