| drkohler said: 2. In the video, there was only one short sequence where the person and the avatar were in the same video pictures. The lag was clearly visible around 0.2-0.3s. This is no surprise as the Natal system has to compare several subsequent frames to determine direction of body movement. At 30Hz, the data acquisition time is already 66-99ms (2-3 frames). Add some overhead for data processing in Natal, sending data to the Box, and data processing in the Box, and you are over 100ms for pure hardware delay.
|
Also, I was wanting to get some hard numbers on the flow. And correct me if I am wrong on anything.
Image capture = 33.33ms (30hz camera)
Any data processing in Natal? = ??ms
USB to XBox = ~20ms from what I have read on USB latency.
XBox Processing to get skeletel system = ~10ms (http://www.newscientist.com/article/mg20527426.800-microsofts-bodysensing-buttonbusting-controller.html?DCMP=OTC-rss&nsref=tech)
Any other game code latency = ??ms
Latency from Xbox to display = ??ms
Display latency = 0.02ms-0.08ms depending on display type.
There are a couple questionable steps. At minimum, the system has around ~63.33ms of latency(this does not include display latency, game code latency, etc). The article also mentions that the skeletel system can be generated from any single frame.
