Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
The original Oculus Rift prototypes used a sensor that was readily available on the market, but ultimately we decided to develop our own sensor hardware to achieve an optimal experience. With the new Oculus VR sensor, we support sampling rates up to 1000hz, which minimizes the time between the player’s head movement and the game engine receiving the sensor data to roughly 2 milliseconds. The increased sampling rates also reduce orientation error by providing a denser dataset to integrate over, making the player’s real-world movements more in-sync with the game.
9-axis motion detect with low latency (1 ms), wireless communication
9-axis motion detect, with low latency (1 ms) wireless communication
The article mentions nothing of 1ms latency head tracking... it does mention the wireless communication latency being 1ms, however. This is a very important distinction as the latency of head tracking is what the Occulus Rift has appeared to have put the most effort into via their custom 3-way merged sensor chip.
Oh and I do love the saying "correlation is not causation" often said here, which is where crackpot anti-logic spills over into the
The actual saying goes "Correlation does not denote causation", which I hope you agree, makes more sense.
"I have come here to chew bubblegum and kick ass, and I'm all out of bubblegum" -- Roddy Piper
The quote from 'They Live'
but unless you've got 1,000+ friends it's not going to help plus you need a sparse range of ip addresses to run it on
This is where 4chan comes into the picture.
What do you think about intermediate variables that are not strictly necessary?
I'll often find myself coding some physics equations from specifications written on paper. Obviously, they are always written in math notations. What I end up doing, if not limited by cpu/ram, is to create a stack variable for each term in the equations. Basically, I'll try to make the code look as much like the paper specs as possible. The specs will ALWAYS change, and trying to figure out how the two relate some years later is a real pita. Also, I'll always preface everything with some comment like "The following is from foobar specs dated Jan 1st 2002" for the reverse reasons.
I'd be completely wrong if they are using infrared vision, or facial recognition, but the article didn't mention.