Software Compatibility

Motive

OptiTrack's unified software platform. Tailored to meet the needs of the world’s most ambitious production studios and research facilities, Motive combines the best features from our past software offerings with a host of new ones designed to deliver simpler setup, larger volumes, and cleaner data. Learn more

Six Rigid Body Skeleton Improved. Simplified the number of steps necessary to set up the rigid body based skeleton from to just a handful. Made a variety of improvements to the skeleton solve to achieve more realistic tracking. Added some variations to the base skeleton model including an upper body only model (with four rigid bodies).

New UI. The process continues towards a whole new user interface by adding two new panes that help to consolidate similar functionality from throughout Motive.

Devices Pane - Displays all devices in one location. It also now allows users to create selection sets of devices, use a more compact device list view, show/hide columns of device properties, and sort the view based on particular properties. All devices have been converted to work with the properties pane. This makes changing settings for a group of cameras much easier, and it also helps persist camera and device settings in Motive.

New Finger Markersets.Must be used with Active Markers. We added several skeleton markersets that allow for individual finger tracking. These skeletons include both a left and right-hand model, a full skeleton model that uses the baseline skeleton, and a rigid body based skeleton with finger tracking.

Improved Profiles. A variety of improvements were made to profiles. The file extension has been changed to (.motive) and that extension has been associated with Motive. You are now allowed to export a subset of the profile. This means that you can easily create profiles that only contain assets, system properties, capture sessions, or hotkeys. You may also reset a subset of Motive settings.

Updated the file icons for the installer file, (.tak), (.cal), and (.motive) files to be more easily identifiable.

Modified the 3D "Live/Edit" and "Active + Passive" indications in the 3D viewport to act as a toggle button to switch between different states.

Modified the "Auto Select" mode in the tracking algorithm setting for active marker rigid bodies to dynamically switch between marker based and ray based depending on the tracking situation to improve tracking quality and performance.

Color Cameras. A variety of improvements were made to color camera integration with Motive.

Improved the video export dialog by adding more options for reducing the frame rate of the exported video, adding an option to the video exporter to overlay timecode data, and renaming some the video export options to help clarify what the options do.

Improved the performance and visualization of color cameras in the 2D view by automatically rendering color video data at a resolution that depends on what distance you are viewing it and automatically changing the spacing of cameras in the 2D view based on their orientation to avoid cameras from overlapping.

The color cameras without a filter switcher are now hidden in the 3D view by default. A "show all color cameras" option was added to the application settings for users that still want to see color cameras that cannot be calibrated into the system.

Camera Panel: Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras: The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent "Dropped Frame" message from the health system.

Cameras: Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Cameras: USB camera systems running on USB 3.0 must not use more than a total of 2 USB extension cables.

Camera Panel: Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras: The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent "Dropped Frame" message from the health system.

Cameras: Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Cameras: USB camera systems running on USB 3.0 must not use more than a total of 2 USB extension cables.

New UI: Motive has started the process towards a whole new user interface. This not only includes nicer looking panes, but also more functional and well thought out controls. This release includes the following new and redesigned interfaces in Motive:

Data Management Pane

Assets Pane

Markersets Pane

Rigid Body Pane

Properties Pane

Streaming Pane

Control Bar Pane

Timeline Pane

Graphs Pane

Trackables Pane

Measurement Pane

About Motive Popup

Splash Screen

Continuous Calibration: One of the biggest new features included this release is the Continuous Calibration. This feature allows you to maintain your volume calibrated by just regularly using your volume. All it requires is there to be moving markers throughout a majority of your volume over some reasonable amount of time for enough samples to be collected (limited to certain types of volumes).

Active Marker Tracking: Another big feature added in this release of Motive is the ability to track actively labeled markers. This uniquely identifies LED markers allowing non-unique rigid bodies with unique active labels to be tracked like regular rigid bodies. This is especially useful when trying to track lots of the same or similar object.

Rigid Body Refine: We now allow rigid bodies to be refined. This means if you bump a marker you can recalculate the rigid body to make it fit better to its associated markers. This is particularly helpful when using rigid bodies for measurement or defining a new rigid body from a template.

Probe Tracking: We are including the initial tools to create probes in Motive. This will allow you to set the pivot point of a rigid body to a precisely calculated location by rotating the rigid body around the probe tip. Once a probe has been created, the pivot location can be used to create virtual markers in your scene.

Persistent Settings: We completely remade our property system. Basically, starting from this release, Motive will persist all of the software settings between each use. Part of this also includes the change to watching folders on your file system instead of keeps a list of files that are loaded; this rewards and encourages more proper file system management. The Motive project file is also being replaced by the profile file which are XML collections of properties.

HMD Calibration: We added a new tool that places the pivot point of a rigid body in the same location as the pivot for an Oculus HMD.

AMTI Genlock Support: Added support for Genlock synchronization with AMTI force plates. This allows AMTI force plates to keep their synchronization with Motive over long recordings with no frame drift.

