| JaggedSac said: It will apparently use 10-15% of 360 CPU and take 10ms to complete the calculations. Not too bad. But it is a noticeable hit. |
Yeah, saw that article myself.
For what I imagine the average Natal game will require that shouldn't matter, but it could limit their ability to mix Natal with a game designed to push the 360 to the max - for example, Halo 3 to me from an engine point of view felt like Halo 2.5. Not a criticism, more a function of MS wanting the game out pretty early in 360 lifecycle. Reach looks to me like the first Halo game built to really exploit 360, however with this change I now wonder whether they could mix Natal with Reach so easily if they want Reach to push the envelope on visuals as they seem to.
I think the move makes sense though. Natal's success won't be down to having it add some extra elements to major games using the normal controller, but attracting the so called 'casual' audience, and that shouldn't require games that use to much of the 360 CPU that the Natal downgrade matters.
So I think it makes sense as a move, and won't make much difference overall - for example, I doubt they'd drop it just to lower the price if they knew it would also have a major impact on the games underway for Natal.
Try to be reasonable... its easier than you think...
