Unity 2020 LTS + Oculus doesn't read Oculus input, and fails to import ASMDEF in new project

Question

Unity 2020 LTS + Oculus doesn't read Oculus input, and fails to import ASMDEF in new project

wirelessdreamer opened this issue 3 years ago · 8 comments

Button input doesn't work in test scenes. Using a Quest 2 with Link.

Test Project: https://drive.google.com/file/d/1t3BxSY-m_TqIvNp39wjCEDvZ4b16krEE/view?usp=sharing

Answer 1 · 2021-08-04T12:58:34.000Z

The first part of this issue is from the package from the asset store, manually downloading the VIU release, and copying the missing asmdef's resolves the initial warning., Input over link, and in Quest builds still does not work though.

Answer 2 · 2021-08-04T21:34:30.000Z

I get the same results in the current version of Unity 2021 as well. I've tried with both Oculus, and OpenXR without success of reading oculus button input.

Answer 3 · 2021-08-06T13:14:44.000Z

Using the latest release from the releases page has the same issue and the package on the unity store.

Answer 4 · 2021-08-09T08:30:40.000Z

@wirelessdreamer Are you using VIU from Asset store or UPM?

Answer 5 · 2021-08-10T13:02:26.000Z

Same results with both.

Answer 6 · 2021-08-11T06:38:38.000Z

@wirelessdreamer Current VIU v1.13.2 is not compatible with Oculus Quest 2.
It will take some time for us to fix issues starting from Oculus Integration v20.1(First version supporting Quest 2).

Here is a quick fix for you to run your Quest 2 using Link Quest,

In Assets\HTC.UnityPlugin\VRModule\Modules\OculusVRModule.cs,

line 556, add
case OVRPlugin.SystemHeadset.Oculus_Link_Quest_2:
case OVRPlugin.SystemHeadset.Oculus_Quest_2:

In Assets\HTC.UnityPlugin\ViveInputUtility\Scripts\Misc\OculusVRExtension\VIUOculusVRRenderModel.cs,

line 871, add
case OVRPlugin.SystemHeadset.Oculus_Link_Quest_2:
case OVRPlugin.SystemHeadset.Oculus_Quest_2:

Known issues,

You will not be getting the correct Quest 2 controller model
Controller model might get wrong model, for example, left model is showing right model or button is not in correct place

Sorry for the inconvenience.
If you have further question, please let us know, thanks!

Answer 7 · 2021-09-08T14:05:38.000Z

@chengnay Just found this fix, thanks! I've been able to deploy to Quest 2 as well now. The one thing (and I note it is a known issue) is I have no controller rendering at all.
This is with:

VUI 1.13.4.0
Oculus Integration 32.0.0
Oculus XR Plugin 1.10.0
OVR 1.63
OpenXR 1.2.8 (not sure if this is needed, I am updating a legacy application).

Answer 8 · 2021-10-11T09:48:11.000Z

Fixed my own issue, not a problem now.
Under preferences > VIU settings (where you switch platform), expand Global Custom Render Model and set the Oculus Quest Controller Left/Right to OculusTouchForQuest2_{left/right}.