Motion Capture Demo

esse quam videri
Revision as of 16:24, 14 August 2008 by Aoleksiuk (talk | contribs)
Jump to: navigation, search

++Overview

  • Motion Analysis hardware
  • optical motion capture
  • 10 Hawk cameras
  • EVarts 5.04 software

++Uses of Character Animation, pipeline overview

  • file formats
  • Autodesk MotionBuilder 7.5
  • marker sets
  • TGEA

++Motion Capture Production (EVarts 5.04)

  • Load a previous marker set (project (.prj) file)
    • Marker set will be visible in post-process tab
    • The number of markers will directly reflect the number of tracks in your track(.trc) file
    • this will translate to points on the skeleton rig
    • depending what your final destination for your Motion capture is, this may be dictate from the model being animated (if it is already created or not)
    • in either case, the data can be massaged later in the pipeline (better to have more)
  • Calibration L-seed - switch to calibration tab
    • Turn on the cameras, put the L-device on the floor, connect to cameras
    • "Run" the cameras for a couple seconds
  • Mask out
    • switch to 2d mode, for each camera mask out any extraneous areas using middle mouse button (wheel)
    • basically, youu should only see the four L dots from each camera angle. mask out anything else by click and dragging rectangles
    • for each camera, use tools ==> camera settings, to adjust the threshold to approximately 300
    • "run" the cameras for a couple seconds
    • review masking for each camera, making sure there are no extraneous red/black marks
    • for each camera, click on Preview calibrations, ok to overseite and "Collect and calibrate" button
  • wand calibration
    • (remove the l-seed)
    • run the cameras by hittin the run button

88 click on the ok to overwrite under the "calibration with wand" section floor, ROM

  • Data output, capture
  • EVarts 5.04 Post production

++Autodesk MotionBuilder 7.5

  • inputting TRC data
  • cleaning up TRC data
  • animation
  • Output formats