ValveSoftware / steamvr_unreal_plugin

SteamVR Input Unreal Plugin - Documentation at: https://github.com/ValveSoftware/steamvr_unreal_plugin/wiki Sample project (UE4.15-4.23): https://github.com/ValveSoftware/steamvr_unreal_plugin/wiki/sample/SteamVRInputPlugin.zip Sample Project (UE.424+): https://github.com/ValveSoftware/steamvr_unreal_plugin/wiki/sample/SteamVRInputPlugin_UEIntegrated.7z

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Axis binding SteamVr

Azool2 opened this issue · comments

Here are my issues with Steam VR Axis binding:
https://youtu.be/JSdHVT8JOEI

Thank you for your time.

Hi @Azool2 - sorry about the delayed response, I somehow missed the github notification for this issue.

Anyways, really appreciate the detailed report you sent. In the video, at 1:42, it seems like you've got your personal input bindings enabled and not the default one that the engine is sending:

image

You need to activate the default bindings from the project. Let me know how that goes.

Cheers,
Rune

Dear Rune, thank you very much for your reply.
Unfortunately, that is not the problem, and it can't be the problem, otherwise I would have found it long ago.

01
02

I'm going to record a video this weekend to show it.
I'm looking forward to your answer.
thank you again for your time, Rune.
Cheers,
Armin

https://youtu.be/6ao5OhQEu8U
I record a new video.
Thank you.
Let me know if you see a problem.
Thanks.

Hi @Azool2 - Thanks for the update.

You need to create a "pair" for thumbstick and trackpad bindings. This is because steamvr uses vector2 (float, float) actions while UE (outside of the new enhanced input system) only supports vector1 (float) bindings,

So in UE, if you create a MOVE_Y action that is bound to ThumbstickY, you need to also create a MOVE_X action that is bound to ThumbstickX. The steamvr input plugin will then recognize what you're trying to do and create behind the scenes a vector2 action to send to steamvr.

For the plugin to recognize you want a vector2 action:

  • Make sure the naming is the same for the actions you want to pair - e.g. MOVE_X, MOVE_Y and not MOVE_X, MOVE_SOMEHTING_Y

  • Also, ensure that the suffix of the action name is _X and _Y (with the underscore)

If you're still having issues after checking the above, send me a minimal repro project and I can have a closer look.

Cheers,
Rune

Thank you, Rune, that was exactly the problem. We have to make 2 _Y and _X.
Thank you for your time.
Best Regards
Armin

Awesome! Glad that worked out :)