Migrate arc-vr-ui completely to the new InputSystem

[Helliaca]

All of arc-vr currently only uses the new InputSystem, except for arc-vr-ui, which partially still relies on the old one.

The VRInput component only works when placed alongside a 'StandaloneInputModule', a 'InputSystemUIModule' will make the VRInput component obsolete, and thus lead to following issues:

• The key-bindings set on the UIInteractionProvider will not have any effect whatsoever. The inputs will instead be taken from the action-list set on the InputSystemUIModule.
• The inputs from the other controller will be used by UIInteractionProvider as well. (Eg. you can point to a UI element with the left controller, then press the trigger on the right controller to click, even when the right controller has no components attatched.

[amr2o12]

Hi there,

I came across this issue and was wondering if there have been any updates since it was opened.

Has there been any progress or a potential workaround for this? Would love to know if this is still an ongoing issue or if there’s been any progress on a fix.

Thanks!

[Helliaca]

Hi!

Unfortunately, I've been (and continue to be) busy with other projects as of late. There's a 2022-udate branch that adds some features to this framework, like passthrough for Meta Quest headsets etc., but the InputSystem is still based on the old one.

In other words: The framework still relies on the old input system and I can't give a good estimate on when it may get updated.

I am, however, very open to accepting any pull requests if someone creates a fix in the meantime.