v71 Break Open XR Implementation?

Yes, I got this behavior too, after updating to v71 on my Meta Quest Link (App Version 71.0.0.451.524). The controller rays are not correctly detected when the controllers are pointing below the same line as the sight. I am using Unity 2023.2.20f1, OpenXR Plugin 1.10.0. 

On my Meta Quest 1 (which has an older version - v50) this does not happen, so clearly it is an update issue. 

This is now Ticket #58882 with Meta Developer Support.  Seems to be effect Quest 3 and Pro with v71, but not Quest 2.

Similarly having issues with OpenXR hand tracking input since updating to v71, while users on v69 have no issues.

In my case I'm using MRTK2, and grab pointer input no longer works in v71.

I have the same issues with v71. Also reporting those issues on Quest 2 after updating to v71. Also can confirm the Quest 3S has the same problem with v71. On Quest 3 that is still on v69 the issue does not show on build, but weirdly it does show when testing on it through Quest Link. Any other headset that is on v71 also has this problem through Link, but I don't know why it also happens with my Quest 3 that is still on v69.

The problem I see is controllers being wrongly prioritised over Hand Devices, resulting in wrong input actions fallbacks and wrong/false tracking mode events.

Here's what helped for me to resolve OpenXR hand interaction issues I was seeing only since updating to v71, hopefully it helps someone else, although my issues were hand tracking related, not controller related:

I am using the Unity OpenXR plugin, and was previously using the "Hand Interaction Profile" on Android for Quest deployment. Removing this interaction profile and instead using the "Oculus Touch Controller Profile" solved the issues I was seeing.

(Project Settings -> XR Plug-in Management -> OpenXR)

Although this will work for me in new versions of the app, it's frustrating that all previous versions of the application no longer work in v71.

I have a related issue with Meta XR Core SDK 71.0.0 - if you add this package to an Open XR project - you can use Unity's VR Core template as an example - it breaks controller tracking in Unity Play Mode (Unity 2022.3.55f1) - controllers don't appear regardless of how you configure the open xr package settings or device profiles (I've tried just about everything imaginable to try to make this work). XR Input Controllers also don't show up as supported devices properly in the unity input debugger.

Apparently, this happens also in v72...

Does anyone have any updates?

Hey everyone! I'm getting caught up on trying to track down issues like this but there are a lot of different potential things going on just in this one thread for me to tease apart so please bear with me.

First and foremost: ImmersiveMatthew I checked on ticket #38882, and it looks like our support team closed it because you didn't respond when they reached out. This isn't the same system that our software developers use to track bugs and updates, though—that ticket number is for your individual conversation with support, not the separate ticketing system our engineers are using to track problems internally.

If anyone in this thread is still having this issue, I encourage you to reply directly to this thread with information about the specific problem you're having—how the plugin is breaking and what sort of results you're seeing when you use it.

If I have a workaround or some information that may help you, I'll be happy to share it with you here. If it's a software issue that needs to be resolved by the engineering team, we'll direct you to file a bug report using our bug reporting tool.