Forum Discussion
[Hypothetical] Input Device API
I just had a thought... There seem to be two big issues with controllers for VR right now: 1. There are so damn many of them 2. Oculus have hinted very strongly that they will be releasing a con...
"nuB" wrote:
The market simply will not support multiple tracking solutions for every device out there, a standard tracking product that can be attached to anything seems much more likely to succeed.
In saying this, while I am aware OculusVR purchased the Carbon Design Group, I believe their current focus is primarily with the design of CV1 as they slowly narrow down the constraints within which it is being designed.
Well, that's kind of the whole reason for a hypothetical input API - it would mean that the market could support many different input devices, since there will be several tracking standards that any number of input devices could be used to fulfil. Of course, the current turmoil in device competition will die down (eg. Either the omni or the virtualiser will succeed, not both), but I think that VR input should work like mouse input - many manufacturers, several different standards (common mouse, trackpad, motion mouse, trackball, etc)
Obviously we would want a certain common 'minimum level' of 3d input - something like what the STEM system delivers with two controllers, and I expect t Oculus to be the company that delivers this common minimum level. But I don't think a single input setup is going to be sufficient for the entire VR market - there will always be room for improvement, and a subset of users willing to spend the money to capitalise on this improvement.