[Trivial Psychic]

Confirmed.  The last CVS build to function properly with -voicer was 2006/02/22.  All since give the same error message:

"Error: Failed to load resource"

followed by:

"Error: Failed to init voice rec"

Anyone able to provide some insight on this?

[Herra Tohtori]

*bump*

3.6.9 RC3 also gives the same two messages.

Original voice recognition build works - on behalf of voice recognition, that is. Other things are not as good as with newer builds, OGL env mapping is not there, and it's not as stable.

Furthermore, Taylor's 20060513 -build doesn't give the error reports, but the recognition doesn't seem to be working in-game.

[karajorma]

Recognition is broken and no one except Random Tiger ever understood how it worked in the first place so it's likely to stay broken.

[Ace Pace]

Recognition is broken and no one except Random Tiger ever understood how it worked in the first place so it's likely to stay broken.

So will someone take it out atleast?

[taylor]

Recognition is broken and no one except Random Tiger ever understood how it worked in the first place so it's likely to stay broken.

So will someone take it out atleast?

It's already a build option and disabled by default.  But if RT doesn't come back and fix it soon then we'll probably just rip the code out so that we don't have to deal with it.

[MadProf]

Decided to have a play with source for this and managed to add a few more commands.

Code: [Select]

<RULE ID="VID_targeting" TOPLEVEL="ACTIVE">
<L PROPID="VID_targeting">
<P VAL="0">Target next</P>
<P VAL="1">Target previous</P>
<P VAL="2">Target hostile</P>
<P VAL="3">Target previous hostile</P>
<P VAL="4">Auto target</P>
<P VAL="5">Target Friendly</P>
<P VAL="6">Target previous friendly</P>
<P VAL="7">Target sight</P>
<P VAL="8">Targets attacker</P>
<P VAL="9">Target sender</P>
<P VAL="10">Stop targeting</P>
<P VAL="11">Target sight subsystem</P>
<P VAL="12">Target next subsystem</P>
<P VAL="13">Target previous subsystem</P>
<P VAL="14">Stop targeting subsystems</P>
<P VAL="88">Target next escort</P>
<P VAL="89">Target closest repair ship</P>
<P VAL="90">Target next uninspected</P>
<P VAL="91">Target previous uninspected</P>
<P VAL="92">Target newest</P>
<P VAL="93">Target next turret</P>
<P VAL="94">Target previous turrent</P>
<P VAL="95">Target next bomb</P>
<P VAL="96">Target previous bomb</P>
</L>
</RULE>

<RULE ID="VID_speed" TOPLEVEL="ACTIVE">
<L PROPID="VID_speed">
<P VAL="15">Match speed</P>
<P VAL="16">Auto match</P>
</L>
</RULE>

<RULE ID="VID_power" TOPLEVEL="ACTIVE">
<L PROPID="VID_power">
<P VAL="69">Increase weapon</P>
<P VAL="70">Decreas weapon</P>
<P VAL="71">Increase shield</P>
<P VAL="72">Decreas shield</P>
<P VAL="73">Increase engine</P>
<P VAL="74">Decrease engine</P>
<P VAL="75">Power balance</P>
<P VAL="105">Max engines</P>
<P VAL="103">Max shields</P>
<P VAL="101">Max weapons</P>
</L>
</RULE>
Compiled verson in from a cvs grab on 28 Oct, http://www.intelwatch.demon.co.uk/fs2open/fs2open_voicer.zip.

Not entirly sure if all the targeting works, but the power management is fine.

The modified files are here http://www.intelwatch.demon.co.uk/fs2open/modifiedfiles.zip

[MadProf]

Had a bit of playing with code for this.  Managed to remove the need to pause in most phrases, so you can say "Alpha 1 Destroy my target" rather than "Alpha 1" pause "Destroy my target".

The phrase file is now also load at runtime so if a phrase isn't the way you want it, it can be edited.
Hopefully it will also work for other than english language settings.|

http://www.intelwatch.demon.co.uk/fs2open/fs2open_voicer.zip (4.36Mb) - modified version of the 3.6.9 branch code - grabbed from cvs on the 6th Nov -
only contains standard exes and a copy of the phrases.xml to place in the data folder.

http://www.intelwatch.demon.co.uk/fs2open/modifiedfiles.zip (5K) is the modified version of the voicer.cpp file.

I've also attached a copy of the phrases.xml to this post. Enjoy.

I find using this better than extra programs mention previously, no pauses required in the phrases.



[attachment deleted by admin]

[Cobra]

Just exactly how accurate is this now? I mean, half the time when I use voice-recognition with Game Commander 2, I always seem to get a few hundred commands mixed up.

[MadProf]

Probably about the same sort of accuarcy initialy.  The Microsoft stuff can be trained up further from standard if required.

[Goober5000]

Cool. Shall I commit this to CVS?  (It would be in the unstable branch and wouldn't appear in 3.6.9, but it would be in future releases.)

[MadProf]

If you want to stick in there be my guest.  I find it handy, if others do as well thats even better.

[Cobra]

Probably about the same sort of accuarcy initialy.  The Microsoft stuff can be trained up further from standard if required.

So, without voice training, commands can still be mixed up. Got it.

[Goober5000]

K, committed.

[Kaine]

awesome. Wish it was in 3.6.9, but there's always the CVS builds 

[miskat]

MadProf: what version build is your build based off of?

[MadProf]

The version linked to is a modified 2.6.9 from a few weeks ago.

[Grizzly]

link down

edit: silly me, it was an outdated one.

[Trivial Psychic]

The version linked to is a modified 2.6.9 from a few weeks ago.

WOW!  Talk about your retro build!

[miskat]

Any chance that voice recognition (and MadProf's fixes and extensions) will ever hit the official 3.6.x branch?

And, before I make myself look the fool: a question.

What, exactly, is the difference between all the different branches in the code?  CVS, official 3.6.x, HEAD....  What is the difference bettween all three?

[Goober5000]

Any chance that voice recognition (and MadProf's fixes and extensions) will ever hit the official 3.6.x branch?

It should be in 3.6.9 final.  If it's not, let us know and we'll rebuild it.

And, before I make myself look the fool: a question.

What, exactly, is the difference between all the different branches in the code?  CVS, official 3.6.x, HEAD....  What is the difference bettween all three?

CVS is the program used to manage the code so that we can keep track of all the changes we make to it.

HEAD is the main version of the code, where all the changes (both features and bugfixes) go.

The 3.6.9 branch is equal to HEAD except that it has none of the features added since June 2006.  We created this branch so that we could focus on bugfixing while making sure not to introduce any new bugs.