C# NatNet precision and frame skip issues.
Posted: Thu Jun 12, 2014 1:23 am
I'm using the latest versions of Motive and NetNetSDK. I'm running Motive and the samples on the same machine. The C# examples seem to have only tenth of a second precision floats from the FrameOfMocapData object for both "fLatency" and "fTimestamp". Is this expected? The C examples are all reporting millisecond precision values correctly. I'd really like to use C# but I need millisecond precision. I'm pretty sure they aren't being truncated by accident anywhere in client code - I'm getting them straight from the FrameOfMocapData on each FrameReadyEventHandler event.
I'm also having a really strange issue where many of the frames seem to be missing / skipped, but only when I'm not recording in motive. As my project requires live data, I don't really care about recording the data in Motive. However, if I don't record in Motive, I get large bursts of missing frames (m_FrameOfData.iFrame not always consecutive). I know Motive has the data because I can see in the rendering in motive that the tracking is flawless, but the missing frames cause problems in my end application. Is Motive doing something different with respect to streaming data when recording is on or off?
I'm also having a really strange issue where many of the frames seem to be missing / skipped, but only when I'm not recording in motive. As my project requires live data, I don't really care about recording the data in Motive. However, if I don't record in Motive, I get large bursts of missing frames (m_FrameOfData.iFrame not always consecutive). I know Motive has the data because I can see in the rendering in motive that the tracking is flawless, but the missing frames cause problems in my end application. Is Motive doing something different with respect to streaming data when recording is on or off?