Motion Capture Or Animation For Games?

Thanks to TotalGames.net for their article discussing whether videogames should use traditional animation or motion capture to capture the movements of in-game characters. The piece points out: "One of the major problems with motion capture is the way that moves can sometimes appear disjointed and separated, as a character goes from one set of moves to another", but an advocate for motion capture comments that the process is "..a lot faster, as long as you can retain the subtleties from the point of motion capture to the raw data to the point where it reaches the engine." Can you tell the difference?

Comments

Motion capture

[recursiv]

Hand animation never seems to capture the feeling of "weightiness" properly. The models just jerk around as if they had no mass or center of gravity. With motion capture, the center of gravity is always apparent, and the model doesn't seem like a hollow marrionette.

Re:Motion capture

[neostorm]

If the animator is any good, the sense of gravity and weight is much better in models animated by hand, rather than motion capture.
Motion capture will always look more realistic, but so far there is a severe lack of animation skills in the industry. Mark of Kri and Jak and Daxter (both for PS2) are the only games I can think of off the top of my head that have well done character animation by hand.

In the end it comes down the type of game you're creating. You would never give a colorfully animated character a motion captured animation set, and giving realistic people exaggerated animations would give the game an entirely different tone.

Re:Motion capture

[NanoGator]

"Hand animation never seems to capture the feeling of "weightiness" properly. The models just jerk around as if they had no mass or center of gravity. With motion capture, the center of gravity is always apparent, and the model doesn't seem like a hollow marrionette. "

Well you've been a bit vague here. Possible reasons could be:

- Animators just getting started
- Technical limitations such as limited RAM. (Very possible.)
- Too little time.
- Motions could have been intentionally simple because when you move the mouse, the character moves according to some equation. Ever notice that when you rotate a character in Quake, his feet just rotate like he's on a pedestal?
- Intentional design. This may sound funny but maybe they didn't want the character bobbing around if you're trying to snipe it.
- Bad implementation. Animation is very complex. Getting from the artist to the programer can be nasty, especially when unexpected nuances appear.
- It wasn't an animator at all, somebody just trying to make the model move.

I could keep going but without a game in particular, I cannot give you an answer why you feel that way. I do think you're unfairly generalizing, though.

Animation v motion capture

[Xerxes of Zealot]

It depends on the game, am I right?

I dont want to play Mario and watch some actor whos been digitally captured, I wanna see some goddamn animation.

Likewise, I don't want to play Manhunt and see animation, then I want motion capture...

Animator's retort

[MobyDisk]

This guy is the animation advocate. His arguments are less than impressive:

...computer processing...takes out the creative flair that brings a character to life, thus making characters maybe more lifelike but somewhat lacking in life.

Well, that clarifies it. More lifelike, but lacking in life.

Obviously, animating traditionally takes longer than motion capture but you do have to spend a lot of time processing the data...So in a lot of cases a skilled animator...will achieve the same if not better results in not much more time than if the moves were motion captured. Motion capture is probably quicker....

So it takes longer, but in some cases it maybe traditionally isn't longer, but it's probably not quicker. Other great quotes:

Motion capture cannot always capture the sheer fluidity that many athletes possess and as a result this supposed realism can sometimes undermine all the motion capture artists' hard work.

Actually, that is the entire point of motion capture: It captues the fluidity of the actor exactly.

Re:Animator's retort

[SuiteSisterMary]

Depends on what you're doing, actually.

With Rainbox Six, for example, they took a man, punched him *really hard* in various spots with a pole, and recorded him falling down. That simulates being shot.

The problem with this, or course, you see in games like Splinter Cell; Sam's running, or jumping, or rolling, or shooting. But he can't really run into a jump, miss, land, roll into a shooting stance and start peeling off rounds.

But nowadays, with tons of processor, and a good physics model, it can be just as good to build your models properly, and let the engine figure it out. Terra Nova: Strike Force Centauri, Die By The Sword (I believe) and Oni, for example, played with this early on; Unreal Tournement 2003 seems to be the current champ.

Myself, for video games, I'd avocate using mocap to more accurately build your models and tweak your physics engine, then let the engine actually do things. When my model's running up a hill, I want to see him leaning forward to place his center of gravity. When he gets shot, I want to see him fall back, then down, then start rolling down the hill. When he's lying on the ground, I want to see his arm tracking where I'm aiming; I want to see him use his other arm to lift himself up off the ground.

This is not an absolute

[NanoGator]

If you can tell the difference either way, then the method was not implemented properly. There is no "is one better than the other?" there's only "which is best for the job."

Consider this: If you want to use mocap, but it causes wiggly meshes, then you have an implementation problem. Do you write the code or adjust the model/actor to solve it, or do you use the video as reference and manually keyframe it? Do you even care? Will the gamer care? Is it worth the money?

I realize this isn't exactly a either/or type of discussion, but it will quickly turn into one. One guy will have seen bad mocap, another will have seen bad keyframing. Done right, either technique will be extremely convincing. It's fun to discuss, but let's keep this out of the realm of absolutism.

State of the Art combines the best of both

[cying]

I strongly urge anyone who wishes to learn more about current research in combining motion capture with animation (similar to image-based rendering techniques applied to the motion domain) to look at these links, one from this year's SIGGRAPH, and a link to several other papers on the topic. SIGGRAPH 2002 had a special track on this (and the bibliography is cited as well).

• Stanford Movement Publications (2002 and before) - especially Kathy Pullen's paper
  
• Motion Synthesis from Annotation
  
• SIGGRAPH 2002 Publications
  

How about a combination of both?

[cloudless.net]

Who says motion capture has to be disjointed and separated? If you insert appropriate animations between different captured actions, the result could look very smooth. Just because many games have crappy motion capture doesn't mean the technology is flawed, we are just waiting for someone to do a better job.

Uh, both?

[GoRK]

No matter which technique you choose, there's going to be some degree of animation involved. To make it look right, most often a hybrid approach can yield the best results. Motion capture is fine and good, but what about when you are trying to model the movement of a 50-ton 20-foot tall rock monster or something? It can't be done accurately with motion capture, but you can use motion capture along with traditional animation techniques to create realistic looking physical movement. Or take gun recoil-- motion capute is probably going to produce something very realistic, but using that data verbatim in a game engine will likely result in poor playability. Animation fills in the gaps.

I don't really see what the argument is about here. There is plenty of work for both the motion capture proponents and the animation proponents!

motion blending

[zaad]

There's actually been quite a bit of research to do motion blending so that the transition between states are not noticeably unnatural.

So the real answer is, it's not a limitation of mocap, but current application of the technology.