Bitching Betty (Expand Dialogue & Configure Warnings)
#21
Posted 26 May 2014 - 04:32 PM
So count me in if PGI gets their head out of their ******.
#22
Posted 26 May 2014 - 04:41 PM
Computer voices from MW2, 3, 4, and MWO closed beta (unreleased betty)
The current MWO actress is the same as MW2.
Other computer voice related vids.
Edited by Koniving, 26 May 2014 - 04:42 PM.
#23
Posted 26 May 2014 - 05:21 PM
Think Jarvis smart-assed tone
#24
Posted 26 May 2014 - 09:53 PM
There is a lot of useful info that gets overlooked in the middle of a fierce fight. The one I want most is a warning when you are under enemy ecm ("Why aren't my pugging team shooting this guy?!?! He's like, RIGHT HERE! Oh, *derp* he has ecm..."). An audible warning like "Low Signal" or "Sensors Compromised" would be useful. Also, +1 for a weapon door status update. If you are in thermal/night vision, the door indicator light becomes useless.
#25
Posted 28 May 2014 - 01:44 PM
#26
Posted 31 May 2014 - 10:25 AM
#27
Posted 31 May 2014 - 12:23 PM
Maverick01, on 12 August 2013 - 08:31 PM, said:
Enemy Mech Destroyed
Chain Fire Engaged
Group Fire Engaged
Mission Successful
Mission Failed
Weapon Door Open
Weapon Door Closed
Arm Lock Engaged
Arm Lock Disabled
Enemy Power-Up Detected
Internal Ammo Explosion Detected
Furthermore, players should be allowed to configure what audible warnings we get from Bitching Betty (checkbox list in the Options Menu). Thoughts/Opinions?
Yes so long as it's configurable. I'd also get rid of new mech targetted if not configurable because it seems so repetitive.
#28
Posted 03 June 2014 - 08:51 AM
Seriously, I would pay money for a Duncan Fisher voice pack in my 'Mech!
#29
Posted 04 June 2014 - 05:18 AM
i suggested the drop ship and the defend assult missions months ago
#30
Posted 05 June 2014 - 11:43 AM
#31
Posted 14 June 2014 - 04:43 AM
What I'd really like to see is them take out the absolutely useless jump jet warnings that only sometimes tell me that I'm at 25% when I'm actually at 0% and plummeting to the ground by the time she spits it out.
I want them to put in "Target destroyed" when a targeted contact gets destroyed. This would let me know if a contact that I have no LoS to is down or just around the corner from the team mate that I'm running to assist. "Spotter destroyed" may be either useful or too far in that situation, I don't know. General awareness of the battlefield helps to negate this situation, but a helper voice would let us focus on more important matters sometimes.
-Rabbit
#32
Posted 14 June 2014 - 04:53 AM
well at least the "oh, i´ll be dead in 2 seconds" moment would be funny for a while
Edited by Alex Warden, 14 June 2014 - 04:53 AM.
#33
Posted 18 June 2014 - 08:41 PM
-Scout target info incoming
-Weapon Jammed
-Warning! Targeted (I can see how this might get annoying)
-Enemy Detected
-Out of range
-Friendly base is being captured (Useful for Conquest
-Overheating
And a whole mess of lance/company leader voice commands (not Betty)
Also, I imagine it would be SUPER easy for them to make "Target Destroyed" by editing together parts of "[Weapon] Destroyed" and "Target Acquired" I just did it in like two seconds, here's hoping it makes it in. Would be amazing.
When this stuff gets integrated: sh*t's gunnna be gooooooood
EDIT: OH GOOD GOD THERE IS A FILE FOR "EJECT"
YES PLEASE
Edited by xeromynd, 18 June 2014 - 08:44 PM.
#34
Posted 25 June 2014 - 11:17 PM
#35
Posted 23 July 2014 - 02:26 PM
Upon UAV usage, After spotting(let's say...) three or more enemy Mechs from an individual Mech:
"Mech Power-up Detected"
ECM toggle:
"ECM Disruptor Engaged/Disengaged" -OR- "ECM Disruptor Engaged/ECM Counter Engaged"
I don't remember if ECM ever had it's own dialogue, but MASC did. So with ECM so common and important
in this game, ECM should have its own lines.
ECM disruption:
"ECM disrupted."
Full Ammo Depletion:
"Ammo Depleted"
Should be said very quickly.
Destroying an Enemy Mech:
"Target Destroyed"
Targeting another Enemy(in the past Hostiles and Allies):
"Targeting"
I believe this would be the most annoying line that could be present in MWO.
This should probably be optional then.
#36
Posted 03 August 2014 - 09:22 AM
#37
Posted 03 August 2014 - 05:25 PM
Edited by Flying Fox 333, 03 August 2014 - 05:26 PM.
#38
Posted 13 October 2014 - 06:43 AM
#39
Posted 24 November 2014 - 10:17 AM
#40
Posted 02 February 2015 - 07:29 PM
From PGI, when they originally did the sound recordings for 'Betty' they ran a second session to add content.
- Quite a bit of what was recorded has not been made available yet.
- Mostly due to future content not being ready or in the game yet.
So, there are (as the earlier post stated) lots of notices and warning that we haven't heard or seen used yet.
- At some point with all the commands/warnings the Pilot can suffer from 'information overload'.
- This would be where PGI would need to allow for on/off selections in Betty's comments, not everything she says is always needed by the Pilot. Some of this info will eventually be 'displayed', so adding a verbal comment would/may not be necessary.
We've all seen at some point that the comments made by Betty can be 'a little too late' by the time the Pilot gets the message.
- Detection range for anything attacking or effecting the 'Mech may need to be extended, just to give the sound bite time to 'spool up' and complete its dialogue. This doesn't need to change anything else in the 'Mechs sensors, all background code, specifically for the 'Betty bites'. (no pun intended, well maybe.)
- With the advent of Ts arriving, perhaps PGI may be able to streamline some of the in-game sound, matching events closer to there required warning event. (were all about to see how that will be working.)
Just some observations,
9erRed
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users