forums.naturalpoint.com

The errors suggest an out of date NatNetTypes.h file.

Reviewing the NatNet 2.6 distro - NatNetTypes.h appears correct with the included declarations. Possible your project is referencing a previous version?

Morgan

I would check this line in the sample:

% TODO : update the path to your NatNetML.DLL file here
dllPath = fullfile('c:','NatNetSDK2.5','lib','x64','NatNetML.dll');

and confirm the path you are loading the NatNetML.dll file is correct.

morgan

The MATLAB error suggests possibly a namespace collision (a duplicate figure with the same name?). Do you have other figures in your code, or other objects with the same name?

I would try creating a figure with the default parameters - the optional params in the example are not required.

Morgan

Several changes have occurred in the angle convention system between Tracking Tools/Arena and Motive 1.0, and again between Motive 1.0 and Motive 1.5, as we try to standardize and simplify the programmatic interface for working with and decoding quaternions. The latest version of Motive and NatNet (...

Yes - if you need marker data you can integrate the PacketClient.cpp code directly into your Linux CPP code. The PacketClient.cpp sample uses winsock so you'll want to replace with unix sockets: replace #include <winsock2.h> #include <ws2tcpip.h> with: #include <sys/socket.h> Our use of winsock is l...

The Timecode parameter in interpreted differently when streaming Live or from File Playback (Edit). In Live mode, the Timecode parameter is only valid when SMPTE timecode is present in your Mocap hardware setup, typically when using the eSync and a timecode generator. When present, the Timecode para...

RE RigidBody data, yes the order of the markers within the rigid body remains consistent. The IDS are indexes into the RigidBody. The RigidBody ID itself should be unique. RE MarkerSet data, yes this is more of a legacy data type we keep to support older NatNet clients. Should the tracking models li...

Hi Stefano,

Thank you for updating your post with the solution. We've updated our docs to reflect the compatibility issue, and are checking with the MATLAB folks to see what changed.

Here is our most common troubleshooting steps: If streaming locally: - Run with the *default* settings in Motive/Arena/TrackingTools and Winforms sample, with both client and server IP addresses set to local loopback (127.0.0.1) on the client, and 127.0.0.1 set in Motive. - Disable Windows firewall ...

Some ideas for troubleshooting: If streaming locally: - Run with the default settings in Motive and Winforms sample, with both client and server IP addresses set to local loopback (127.0.0.1) on the client, and 127.0.0.1 set in Motive. - Disable Windows firewall If streaming remotely - Disable Windo...