PrioVR delayed until "little later this year"

As with any new technology, if we waited until the suit was “perfect” we’d never ship a product at all. There will always be improvements to be made, and we’re only just brushing the surface with where we can take inertial motion tracking. That being said, we’ve set three benchmarks that we need to meet before we can say it’s ready to ship.

(1) Developer tools. This is first and foremost – solid developer tools, matured APIs, and seamless integration into Unity and Unreal engines. We know you don't have a lot of time to spend experimenting with integration into your game or VR experience, so we want to make sure you can have confidence in our APIs and that there’s a near-to-drop-in experience for integration into main engines. This means clear documentation, code examples, and plugins. We don’t need to have it all on day one but the platform must be solid.

(2) Mocap with Skeletal. We already have a full Mocap suite that works with our alpha suit, but we want to make sure it’s updated to use our new Skeletal API – so that as we make improvements they’re carried through to the Mocap Studio. This is our “generic” Mocap suite. We’re currently supporting export to BVH for MotionBuilder, but are looking into FBX, CSV, C3D and COLLADA (so let us know in our forums what formats are most important to you).

(3) Stable hardware. While we can continue to roll out updates over the air for firmware and software, hardware is another thing altogether. We have to make sure that the platform we send you has enough room to get us to the next stage and is one that you can rely on with your projects. At this stage, it has to be function over form.