Changes

Jump to: navigation, search

Constellation

18 bytes removed, 15:23, 17 December 2016
m
Text replacement - "external camera sensor" to "Oculus Sensor"
[[File:oculus rift cv1 tracking volume1.png|300px|thumb|[[Tracking volume]]: 100°H x 70°V (>18 feet range)<br>Room size: 15 feet by 15 feet]] [[File:oculus rift cv1 tracking volume2.png|300px|thumb|[[Tracking volume]]: 100°H x 70°V (>18 feet range)<br>Room size: 15 feet by 15 feet]]
{{see also|Oculus Rift CV1}}
The first iteration of the system will be released with [[Oculus Rift CV1]] in Q1 2015. The [[Rift]] will utilize an [[external camera sensorOculus Sensor]] that sits on top of a thin and malleable pole about a foot in length. The entire setup can be placed on a desk similar to a lamp. The sensor and its mount is black in color. It is small, sleek and looks like a small desk lamp.
IR LED markers are placed on the HMD and Oculus Touch controllers so they can be tracked by the sensor(s).
For Constellation, high-speed position tracking performance is down ENTIRELY to IMU performance. It wouldn't be possible at all without another absolute reference system (optical, magnetic or otherwise) but it's the IMU that's doing the grunt-work.
Constellation's [[external camera sensorOculus Sensor]] is genlocked; they capture a frame at the same point in time. That means all marker positions are known at the exact same time. As for Constellation having a 'smearing' issue: Commercial optical MCAP systems do not generally use active markers (though some do), but retroreflective markers and an illumination system adjacent to the camera lens. These relative dim markers are still easily discriminable in all but the harshest (e.g. outdoors in direct sunlight) conditions. If you're being clever with your blob tracking, you can even use the blob shape from the smear in order to provide an instantaneous velocity measurement, though it's generally just easier to drop the shutter speed and make your markers brighter.
==References==
15,794
edits

Navigation menu