SUNROCK: SteamVR Knuckles Support for UE4

[mordentral]

@YuriNK

1. If UE4 SteamVR plugin generated binding and actions manifest files, it would re-associate UE4Editor with actual inputs every time you open a project. Binding files are only geenrated in editor. For packaged game, user can overwrite them via standard SteamVR interface.

2. I want VR input in my project working regardless of hardware I use. For Vive controllers, Knuckles, Touch via SteamVR, Touch via Oculus API.

Example: I use touchpad for locomotion input. But touchpad on Knuckles isn’t good for this purpose, because it has very limited X axis. Instead, I have to use joystick. So I need custom binding files to bind Vive/touchpad and Knuckles/thumbstick to the same action, because I can’t separate touchpad at Knuckles from touchpad at Vive controllers in my player controller blueprint. And even if I could - it’s unnecessary duplication of work instead of unification.

Oculus has no similar input system, it uses default UE4 events for motion controllers. And I don’t understand how you’re going to build unified input system without using unified input events/axes.

1. It DOES generate binding and action manifests every time you open it though… The default bindings are just only overwritten if they don’t already exist. Steam Input no longer “remembers” manifest files between launches now either so it doesn’t corrupt other projects that are using the legacy pathway.

2. Yes? That is the point of SteamInput, I think you might have misunderstood me, I wasn’t saying to NOT use SteamInput, I was saying that automating the binding by hardcoding it isn’t necessarily a good thing as the entire system is meant to be used off of the “action” names not hard axis references. When the generic interface becomes XR across the board they will ALL work much like SteamInput does currently.

I was responding to

• The plugin doesn’t generate input for Knuckles for Trackpad press/release

, which it shouldn’t have to do, as that would be an event that you can define through the editor and set up with the bindings files.

Regardless I don’t exactly have the native oculus vs openInput issue myself as I have an XR like interface for dynamic input re-binding per controller type that covers it already cross platform until the unified standard is out.