System Latency: Added new latency metrics to Motive and NatNet including the system latency which measures the time it takes for data to make it through Motive. See the wiki for more information about how these new metrics work.

The graphs pane in Motive now allows the rigid body pivot position/orientation to be graphed in Live and Edit mode.

Motive now has the ability to add custom marker colors and sticks to marker sets. This helps with labeling when tracking complex objects that can't use rigid bodies.

Created a new skeleton adding finger tracking to the baseline 50 skeleton.

Added the ability to toggle between hotkey profiles in the hotkey managers.

Added a visual in the 3D pane for showing the current primary selection.

Added the ability to change RB Pivot Point size.

Added the ability to adjust the opacity of skeletons and geometry attached to rigid bodies.

Added the ability to change the selection color in the 3D viewport.

Added the ability to update rigid body marker location in the Motive API.

Gizmo Tool: The move/rotate/scale tool has been expanded to work with rigid bodies and markers. This also makes customizing rigid bodies much quicker and easier by allowing the pivot point to snap to locations determined by markers in the scene. This also allows skeletons and rigid bodies to be edited during the Live mode.

Batch Exporting: Exporting data for a group of takes in Motive now only takes one export dialog now instead of one for each take.

Hotkeys: A large number of available hotkeys have been added to Motive. Some examples include the ability to switch between object and video modes for cameras, one click cubic or pattern fill, select/move/rotate/scale hotkeys, view tracked/untracked rays, etc… For a list of default hotkeys, see: [Link].

Ability to Graph Subsamples: The graphs pane now draws subsamples for force plates and NI-DAQ devices running at higher frequencies.

Tracking Bar Issue: Improved how Motive handles the situation with small camera count (2-3) systems where two, or more, markers are positioned in the same plane. Now it has a more deterministic way of figuring out proper locations of the reconstructions among multiple ray intersections.

New Mask Tools: Improved the masking tools in the 2D pane by adding better mask eraser tools and icons that are more understandable.

Designed and implemented an alternate visualization of rigid bodies that have solved data (previously known as JT data).

Follow selected now has a memory of what was selected when you started following selected.

Camera Panel: Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras: The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent "Dropped Frame" message from the health system.

Cameras: Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Cameras: USB camera systems running on USB 3.0 must not use more than a total of 2 USB extension cables.

Active LED marker labeling is now fully supported in Motive. With the proper hardware, this allows you to assign a unique ID to our infrared LEDs allowing non-unique rigid bodies and improved tracking capabilities.

Project files and rigid bodies from this version of Motive will not be compatible with earlier versions of Motive 1.10.x.

Camera Panel:Force plate data will only be recorded when 3D recording is enabled.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Cameras:USB camera systems running on USB 3.0 must not use more than a total of 2 USB extension cables.

Project files and rigid bodies from this version of Motive will not be compatible with earlier versions of Motive 1.10.x.

Camera Panel:Force plate data will only be recorded when 3D recording is enabled.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Cameras:USB camera systems running on USB 3.0 must not use more than a total of 2 USB extension cables.

Camera Panel:Force plate data will only be recorded when 3D recording is enabled.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Cameras:USB camera systems running on USB 3.0 must not use more than a total of 2 USB extension cables.

Camera Panel:Force plate data will only be recorded when 3D recording is enabled.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Cameras:USB camera systems running on USB 3.0 must not use more than a total of 2 USB extension cables.

Separated reconstruction and auto-labeling processes. This improves labeling workflows by allowing the auto-labeler to be run multiple times on the same take file.

Documentation for Motive has significantly improved over the last few months. Check out http://wiki.optitrack.com/

System latency has been improved for large volumes as well as with a large number of rigid bodies. Point cloud and rigid body solves now handle not having history data better. New rigid body solver optimizations implemented that
increase solver performance.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly.

Camera Panel:Force plate data will only be recorded when 3D recording is enabled.

Cameras:The frame rates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 frame rate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly.

Cameras:The frame rates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 frame rate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Added the ability to export default marker name template (XML) using the skeleton export dialog. This generates templates that can be used with the skeleton pane to allow users to apply custom names to skeleton markers.

Skeletons may now be created using A-pose palms forward and A-pose palms down poses.

Camera Panel:Force plate data will only be recorded when 3D recording is enabled.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly.

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly.

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly.

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly.

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using frame rates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Fix for FBX Binary exporter producing nothing when Rigid Bodies are on and Skeletons are off.

Fix for inconsistencies when reconstructing and auto-labeling selected regions.

Fix for a crash while filling gaps on markers that have no data.

Fix for an occasional crash when trying to "Remove from Project".

Fix for Application & Display Settings corruption that can happen when running a previous version of Motive.

Fix for a crash when clicking Capture Volume in Perspective View.

Fix for OptiTrack USB Driver failing to correctly install.

Fix for textures only displaying while a rigid body is selected.

Fix for UI reporting an incorrect IP in use when streaming data.

