[BUG] Controller ray shows up correctly (hovering works), pressing the trigger button does not trigger the select action.

[Kyoungjoon-VIRNECT]

Describe the bug

I'm experiencing an issue with MRTK 4.0.0-pre.1 on Unity 60000.0.49f1 for Quest 3. While hand tracking works perfectly fine and the controller ray shows up correctly (hovering works), pressing the trigger button does not trigger the select action. The ray does not change its visual state to indicate a pressed state, and it doesn't interact with UI elements. ( mrtk 3.2.2 input package is work )

And I attached the script below to the Far Ray object of the MRTK XR Rig, and confirmed that logs are printed when the controller trigger is pressed.

using MixedReality.Toolkit.Input;
using UnityEngine;
using UnityEngine.InputSystem;


public class TriggerFix : MonoBehaviour
{
    public InputActionReference triggerAction;
    private MRTKRayInteractor rayInteractor;

    void Start()
    {
        rayInteractor = GetComponent<MRTKRayInteractor>();
    }

    void Update()
    {
        if (triggerAction != null && rayInteractor != null)
        {
            float value = triggerAction.action.ReadValue<float>();
            if (value > 0.5f)
            {
                rayInteractor.allowSelect = true;
                Debug.LogWarning("value > 0.5f Z: rayInteractor.allowSelect  = true");
            }
        }
    }
}

To reproduce

"I cannot share my project publicly, but I followed the environment setup of the project in this link while migrating from Unity 2022.3.x version to Unity 6. The build results from this project show the same issue.

https://github.com/LocalJoost/QuestBouncer/tree/empty-starter-project

Expected behavior

Controller trigger should change the ray visual state and interact with UI elements.

Screenshots

here is my screenshot of the Unity environment settings

Your setup (please complete the following information)

• Unity Version Unity6.0 ( 6000.0.49f1)
• MRTK Version 4.0.0-pre.1
• Meta Quest 3 v76

Target platform (please complete the following information)

• OpenXR

[SashelI]

@Kyoungjoon-VIRNECT I have the exact same problem with OpenXR and Pico4 Ultra.
I managed to manually subscribe to the event via another script like this, but still nothing happens on MRTK side. Let me know if you found anything

		[SerializeField] private InputActionProperty pico4TriggerPressAction;
		[SerializeField] private InputActionProperty pico4MenuPressAction;

			pico4TriggerPressAction.action.Enable();
			pico4MenuPressAction.action.Enable();

			pico4MenuPressAction.action.canceled += Pico4_Menu_performed;
			pico4TriggerPressAction.action.performed += Pico4_Trigger_performed;

[MaxPalmer-UH]

Interesting, I've just done a check with a Quest 3 and the latest Unity 6.0 LTS release (6000.0.53f1) using the latest on the feature/XRI3 branch, which was (an earlier) source of the 4.0.0-pre.1 files and can switch between hands and controllers in the hand interaction examples scene in a build for the Quest. I get rays for both and can interact with scene elements using both hands and controllers (i.e. using the trigger on my right controller). I'll take a look at the referenced commit in this bug report, which is slightly earlier / different to the branch I've just tried to see if it changes anything.

[MaxPalmer-UH]

I assume you're seeing the UI switch between hands and the virtual controller model as the user makes this switch?

[MaxPalmer-UH]

OK, going back to the commit used to create MRTK 4.0.0-pre.1 https://github.com/MixedRealityToolkit/MixedRealityToolkit-Unity/releases I see the issue. So, it looks like that more recent work on the feature/XRI3 branch has fixed the issue.