VR Motion Cancellation - Time to test!

A bit of an update from my original comments on the subject, based on owning the Rift and Vive, plus doing lots of public VR demos.

Price is now a significant factor following the Oculus price reduction, but it is not necessarily a determining one.

It makes sense to choose the Vive if your choice is driven by above average or large roomscale, robust tracking, not wanting USB cables snaking everywhere, you plan early adoption of eye tracking, wireless and tracked peripherals, are considering motion simulation and want native motion cancellation, wear glasses or need greater adjustability for eye issues, or if you have a philosophical concern about Facebook and user data.

Choose Oculus if your choice is driven by lower price, included audio, refined design, slightly larger sweet spot and slightly less screen door effect and you want native freebie/exclusives, or if you never plan on using tracked controllers.

The Rift really benefits from a third sensor for roomscale but be aware it does not play nice with all USB ports or cables, plus other USB peripherals like wheels, pedals and HOTAS may complicate the USB bandwidth issues.

The Vive controllers are great at simulating things, such as guns and swords, while Touch is better at simulating hands. Personally I prefer the Vive haptics and Oculus positional audio, but their respective counterparts are fine and not a deal breaker.

The Vive wands can also be used in creative ways, such as a joystick, wheel or virtually any other input device: https://www.xsimulator.net/community/threads/use-vive-wands-as-a-joystick-or-wheel.10452/

With respect to tracking according to this data source less than 2% of Rift owners (4 cameras) experience comparative tracking with the Vive, and even then only reach those comparative figures over a much smaller tracked volume of less than 8sq m, with the average being only 3.3sq m, while the Vive average is a much more substantial 5.7sq m and can go out to an officially supported 12sq m: http://ghostline.xyz/publications/W...[{"num":1375,"gen":0},{"name":"XYZ"},0,595,0]

In fact the Vive can actually do up to around 28-30+sq m with two base stations:


My personal Vive playspace is big enough (8x4m) that I can also run my Rift in the area normally used by just the Vive:


I have and use both the Rift and Vive in lots of public demos and have had thousands of users. Last week was the Bay of Fires Youth Arts Prize, this week it is the State Youth Conference. In my experience there are far greater differences between individual users and use cases than there are between the Rift and Vive themselves. As a consumer you really can't go wrong with either the Rift or Vive HMD for first gen consumer PC VR, both will be superseded but that is at least a year or more off. The best thing is to try them both, preferably back to back, and then choose what suits you best, based on your own personal needs.

There are other HMDs hitting the market later this year, which you may also want to consider, if you can wait.

I don't understand your question, v1.0.3 is the latest version and the most up to date version will always be available here: https://github.com/matzman666/OpenVR-InputEmulator/releases

As indicated in its title the hotfix is for the new SeamVR Home, which likely you will now have if Steam is up to date, as it has been rolled out.

The HMD tracks the user head, the controller tracks the rig movement, you need both.

The motion data does not precisely measure the seat movement in 3D space, in fact the same data sent to very different designs would result in substantially different movement in 3D space. With sub mm VR tracking it is trivial to measure 1:1 where any design rig is moving.

Accuracy is affected by the distance between base stations and I believe they were 4m apart in that test using a ruler, while the sub mm claim related to 2+m apart: https://www.reddit.com/r/Vive/comments/40877n/vive_lighthouse_explained/