6 replies to this topic

[Ronin1051]

Betty's voice seems more than a little lacking. Hearing someone tell me "Target: (wait 3 seconds) Acquired" sounds like they're either asleep (in which case I DO NOT want them as a "co-pilot") or they are not very into it. In fact, why do you need someone to tell you in the first place that you ARE acquiring a target? A simple beep/sound does that just fine! Just have her confirm USEFUL things like "AMS: Activated", "ECM: Engaged[/Disengaged]", etc. And please keep the "verbage" the same, i.e., "Damage: Critical", "Target: Destroyed", "Heat Level: Critcal; Shut down imminent", etc. Just how you would expect a machine to talk: Noun first, action/adjective second. The pacing of the voice needs to be faster! I do not have time to hear how this "lady's" day was! It needs to be sharp, quick, and precise!

Some say MechWarrior 2's voice was the best...

I loved MechWarrior 4's though:

^Not much to it, but it did the trick.

Edited by Ronin1051, 12 December 2012 - 11:56 PM.

[JohnnyWayne]

It's called bitching betty, not bitchy.

[MrLiNcH]

Agreed... it should be sped up quite a bit... a little computer modulation to make it sound like a computer might separate it as well. Like the one mod someone posted on the Guides forum a while back but was taken down.

[Death Mallet]

I agree. . . less of a "measured pace" and more of quick, harsh, useful information.

[sycocys]

The voice doesn't kick in half the time for me so I just turned it off. No point having a voice for "incoming missiles" if it doesn't tell me, or waits until after I get pounded to chime in.

I do agree though it should be quick, concise notifications and not sound like you've got a hd audio setup installed in your war machine.

[Qarnage]

I feel that the voice is not kicking in as expected since the patch following implementation. Also causing sound glitching, cutting half short.

[Banditman]

You realize you can create your own voice paks, right?