Question Unite 2022 - XRI 2.2 and cross device play

Hi @ShawnFeatherly,
The release notes for XRI 2.2 can be found here. While there is nothing specifically added for any one particular device, we made enhancements to some of the workflows that make it easier to work on XR projects, such as some minor fixes to the Device Simulator that makes it easier to test interaction capabilities having to switch project settings, automatically adding needed components when using the Input System with the XR Origin, and the biggest one is adding the required prefabs to get started in a fresh project (can be found in the Starter Assets sample package found in the XR Interaction Toolkit area of Package Manager). These prefabs are setup/tested with the most common XR devices, such as Meta Quest 1 & 2, Windows Mixed Reality devices and PS VR2. We have also tested with HTC Vive Pro and Valve Index, but there are some documented input changes required to fully utilize those devices at this time. We do hope to integrate those needed pieces into the standard offering for XRI so developers don't have to build custom solutions for every different controller type out there.

In our upcoming release of XRI 2.3.0, we will be adding even more features to utilize new devices and input modalities that are becoming more and more common (such as hands as gaze).

 

@Shizola,
The samples you saw during Unite will ship soon as a replacement for the XRI Samples in GitHub due to the size of the project (we don't want to bloat your package folder). We are going through our internal standards process and cleaning up the project for public release, so this should hopefully land soon.

@mikeNspired,
This is somewhat in-line with how Unity does releases in general: new tech-stream releases while still supporting LTS versions of the Editor with patch fixes. The most recent feature release for XRI was 2.2.0. This is not to confuse the latest patch release of XRI, which was 2.0.4, which was a backport of fixes from 2.2.0 to the 2.0.x branch. This is done for LTS versions of the Editor where the verified feature set is locked for almost all non-critical packages (in most situations anyway). In any case, to update to 2.2.0 in 2021.3 or 2022.1, you would need to modify the manifest file, as you said. This is definitely not the most user-friendly process, but we are looking to improve that and discoverability in general.