Page 1 of 1

RigidBody is tracked doesn't work well in the API

Posted: Sun Jul 05, 2020 2:20 am
by issahar
Hi.
I'm using the Motive API 2.2.0. I create a RigidBody in the Motive application, and export the profile. Didn't change any default settings.
When I'm using this profile in the API, I get a high percentage of the time that the RigidBody is not tracked. When I open the Motive application, the rigid body is seen clearly and the UI shows the exact movements, but not in the API.
Why is it happening?
Is there a way to configure it so the API will work as well as the application?
Thank you,
Issahar

Re: RigidBody is tracked doesn't work well in the API

Posted: Tue Jul 07, 2020 10:59 am
by steven.andrews
Hello Issahar,

Thank you for reaching out to us regarding the API.
Rigid body tracking should be the same whether you are running the Motive UI or the API. The API uses all of the same algorithms, just without the interface.

After you export your profile, you may want to also export a calibration file. Both can be imported through the API to be sure you are using the same settings and calibration.

If importing the calibration does not seem to make a difference, please feel free to reach out to us directly.

Best,
Steven
--
Steven Andrews
OptiTrack | Senior Customer Support Engineer
help.naturalpoint.com
support@optitrack.com