Kinect v2跟踪速度：Unity插件与Windows SDK [英] Kinect v2 tracking speed: Unity plugin vs. Windows SDK

问题描述

在SDK浏览器中运行Body Basics示例，然后在Unity中运行Kinect View项目的精简版本（仅骨架）时，我发现跟踪速度存在显着差异。   Unity插件似乎会引入显着的
延迟时间。 

When running the Body Basics example in the SDK Browser and then running a stripped down version (skeleton only) of the Kinect View project in Unity, I've noticed a significant difference in tracking speed.  The Unity plugin seems to introduce significant lag time. 

有谁能告诉我开销可能来自哪里？  

Can anyone tell me where the overhead might be coming from?  

谢谢。

推荐答案

有一个偶然的事情可以解释你所看到的延迟。样本没有进行优化，因为它处理颜色/深度网格，删除可能会改善你的东西。另外，在COM
Api之间有一个Interop层，在某些情况下，必须转换数据，这会增加一些开销。提供的示例演示了如何将Kinect数据（sourceManager）导入Unity。您可能会发现只是接受代码并且执行一个简单的对象跟踪
的关节将以不同的方式执行。

There are a couple things that could account for the latency you are seeing. The sample is not optimized and since it is handling both color/depth mesh, removing that might improve things for you. Additionally, there is an Interop layer between the COM Api where the data has to be converted, in some cases, that will add a little bit of overhead. The sample is provided to demonstrate how to get Kinect data(sourceManager's) into Unity. You might find just taking the code and doing a simple object tracking for the joints will perform differently.

这篇关于Kinect v2跟踪速度：Unity插件与Windows SDK的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！