Fix for specular highlight making it difficult to see some reconstructions while editing data.

All tracked or untracked rays are now shown in the 3D views, rather than a subset of them.

Fix for streaming dropping a frame in a variety of circumstances.

Fix for a crash when setting the ground plane.

Fix for occasional frame skipping during 2D playback for some takes.

Fix for an occasional crash when deleting a take from disk.

Fix for a crash when exporting FBX ASCII.

Fix for Active Marker Labeling not properly labeling 3D markers.

Fix for the CameraLibrary occasionally failing to initialize a Prime Series camera or eSync2 after a bitstream update.

Fix for the Project Pane property grid not refreshing correctly when toggling selection between the asset definition in the top of the Project Pane and the asset instance in a take, underneath a given take.

Fix for labels not clearing when re-running reconstruction and auto-labeling then manipulating a skeleton or rigid body.

Fix for recording large take files (>5 GB) creating take files that cannot be read back into Motive.

Fix for inconsistent timecode usage across C3D and FBX exporters.

Some icons in the Project Pane were cleaned up.

Fix for, when clicking "a" in the Timeline Pane, the window did not properly reset.

Fix for auto-loaded (at startup) calibration not including all camera and reconstruction properties.

Fix for the Show/Hide Markers button saying it's on when it's not.

Fix for an empty 'Source' drop down in 3D Glasses panel when an OptiHub is connected.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:The fTimestamp value in NatNet packets may be incorrect if the camera system is operating under external synchronization.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:The fTimestamp value in NatNet packets may be incorrect if the camera system is operating under external synchronization.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:The fTimestamp value in NatNet packets may be incorrect if the camera system is operating under external synchronization.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:The fTimestamp value in NatNet packets may be incorrect if the camera system is operating under external synchronization.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera Panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent
"Dropped Frame" message from the health system.

Cameras:The fTimestamp value in NatNet packets may be incorrect if the camera system is operating under external synchronization.

Cameras:Having cameras in the Reference group running at a faster frame rate than those in the Tracking group is not supported.

Camera panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent "Dropped
Frame" message from the health system.

Cameras:The fTimestamp value in NatNet packets may be incorrect if the camera system is operating under external synchronization.

Camera panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent "Dropped
Frame" message from the health system.

New calibration engine that provides much faster and more accurate camera calibrations. Calibrations will typically take a tenth of the time required previously, can calibrate hundreds of cameras together, and yield much
better marker reconstruction quality.

Motive Batch Processor has been added, which is a specialized application for performing processing on any number of Take files. See documentation

NMotive scripting framework and .NET assembly. This is at the heart of the Motive Batch Processor, and allows application developers to interact with core Motive functionality through C# or Python scripts that can be run
independently from the Motive application.

New on-board camera marker segmentation and circularity filtering that better separates and classifies objects in the camera's view.

New take file format that utilizes data streaming, allowing very long take recordings limited only by available hard drive space. Take files load and keep only what is needed in memory, so even very large take files can be edited
smoothly.

The eSync now supports several new trigger modes on its analog inputs which are configurable in Motive.

Reconstruction settings can be saved independently and easily managed through the Reconstruction pane.

Calibration visualizations have been added to both the Prime Series status rings and Motive, making it much easier to see how many samples have been collected for a camera while wanding in a capture volume.

The Calibration pane has been completely reorganized and automated. The display of information has been revised to make it more clear and useful.

CSV exporter will now filter what it exports based on what is enabled in the scene.

Asset management in the UI has been simplified and made more clear. Assets can be added to or removed from takes via drag and drop or context menu in one step.

Support for the industry-standard "Helen Hayes" marker set has been added.

C3D files now transmit timecode information to a wide range of target packages.

Camera panel:Raw grayscale imagery recorded with FLEX:V100 cameras may not play back correctly

Cameras:The framerates for different sync groups need to be either 2:1 or 4:1 (e.g. 60 fps & 120 fps). Using framerates that do not use those ratios, or using 4:1 framerate ratios may result in a persistent "Dropped
Frame" message from the health system.

Direct depacketization clients:Motive 1.7 includes changes to the bitstream syntax from Motive 1.6. As a result, client applications that decode Motive UDP packets should be updated. NatNet 2.7 SDK direct
depacketization sample app (PacketClient.cpp) for a complete example of decoding the current bitstream syntax. Client apps using the standard NatNet SDK are unaffected.

Fix for issue when playing back trajectorized data. If a rigid body became untracked it would pop to a stale solution from live mode.

Fix for issue where rigid body solutions were streamed before they were calculated. This caused additional latency and a potential race condition that may have resulted in skipped frames or duplicate frames.

Fix for when deleting a rigid body could delete the wrong one.

Fix to correct LLDP/PoE+ detection on Cisco switches.

Fix for camera and camera group properties reverting to defaults when Reconstruction properties were edited.

Added ability to select 'multi-threaded' or 'single thread' camera calibration to help work-around a likely concurrency issue experienced by some users.