Problem with Frame Callbacks.

[roman tunkel]

I noticed yesterday that there seem to be a bug with the Frame callback method associated with the _INPCameraEvent interface. I realized that if you use the INPCamera parameter of your implementation of the callback function the program crashes. Looking through the OptiTrackSample demo, I noticed that this parameter was not used in the callback function. I would appreciate it if someone can look into this.

void CCameraDlg::HandleFrameAvailable(INPCamera * pCamera)
{
1. No use of parameter pCamera
}

[roman tunkel]

Is there a way we could have access to the 1-bit frame/image buffer now or in future releases of the OptiTrack SDK?

We have developed our own tracking algorithm by capturing the image drawn on the application window.

Frame/image buffer access will certainly be convenient.