and you best start with vvvv-sdk on getting everything running conveniently on your machine to build and debug your own (or one of the available) plugs. don’t hesitate to ask questions if you encounter problems along the way…
It seems like Microsoft decided to narrowed the range of the depth stream in the driver. They say it gets you better data (which is true).
As I still need the tracking data that is farther away than these 3.5 to 4m, I will use the OpenNi drivers. While slower, they provide a deeper depth range and are ‘open’, which means easier to ‘hack’.
Thank you for your help, I’ll keep you posted as this seems a problem that many Kinect Users on vvvv try to solve.