forums.naturalpoint.com

In general, we try to provide the most comprehensive data to client applications. For marker data, this means providing both the observed marker position and the model-solved position. I'll try to (hopefully) clarify: Observed Marker Location - This is the triangulated location of the marker as &quo...

The frame of mocap data structure exposed by the NatNet managed library (NatNetML) used by MATLAB contains a frame ID and a timestamp. The timestamp is a float, in seconds, representing the time the mocap data arrived at the host from the camera. I would use this for measuring the time delta between...

This is correct - marker size information is currently only available for labeled markers. Possibly a solution here would be to create a rigid body for your markers in order obtain label and size information. RigidBodies have a deflection parameter that allow them to be quite deformable before losin...

Thanks for the find. We'll work on getting some improved safeguards into the next release.

Morgan

New to NatNet SDK v2.6 is the TrackingValid flag for rigid bodies. See the SampleClient for an example of how to use, but basically: // params // 0x01 : bool, rigid body was successfully tracked in this frame bool bTrackingValid = data->RigidBodies[i].params & 0x01; Morgan

[Client] Server returned NAT_UNRECOGNIZED_REQUEST Is OK and can be expected when the server doesn't recognize the request. We're you able to get streaming working from the data handler callback? If not I would first test using one of the pre-compiled samples that ship with the NatNet SDK (WinForms i...

You are correct - Timecode is not available in the NatNet Managed Library (NatNetML.dll) v2.6. We'll get this into the 2.7 release, which (don't quote me) should be available this month.

Morgan

We've confirmed unhandled exception occurs during Getdatadescriptions() call to client library is triggered when a RigidBody name on the server side (e.g. Motive) contains only a number (e.g. 1). We've scheduled a fix for this in the next release of the NatNet SDK (2.7). Thanks for the detailed trou...

We tested your SampleClient binary here and it appears to work correctly (no crashes, data descriptions and data stream correctly). Some notes: - Our test OS is Windows 7 x64 and 8.1 x64 - Motive 1.6b2 - Your SampleClient.exe is using the x86 NatNet dynamic library. We tested your exe using the 2.6 ...

Testing the NatNet SDK 2.6 SampleClient.cpp x86 debug using VS 2013 with project updated to target the VS 2013 platform toolset (V120), GetDataDescriptions() appears to work correctly. Since the NatNet SDK was build using VS 2010, you might try a VS 2013 project but target the VS 2010 platform tools...