“Gnhhh!”

“Whhhhaaaah!”

“Bah….ah….gahhhhhh…”

“Hmmmf!”

“Ehiehhh…”

“Mhaemm!”

These grunts, sighs, squeals and miscellaneous other vocalizations compose roughly 1/4 of the dialogues in the early hours of Final Fantasy XIII.

One one hand, they’re to be expected; Japan is known for its plethora of exclamations and onomatopoeiae. On the other — when translated literally — they make for a poor localization.

These sounds are often louder and longer than their English counterparts, or they simply have no equivalents. As such, they’re difficult to remove or replace and are usually left untouched. They’ve even become something of an accepted “quirk” among the more dedicated fans of Japanese media, but that doesn’t mean they couldn’t be handled in a friendlier fashion.

I think the localization team for FFXIII wanted to give Vanille a unique voice -- much like the Björk-esque Fran in FFXII -- but the voice actress' performance is a bit of a mess.

As things stand, vocalizations often come across as alien and awkward. They break the flow of conversation and the suspension of disbelief, and can leave a new audience feeling put off.

Sure, one can always argue for the purity and cultural authenticity of any given product, but that’s being a bit of a stick in the mud. Literal translations lack context and social nuances, and those fully familiar with them might as well experience the original versions. In order to make the products easily digestible by a different audience, though, some things need to change. FF XIII in particular is a title Square Enix wanted to be a global blockbuster, not just a Japanese game released to a niche audience outside of its home country, so it stands to reason that they’d want to iron out these kinks.

So how can this be done?

A couple of points:

• If possible, simply remove the exclamations altogether. The ones that could easily be cut are left in to keep things consistent and speed up the localization process, so getting rid of them shouldn’t be a big issue.
• Use local equivalents of the vocalizations if available. For example, make a character surprised by a hand on his shoulder utter a short “Huh?” instead of the original, “Mnhaaa?”
• Use actual words or sentences for sounds that have no local counterparts. A character crying out “Gwahhhhhhhhhhhh!” for three seconds after witnessing a car crash could easily be replaced with a quick “Oh my god!”
• Meld the exclamations into the speech itself. I’m not an expert, but I noticed many of the vocalizations were isolated within the dialogue, whereas in English they’d part of it, e.g., “Mmmm, I don’t know about thaaaaaaaat.”
• Finally, keep these points in mind when developing the game, and provide the team(s) with the tools necessary to port it. Automated lip-synching is already widely used, but I’m sure other functionality — or just the permission to alter the in-game cutscenes — would be appreciated.

Of course there are more issues to consider as well — perhaps toning down on the dramatic, clenched-fist poses with characters uttering such phrases as “I’ll do my best!” — but those are a whole other topic…

I’ve recently praised the use of states and derided their absence, but it’s not a one-way street.

To put it simply, states are great for abstractions. They fit unrealistic settings very well, and give us clear signs of what’s actually going on inside the game. They can also diminish the need for complex transitions while making the best use out of limited resources. A clear benefit of this approach is gameplay that can rely on instant, i.e., twitch, responses. For example, a character in Street Fighter II can go from doing a leg sweep to a backflip in a split second without looking too awkward.

Despite being a 3D game, Wind Waker -- like most Zelda titles -- made great use of state-based mechanics.

States are not directly tied to arcade titles, though, nor are they unfit for 3D games. The correlation here is between states and the lack of realism, not states and projection types. The further a game gets away from what we know of real life, the more explanation and experimentation it requires. Sure, Super Mario Bros. might be pretty intuitive, but you can’t really tell how fast Mario can run and jump until you try it out yourself (or see it happen). Conversely, when initially approaching Call of Duty 4, there are many preconceptions for how the characters should move and animate because of their depictions.

Of course CoD4 isn’t a life simulation, but it does aim for what “feels” right and consistently follows its own rules. As does SMB, actually — both titles have a real sense of verisimilitude. One’s just more abstract than the other, and as a result can get away with being much less realistic.

Which leads me to my main point: as the fidelity of games approaches real life, state-based mechanics increasingly detract from that illusion.

But first, let’s take a look at two drastically different titles: Snow Bros. 2 and Grand Theft Auto IV.

In Snow Bros. 2, the enemies have a few basic states. There’s walk, jump, covered in snow (1/4, 2/4, 3/4, or fully), and a couple more. The physics behind movements are very basic, while the transitions are instant. As soon as an enemy gets hit with a shot, its visual representation changes to an animation that shows it on its back struggling to get free.

Say what you will about Assassin's Creed, but the way it allowed Altair to interact with his environment spoiled the audience of third-person action games.

In GTA IV, all game objects respond to a wide variety of variables. The cars don’t have a simple moving/idle/dead state, and their visual representation is a reflection of their physical properties. The cars accelerate on a curve and dip with each turn, while a drunken character’s skeleton animates him as he hangs on to the door handle.

Trying to apply the state mechanics of Snow Bros. 2 to GTA IV would result in ludicrous situations that would detract from its sense of realism. In fact, making the world feel more organic was one of the major improvement of GTA IV over GTA III.

And this gradual raising-of-the-bar is to be expected in videogames in general. Dialogues were once just text, with the occasional frame or two of a “talking head.” These days they’re fully voiced and lipsynced, and character models even emote and use body language. However, many games that rely on a realistic presentation still insist on state-based mechanics. I think one of the more notable examples of this is the upcoming Final Fantasy XIII.

Here’s a video of its demo:

Various fans have praised this game’s detail and fidelity, providing glowing commentary on its rendering of hair and other such tidbits. Well, it is quite a long stretch from the deformed pixel art of the older titles, but it’s also a clear example of dissonance between visuals and mechanics. The player character’s movement has an instant acceleration, and, when she gets stuck on a wall, she performs that old running-man animation. The topography of the obstacle at the 0:52 mark is also quite complex, but its collidable surface is represented by a giant, invisible block. Furthermore, traversing this obstacle is done with a single button press that initiates an instant and perfect jump. This movement is entirely scripted, and it looks quite awkward and unreal when contrasted with the scope of the environment and the proportions of the character.

Now I’m not sure if this is technically an example of the uncanny. After all, that phenomenon describes a feeling of unease brought on by an almost-but-not-quite-real object, and I don’t think anyone would describe the above example as being entirely realistic. Still, the uncanny concept deals with the contradictions between what’s expected and what’s witnessed, and I think high-fidelity games that rely on state-driven mechanics embody that point quite well.