The OpenVRInput plugin / module customizes the action manifest to allow skeletal actions and add missing keys.
It also supports hand gesture detection and skeletal animation both per hand as well as adding it to a full body IK setup.
A few bugs currently in Epics main Beta input are also fixed.
You can either clone it or go to downloads and download the repository:
There is also a seperate branch for using it without the full VRE plugin for those that don’t want to use the main plugin and just want the skeletal actions and other related functions.
I am not yet providing pre-built binaries for the module. The current branch should work in engine versions 4.19 – 4.22.
If you are running the module WITHOUT VRExpansionPlugin and are not using the branch specifically intended for this, then open up OpenInputPlugin.build.cs and change the line
bool bCompileWithVRExpansion = true;
bool bCompileWithVRExpansion = false;
This will cause it to no longer compile against my primary plugin and to act standalone. You will also want to remove the reference to it in the OpenInputPlugin.uplugin file.
Alter your DefaultEngine.ini file to include this:
This turns on beta input and enables the custom beta input of the new SteamVRInputController shipped with this module (if the official Valve plugin is not active).
The skeletal action names used are below (auto set if the skeletal action name is blank):
I am setting the plugin to default to these for now when none have been provided by the end user.
You can access the local binding interface from your desktop here:
http://localhost:8998/dashboard/controllerbinding.html or by following the link in this websites menu to it (added for convienance).
You may want to get the knuckles controller profile from the latest template (if using the VRExpansionPlugin).
Also I am also packaging the OpenInput testing hands as they are pre-rigged and fully setup already and they look 100x better than pretty much all stock hands for ue4. When using ue4 hands you likely will want to turn off bone morphing in the settings as they likely won’t be rigged correctly for it.
Load in and go to your pawn, under each motion controller add an OpenInputSkeletalMeshComponent
Add at least 1 skeletal action to the skeletal action array and set its hand type (Left or Right under SkeletalData)
If you have a custom action manifest generation then add the action names in, if you do not then they will be auto filled with my defaults.
Leave the rest of the settings default for now.
Set the mesh and animation blueprint for the mesh
Open up the animation blueprint for your hand meshes
Click on “ClassSettings” on the menu bar
Re-parent the class to the OpenInputAnimInstance class
Go to the Anim graph for the anim blueprint and drop in a Apply_OpenInput_Transform animation node
Hook up the output to the final animation pose input
Change the drop down selection to which hand right/left it is (I may automate the hand type at some point) and which skeleton to use OpenInput/UE4
You can also manually map a new skeleton but that is for advanced use.
4. Full body setup
If you are doing a full body setup you will need two skeletal actions and two Apply_OpenInputTransform nodes in the animation graph, one for the left and one for the right hands.
You will also likely want to tick on bSkipRootBone on these nodes so that the wrist isn’t moved (unless you have a proxy bone where the wrist is to allow controller offsets).
Also for the left hand you will likely need to tick the “MirrorSkeletal” boolean on the action struct as the OpenInput skeletal data is not setup for inverse directions.
You also will want GetTransformsInParentSpace true and AllowDeformingMesh false (if the hand mesh isn’t weighted and rigged correctly).
The SteamVRInput system is a robust and flexible input re-mapping setup, allowing users and devs to define profiles for all supported controllers and even set up legacy profiles to support older games as the system upgrades.
It uses the concept of “ActionManifests”, lists of actions in a JSON format that the program uses and expects bindings to be assigned for. The developer is to supply the default mappings per controller for this list. The end user is also capable of overriding the default mappings, or creating entirely new mappings for new controllers or hardware that didn’t exist at the time of the games creation or that the developer did not have access too.
The input style and methodology is very close to the OpenXR spec that has recently been released and it should very seamlessly merge in with it when the time comes I assume.
If you are interested in the actual line by line format of the action manifest you can find more information here:
As generally the developer shouldn’t need to directly interact with this file. I will walk you through a very basic input mapping / setting default profiles for a controller that you can ship out with your game.
Prior to starting mapping you will need to do a few things.
First of all, if you are using my OpenVRInput module then you will need to follow the setup instructions for it. If you are not then you will need to enable the engines default OpenInput Beta via config file.
Then you will need to load into your project with SteamVR running so that the manifest generation takes place.
The manifest is generated on program launch (every program launch) at the GeneratedConfigDirectory. In editor projects will generate this at
projectdir/saved/config/steamvr_actions.json and packaged projects will generate this in the
users appdata/unreal engine/project name/config/steamvr_actions.json.
The default bindings files are generated only in editor, and only if they don’t already exist. You are expected to ship these with your packaged game. They exist in
Then to make sure that you have access to all data and the ability to easily overwrite the default bindings, you should open up SteamVR, go to the Settings tab and enable the pictured field, it will enable the advanced developer controls.
Once this is enabled you can either load up the bindings interface in the settings menu in VR. Or you can follow this link (also a shortcut in this website menu) to load the browser version.
You will see the binding interface.
Clicking on a button or feature will let you map it to one of your applications input events / axis’s in the engines input settings. See below for an example of some of the events my template passes forward to SteamVR.
Selecting the trigger button and hitting + will give you an option of input types to assign to it. Here I have assigned it to a Trigger action type.
Then clicking on the “Click” event I am given the option to assign one of the engine input events that I have setup.
Then your engines event should fire when the controllers trigger is clicked. You can launch into your project (or get out of the VR menu overlay if doing this in VR) and test out the button.
If using my OpenVRInput module then you will also want to assign the default skeletons it provides by clicking on below.
And then assigning the correct skeletals to each hand.
Once testing is complete and all mappings are done, you can export the mappings to the default controller bindings for your application by clicking on “ReplaceDefaultMapping”.
Congratulations, your controller type is now setup for SteamVRInput!
There is more advanced things you can do with it, but these are the basics.
The video in the first section goes over the gesture detection. I will flesh out an image based tutorial for it soon.