New Input System Knuckles Support?

Is there a timeframe for the new native input system of unity to support the Valve Knuckles controllers?

TY!

Sorry if this has already been asked to death.

 

Should be working. We have a number of issues around XR so there may still be problems. But the support is there.

 

Is there a beta update that will have more support? A dev I know for Blade and Sorcery mentioned he was waiting on it to come out for Knuckles support. TY!

 

What is the rough estimate for the OpenVR backend update?
I'm not asking for a precise date, but something like 1-2 months, mid-2019 or late-2019 will be good enough.
Thx!

@StayTalm_Unity
I just saw your last pull request on Github, thank for all that VR fixes!
Really happy that haptics has been fixed

 

@StayTalm_Unity

With the Valve Index releasing in June, It's likely that Knuckles will be releasing soon.
Any news about the OpenVR backend update? Meanwhile maybe it's possible to link buttons and axis from the old input system (https://docs.unity3d.com/Manual/OpenVRControllers.html) to the new input system?

 

Any news on support for Steam VR Input 2.0.
We would really love using the new input system for our upcoming VR projects and this seems to be the last blocker for us.

 

Hi, I was wondering if this has been fixed.

I just bought index controllers and i cant get the A buttons to work for the life of me. It does grip and even if i add new unity button ids it is not responsive. I would appreciate any kind of help.

 

Wondering if there is any information anywhere that says what the state is for Knuckles. I'd like to send a build of my project out to Knuckles users (we don't have them), and it would be good to know what I can expect should work.

 

I've somehow forced the Input System to recognize the Valve Index controllers briefly



Although that's all I managed to map. Is there no way to obtain other controller data through the new Input System? I'd like to avoid having SteamVR 2.0 SDK in order to keep the application compatible on all platforms.

 

I did some testing remotely (I don't have Knuckles locally) using a scene that prints out all available inputs.



Fun. I was able to get the alternate button and joystickorpadpressed to register...but they don't actually fire events correctly, so you'd need to read them manually and construct your own press detection. Would be so nice to have this working, so many Indexes out there now.

 

Wait, how did you access all those commands? When I look for "Knuckles" on the Input System it shows up nothing at all.

I managed to access that particular value completely randomly, can't even replicate it now

 

You can access all of the controls available (from Unity's PoV) via:

var controller = XRController.rightHand

(or leftHand) to get a reference to the controller. Then you can iterate through

controller.allControls

, casting where appropriate to the following classes:

Code (CSharp):

1. ButtonControl
2. AxisControl
3. Vector3Control
4. Vector2Control

...and so on. Each control class has values to check if they're active or not. If you have Knuckles connected, while you can see some of their inputs available in the input actions window, Unity does not have a class yet available for the Knuckles, and the controllers are instantiated as generic XRControllers, and events for the inputs are not fired.

..speaking of which, would be interested if @Rene-Damm had any info about this. My other option right now is to just right a custom input handler for Knuckles only, then toss it out when support (hopefully) arrives. But if support is gonna come soon I'd rather avoid that entirely.

 

As far as I know there is no way to obtain separate button inputs for the additional buttons of the index controllers (which were not available on vive wands) without OpenVR 2.0. This is why they neither work with the old input system (with Steam VR 1.0) nor with the new one (e.g. A is the same as Grab).
It also seems like the new XR interaction SDK isn't compatible with the new input system either.
This is getting really confusing.
@Iron-Warrior a custom input handler would certainly be interesting if index integration will take much longer.

 

Ended up just wrapping all the input functions in a class, and then extending that class with knuckles-specific functionality (using the method above) for when knuckles are present. It didn't actually take too long, and should tide my project over for the time being. Note that this only gives access to some of the buttons on the controllers, but we don't use a whole lot for our game.

 

Will there ever be knuckles input on Unity's (new) Input System?