nightsurge said:
Underlined is just plain wrong. They already said no matter what the game, it will use ~10-15% of the resources. The software and data used from Natal will always use about that amount. It doesn't matter if you are overlaying the skeleton with say a Gears of War character or if it is just an Avatar, the "lag" will be the same as all the processing related to Natal and it's data will always have that amount of dedicated resources to use. Also, if it really is faster than pressing a button, then why does it have less input lag than many games using controllers? Killzone 2 and Halo 3 both have worse input lag than Natal at this point. |
I think you missed the point of what I was saying, so I will use an example. Lets say that Halo Reach without natal uses 85-100% of the CPU (for physics, AI, Decompression etc) if you use 10-15% of that processing power for natal that means that the other processing will have to be done later causing the game (or the input) to lag. And as for the other comment about the Natal lag processing the image into game readable input takes time as illustrated by it using 10-15% of the CPU, a button press wouldn't even use 0.0001% of the CPU so Natal will be slower, the reason for the controller lag in games is because of the nature of wireless the frame rate of the game because of the way the lag is measured the game waiting for the last frame to be rendered before reacting to the input, any lag Natal adds will be ontop of the existing input lag.
@TheVoxelman on twitter