Search Issue Tracker

In Progress

Fixed in 3.0.6

Fix In Review for 2.6.4

Votes

3

Found in [Package]

2.6.3

3.0.1

Issue ID

XRIT-157

Regression

No

Error “InvalidOperationException while resolving binding ‘Eye Gaze Rotation:QuaternionFallback'“ when entering the Play Mode with XRI Default Input Actions.inputactions selected as Project-wide Actions

Package: XR Interaction Toolkit

-

Reproduction steps:
1. Open the attached project "ReproProj"
2. Open the “/Assets/Samples/XR Interaction Toolkit/3.0.3/Starter Assets/DemoScene.unity” Scene
3. Enter the Play Mode
4. Observe the Console window

Expected result: No Errors exist
Actual result: Errors such as “InvalidOperationException while resolving binding ‘Eye Gaze Rotation:QuaternionFallback'“ are present

Reproducible with: 3.0.0 (2022.3.0f1), 3.0.3 (2022.3.0f1, 2022.3.30f1, 6000.0.2f1)
Could not test with: 3.0.0-pre.2 (2022.3.0f1), 3.0.3 (2021.3.38f1, 2022.2.21f1) (Project-wide Actions option does not exist)

Reproducible on:
Play Mode

Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested

  1. Resolution Note (fix version 3.0.6):

    Added a validation rule to the Starter Assets sample to check that Input System >= 1.11.0 to avoid confusing error messages when Project-wide Actions are used that contain custom processors, composite bindings, or interactions.

  2. Resolution Note (fix version 2.6.4):

    Added a validation rule to the Starter Assets sample to check that Input System >= 1.11.0 to avoid confusing error messages when Project-wide Actions are used that contain custom processors, composite bindings, or interactions.

Comments (1)

  1. chris-massie

    Aug 01, 2024 20:08

    Current workaround is to unset Project-wide Actions and instead use a component like Input Action Manager to enable the Input Action Asset instead. That component will enable the actions during OnEnable, which is after the custom composite bindings, interactions, and processors in the package registers them with Input System. Currently when the Project-wide Actions are set, the actions will be enabled by Input System before the definitions can be registered, causing the errors.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.