Question SteamVR actions not firing consistently on some control inputs

I have a Vive Pro Eye (and have got the same behaviour on a standard Vive) and I recently changed the controller binding of 2 actions from one controller to the other and now one of them only works very occasionally; I definitely have the correct hand assigned as one of the actions in that script works, and the other works occasionally. The actions are bound to clicking directions on the D-pad, but click north is only triggering the action very rarely, though the other directions do work properly. In VR looking at my hand and controller it is clearly detecting my touch on the North of the d-pad, and sensing the click as the VR model of the controller shows the touch and button press. Binding one of the actions to the grip button it works fine, reverting back to the other hand also works fine. Binding a different action to click North I get the same behaviour - intermitent action triggering. SteamVR live input viewer shows the same behaviour, the action triggers occasionally. I can't figure out a consistent way of making the action work to connect the problem to anything in the scene. I have tested my controllers in the SteamVR controller test and they work fine there (and have switched hand assignment of the controllers, and tested with someone else's controller) so it is not a hardware issue. Does anyone have any suggestions what could be interfering with the action working?

Unity 2021.3.13f1. SteamVR Plugin v2.7.3

 

Could you provide some screencaps of what you are trying to bind? And how you bind it vs what is "out of the box" when it's standard.

 

HI @Chimpien - can you check if your issue is similar to this:
https://steamcommunity.com/app/358720/discussions/0/1734342161853608849/

otherwise, can you check the active bindings from: Unitiy Editor -> Window -> Steam VR Input -> "Open Binding UI" (screen caps as what nilagard suggests, would definitely be helpful)

 

Hi,

Attached is screenshots of the binding UI and package list, and the script file containing the jump actions.

As I explained the grip binding of the action works as expected, and when rebinding jump actions to the right d-pad the actions work as expected also (although the east and west actions are triggered accidentally a lot).

 

I believe you are trying to bind this through the SteamVR bindings list, this ain't gonna work like you want it to. You have to programatically bind this inside Unity through either code or the XRAction assets. The way you are binding it now have nothing to do with the way it works with your scripts, it will always be in conflict with your scripts. I suggest reading/following a few VR guides on how to program/setup your VRControllers and buttons.

 

Thanks for the update and screenshots.

First off, you need to save your bindings as the default binding:

(a) Click on "Replace Default Binding"
(b) Click "Back"
(c) Under "Official Bindings", click on "Activate" to make your edited bindings the default one for your project.
(d) Click on "View" on the now "active binding" (this shouldn't be "local changes") to double check if your bindings have been properly saved and active.

In your script, the action names doesn't seem to match the ones in the Binding UI, did you add the actions via the SteamVR Input Window? (Window > SteamVR Input)

For step-by-step instructions on how to add bindings, you can refer to this documentation:
https://valvesoftware.github.io/steamvr_unity_plugin/tutorials/SteamVR-Input.html#adding-an-action

For dpad actions, you can fine tune them in the settings (gear icon):


Finally, this is the quick dpad test project I created using latest versions of our Unity XR plugin and Interactions/Input Plugin.
https://www.dropbox.com/s/p6ailh8b0fv10g3/SteamVRInput.zip?dl=0

Scene is: Assets > Steam VR > "Simple Sample (scene)"
Script is here: Assets > SteamVR > Interaction System > Samples > Scripts > "Jump.cs"

Note: The method I used in Jump.cs is not the only way to do it nor is it the recommended one - you'd have to judge which one works best for your project (other methods here: https://valvesoftware.github.io/ste...R-Input.html#working-with-actions-in-the-code)