Quote:
Originally Posted by stoianm
 i had the sames problems but i chosed the most simplest solution - i play the game using my headphonephone  |
Lol ..
Quote:
Originally Posted by MiTon
Oh thanks for the correction! Was lazy used copy and paste.
Perhaps you should set your confidence level to 1.00, 10 may create a "buffer overflow" setting your confidence level to 0.10 or 0.00! 
I had the same issues with the speech recognition for SH4 a view times.
Think it was a problem with the soundcard drivers!
I would check that if you're having the problems with the headset too!
If they don't handle the channels properly...
A workaround for this might be, changing the orders to phrases that are more unique and don't mess with the readback of your crew.
Like "both engines stop" when your crews readback is "All stop"!
I'll keep an ear on it! |
Shhhh! Say that it was a typo problem, not that you were lazy.
I gave .1 a try to no avail.
As for soundcard drivers, I've had different ones, and recently changed my board, which uses different drivers, so that "might" not be an issue in this case. I say "might", because even with different drivers, you never know.
Your workaround is a good idea, and I'm really glad that you reminded me about it, because if I can't resolve the problem directly, going in this way is a good alternative. I think I'll start with "Both engines stop" or perhaps a shorter "Engines stop", then do many of the other commands.
In fact, I actually already implemented a bit of it since originally encountering this problem. For example, for "surface the boat", I removed that voice command and all other references to it, leaving only "take her up". Since that time, I haven't had a rogue surface order except for "Blow ballast!" which is maddening (I'm going to pull that out too).
I have to figure out what's causing time compression to go to maximum, because that's a problem too.
I went in to the game after reading your suggestion, and watched the responses. "All stop" is one of those commands that is repeated back exactly, whereas speeds are not. So, "ahead slow" comes back as "minimum speed" or something like that, hence, not causing a loop. I think this is what tipped me off originally, but frustration probably made me give up early on an overhaul at that time.
Hopefully skwasjer may have some insight into the original problem one day.
Cheers!