Meta (formerly Facebook) announced a mixed reality headset at its Connect 2021 dev conference last week—code named Project Cambria. The company’s official teaser video is supposed to leave a little something to the imagination, however leaked 3D models have surfaced now that seems to show a convincing view of the headset.
Here’s that teaser in case you missed it:
Prior to its unveiling at Connect, a number of leaked videos revealing Project Cambria were posted on Twitter by user Bastian which was reportedly found in the ‘Seacliff’ firmware—ostensibly an internal name designation used by Meta.
In the video you can get a better look at the headset’s strap, which appears to be a bit of a mix between PSVR’s halo strap and the Quest 2 elite strap that both cradles the occipital bone and the forehead.
The reconstructed model also gives us a closer look at the headset’s Touch controllers, which have a noticeable inward slope in comparison to the flat button area in previous Touch designs. Like we’ve seen in previous leaks, the Touch controllers appear to house their own optical sensors, or depth sensors of some sort.
There’s even the model of the charging cradle, which we also saw in the previous how-to promo.
Notably included in the 3D model is the Oculus logo. Meta announced last week that the Oculus naming scheme will be phased out sometime in early 2022, as the Oculus Quest line becomes Meta Quest. This may imply that the Meta rebranding wasn’t known to the Oculus team at the time, or that the model itself was an earlier representation before the name change was internally discussed.
Speaking to Road to VR, Bastian reports the model in question is at least older than September 22nd, 2021, since that was the build time indicated in the Seacliff firmware.
Meta says Project Cambria will launch “next year,” however there’s still no pricing or more precise launch window. Check out the Connect announcement of Project Cambria to learn everything we know about the upcoming headset.
Update (12:20 PM ET): Bastian reached out to us to provide corrections to material errors made within the article. We’ve included all corrections above. Thank you, Bastian!