First, you'll want to follow the instructions below to set up the data streaming settings in Motive. Once this is configured, Motive will be broadcasting tracking data onto a designated network interface where client applications can receive them.
Open the Data Streaming Pane in Motive's Settings window and set the following settings:
To get started, drag the OptiTrack Optical plugin from the Motion Builder Asset Browser tab > Devices into the Viewer window. This will create a dropdown menu called I/O Devices in the Navigator tab. Click the + button next to I/O Devices and select OptiTrack Optical. This will populate the plugin's settings tab if it hasn't already auto-populated from the drag and drop step from earlier.
Once the above settings are input appropriately, you'll want to click the box next to Online. This indicate whether or not Motive is successfully streaming to MotionBuilder.
Configure Motive for Streaming Data
Be sure to configure any Firewall software first (either disable or permit MotionBuilder as an exception).
Create an OptiTrack Optical device
Connect Optical Device to Motive
Create a MarkerSet > Opticals Mapping
Begin streaming marker data
The OptiTrack Optical device can record streamed optical data to the current MotionBuilder take. Note that the looping feature in Motive must be disabled in order to record streamed data in MotionBuilder. The following step-by-step procedure can be used to record data:
The OptiTrack Optical device can be used to show live data or blend live data with a recorded take. To playback recorded optical data, you need to tell MotionBuilder to disable live streaming.
When the opticals are generated, their naming conventions will be determined depending on whether the Organize Assets option was enabled under the Optical Device properties.
The device will generate optical data with colon ( : ) separator (e.g. AssetName:MarkerName), and all of the optical data will be organized under their corresponding root nodes.
The device will generate optical data with an underscore ( _ ) (e.g. AssetName_MarkerName) and all of
the optical data will be listed under a same optical node
For auto-mapping imported FBX actors to optical data, the Organize Assets setting must be disabled and underscore separators must be used.
The following guide is provided as a simplified process for working specifically with Motive, but this is not the only way. For the latest information on setting up and configuring MotionBuilder Actors and Characters, please refer to the MotionBuilder documentation.
To animate characters in MotionBuilder, you need to create the following data flow (or “mapping”):
The Mocap Marker Data > MotionBuilder Actor step maps Motion Capture data (Markers) to the MotionBuilder Actor object.
The MotionBuilder Actor object is a skeleton solver that creates joint angles from Marker data.
The MotionBuilder “Actor” > Skeleton Data > MotionBuilder “Character” step is specific to MotionBuilder, and this pipeline
maps the MotionBuilder Actor skeleton onto your final character skeleton. This step requires a “rigged” character. Refer to the
MotionBuilder help for detailed information on this process.
There are 3 ways to create a Motive markerset > MobBu Actor mapping.
Autodesk has discontinued support for FBX Ascii import in MoBu 2018 and above
The Optitrack MotionBuilder plugin can generate a MoBU Actor for you automatically.
In order to workaround Autodesk's removal of support for FBX actor import, we recommend the following:
For more information on setting up and configuring MotionBuilder Actors and Characters, please refer to Autodesk's MotionBuilder documentation.
Unlabeled markers are not commonly needed in the MotionBuilder workflow, but if needed, they can get streamed through the
Optical Device plugin.
The Optical Device has a special property for Arena Expression ( viewable from the MotionBuilder Properties tab) that
must be checked when using with Arena Expression software: