Kinect SDK 2.0 的功能明显少于 1.8？
Kinect SDK 2.0 has significantly less functionality than 1.8?
我想念以前的 SDK-s 中存在的几个功能。
例如：
//Getting reference to sensor(s)
//Old (1.8)
sensor = KinectSensor.KinectSensors[0];
//New (2.0)
sensor = KinectSensor.GetDefault();
//
//the latter one does not support multiple sensors?
还错过了使用多个传感器跟踪骨骼的选项：
https://msdn.microsoft.com/en-us/library/dn188677.aspx
这个也少了吗？
随着新传感器的出现，硬件要求增加，使得多个传感器变得更加困难，因为 Carmine Sirignano reported。
Only one Kinect for Windows v2 sensor is supported. It is both a runtime and hardware issue of the system due to available USB3 bandwidth could only support one sensor. You would need a system with multiple USB3 host controllers in addition to those host controls on separate PCI Express 2.0 buses at a minimum.
Wyck 同样继续 link:
The Kinect uses a lot (more than half) of the available bus bandwidth to operate normally. So even though you could physically connect two or more sensors, there is no feasible way to have them both sustain enough of a data rate for them to operate normally using the existing hardware.
由于硬件限制，运行时似乎只能在单个设备上运行，因此 API 已更改以反映这一点。
我想念以前的 SDK-s 中存在的几个功能。
例如：
//Getting reference to sensor(s)
//Old (1.8)
sensor = KinectSensor.KinectSensors[0];
//New (2.0)
sensor = KinectSensor.GetDefault();
//
//the latter one does not support multiple sensors?
还错过了使用多个传感器跟踪骨骼的选项： https://msdn.microsoft.com/en-us/library/dn188677.aspx 这个也少了吗？
随着新传感器的出现，硬件要求增加，使得多个传感器变得更加困难，因为 Carmine Sirignano reported。
Only one Kinect for Windows v2 sensor is supported. It is both a runtime and hardware issue of the system due to available USB3 bandwidth could only support one sensor. You would need a system with multiple USB3 host controllers in addition to those host controls on separate PCI Express 2.0 buses at a minimum.
Wyck 同样继续 link:
The Kinect uses a lot (more than half) of the available bus bandwidth to operate normally. So even though you could physically connect two or more sensors, there is no feasible way to have them both sustain enough of a data rate for them to operate normally using the existing hardware.
由于硬件限制，运行时似乎只能在单个设备上运行，因此 API 已更改以反映这一点。