Hi Ed,
When using the no-calibration-pose skeleton (which is the default) you
cannot save or load the calibration data in the intial stage (usually
up to 15 seconds). During that time you should get "not implemented"
error. There was a bug in earlier versions which returned okay by
mistake - but it failed internally. The correct behaviour is to return
the error.
About the start up time - this shouldn't happen.
Can you tell me which sensor you are using and which sample are you
trying to run?
Are things behaving differently when you run the sample as root?
Is it only NITE samples that are slow to load or non-nite samples such
as NiViewer as well?
Here is what I measured on my machine MacOSX 10.7 Lion machine (with a
Kinect sensor)
Only SensorKinect installed:
NiViewer - 8 seconds to startup.
UserTracker - 9 seconds to startup.
With both Sensor+SensorKinect installed:
NiViewer - 14 seconds to startup.
UserTracker - 23 seconds to startup.
Ziv.