forums.naturalpoint.com

I'll send $100 to whoever figures out how to get TT_CameraFrameBuffer() to deliver me grayscale data on 1 camera... We're using the Prime 41s, but it could be for any camera. I've been stalled on this for a long time.

I can't seem to get gaps working at all in 3.0.2. I select the rigidbody, it shows my tracks fine. I select "next" and "previous" gaps and the graphs "go away" with nothing in the windows. I go back and select the rigidbody again and get my graphs back. I press "fi...

Hm. I haven't seen this thread. I have been working on a few wrappers for the Motive/Camera SDK stuff. It might warrant a new thread. My stuff: 1. Creates a slightly smarter C++ API layer to do different housekeeping chores with the OT stuff. Like auto switching the stuff between the CameraSDK and t...

i modified the MotiveAPI sample "markers" to set camera 0 to "luma" mode, right after the call to TT_FlushCameraQueues(). I would have thought this would set the camera into luma mode, and it does say the call worked. But then, a subsequent call to TT_CameraFrameBuffer() returns ...

I'm calling TT_UpdateSingleFrame() and getting the bytes out of our prime 41 (?) with TT_CameraFrameBuffer( 0, 2048, 2048, 0, 8, pLumaBuffer ). it's returning false. pLumaBuffer is full of 0's. It's not clear how this method is supposed to be called. I'm going off MotiveApi.h. 1. What is ByteSpan, t...

The focus and fstop rings on the camera are manually set. Does the CameraSDK/Motive/etc not allow reading what these values are manually set to? Do you have an optical encoder in there? Should.

I'm linking to MotiveAPI.lib, in VS 2022, using the v143 compiler, x64 mode, and when i try to start debugging (with all the right dlls on the system in the right path), I see a dialog box that says "a debugger has been found running on your system. Please, unload it from memory and restart you...