I don't particularly disagree with the price point argument but since you're here...
"high-quality AR mode" -- do you have public SDK documentation for this and does it have a mixed passthru VR / AR mode like the Quest 2? The quest actually is a bit underpowered for doing this properly imo so I can see a higher price point potentially being necessary to pack it with the right hardware.
Not that I'll ever build it but somewhere along the line some cordless headset is going to have great passthru and the ability to replace the windows in my house with the beach or a beautiful mountain vista.
Also just an observation -- x86 on your face makes me think it probably gets quite hot :)
No documentation yet, but I can give you an overview.
We have two wide-angle RGB cameras mechanically locked to the users' PD. The cameras itself are around 2k x 2k at 90 fps. For the standalone mode, the data is pushed over a PCIe gen 3x4 link so we can hit <12ms latency. Tethered is a bit more tricky as we can't count on the bandwidth being available, but we'll either compress it or do a reduced resolution.
The actual sensor is still TBD. I'd like to do this properly with a global shutter sensor (IMX547), but they're a bit too expensive. If we don't have the margin for it, something like a IMX715 is the fallback.
The compute pack will be on the back of your head, so a bit easier to cool and not as severely annoying. Also helps balance the headset.
"high-quality AR mode" -- do you have public SDK documentation for this and does it have a mixed passthru VR / AR mode like the Quest 2? The quest actually is a bit underpowered for doing this properly imo so I can see a higher price point potentially being necessary to pack it with the right hardware.
Not that I'll ever build it but somewhere along the line some cordless headset is going to have great passthru and the ability to replace the windows in my house with the beach or a beautiful mountain vista.
Also just an observation -- x86 on your face makes me think it probably gets quite hot :)