MocapForAll PC

Capture human motion with everyday webcams and AI in this Windows-based animation tool. Set up two or more cameras in a 2.5m x 2.5m room, and a mid-range PC handles real-time processing at 17 fps on devices like Surface Pro 7 or 30-60 fps with GTX 1080 Ti hardware. No specialized gear needed-turn smartphones into webcams if desired. Stream motion data live via VMT and VMC protocols to SteamVR trackers through Virtual Motion Tracker, or pipe it into Unreal Engine 4/5 and Unity for development. Save clips as BVH or FBX files for Blender workflows, share via memory buffers, or link to apps like VSeeFace and VirtualMotionCapture. Early access animation and modeling creators gain affordable mocap for games, videos, and custom programs.

--------
PLEASE TRY DEMO VERSION FIRST
Make sure the app works in your environment before purchase. The demo version has limited functionality only for data export.
--------

This is a Windows application that uses multiple webcams to capture human motion using AI.

No special equipment required

You can capture human motion if you have the followings:

• a middle range PC
  
• 2 or more webcams
  
• a room of about 2.5m x 2.5m

You can use regular webcams like the ones used in video conferences. You can also use apps that turns your smartphones or tablets into webcams.

Realtime with a middle range PC

For examples, it runs at

• around 17 fps on Surface Pro 7 which does not have a dedicated GPU
  
• 30 to 60 fps on GTX 1080 Ti

What you can do with MocapForAll

• You can output captured motion to the network(*1) via VMT protocol(*2) and VMC protocol(*3) in real time.
  
• You can save the captured motion to files in BVH format and FBX format.
  
• You can output captured motion to the shared memory in real time.

(*1) Both VMT protocol and VMC protocol use UDP/OpenSound Control.
(*2) "VMT protocol" here refers to the message format used in the communication of Virtual Motion Tracker. The official HP of Virtual Motion Tracker does not use the word "VMT protocol", but MocapForAll uses the word "VMT protocol" for convenience.
(*3) "VMC protocol" is a message format used for communication between applications such as VirtualMotionCapture. Note that VirtualMotionCapture itself is not required for other compatible apps to communicate with each other using VMC protocol.

These allow you to do the followings:

Use in SteamVR via Virtual Motion Tracker
Through Virtual Motion Tracker, the capture motion can be used as virtual trackers in applications running on SteamVR.

Use in Unreal Engine4, Unreal Engine5, Unity
You can send the captured motion to Unreal Engine4, Unreal Engine5, or Unity for game development or video production.

• Plugins for linking data directly to UE4, UE5, or Unity are available from the online manual.
  
• As described in Use in other apps via VMC protocol, it is also possible to link by EVMC4U and VMC4UE using VMC Protocol.
  
• A Unity sample to read data from the shared memory written by MocapForAll is available from the online manual.

Use in other apps via VMC protocol
You can send the captured motion to various applications via the VMC protocol. The following are confirmed to work:

• Sending bones and facial expression morphs to Unity using EVMC4U
  
• Sending bones and facial expression morphs to Unreal Engine using VMC4UE
  
• Sending bones to Blender using VMC4B
  
• Sending bones to VSeeFace, and receiving facial expression morphs from VSeeFace
  
• Sending tracker to VirtualMotionCapture

Save animations to files
You can save the captured motion as BVH files and FBX files. It can be used with Blender etc.

Create programs to receive data
As the output specifications are open to public (except for FBX), you can even create your own programs to receive data from MocapForAll.