slowmo said:
Nyleveia said:
My initial comment regarding ingame was done jokingly, most commands are disabled entirely (not even local users can use them), during games.
however the latter comment, which was the one you found fault with, was something a great deal of people had issue with.
Just because you and your friends didn't, doesnt meant it cant happen, that's like saying "rrod is a lie because i havent had it".
|
So the fact that the reason it happened is because those people affected didn't use the Kinect Tuner to setup their device properly is somehow a fault of the technology. I still fail to see how this is the fault of Kinect when it quite clearly states numerous times during the setup process that you must run the Kinect tuner if the circumstances of your setup change. It happened because people didn't follow the instructions, had they done so like my friends and I did then they wouldn't have had the issue. I don't see what your problem is with admitting you were wrong.
|
How am i wrong? I simply stated that people had issues with it, and provided proof of people having issues with it, as such i'm not wrong as im not claiming to have experienced it first hand, my 360 and kinect are currently 6000 miles away and probably staying 6000 miles away so i wont/cant check for myself.
Also, you're basing your view of if these claims are real or not on the assumption (yours, not mine) that these people only had problems because they failed to setup their devices correctly, that, as i said, is an assumption and unless you know *for a fact* that those users (including an editor for polygon) are inable to, or neglected to setup their devices correctly, then you can't really comment on it as if it IS a fact.
