VR Expansion Plugin

[mordentral]

@Bino

Hi,

Big fan of plugin. I’m mainly integrating it via C++ and found I needed the following changes.

I think my approach has maintained the patterns you have. But correct me if I’m wrong

GripMotionControllerComponent::GripObjectByInterface

When function eventually calls GripComponent it passes NAME_None as the socket name. I needed to add an optional socket name parameter to function and pass it. Now grips at the socket location.

**I tend to prefer using direct transforms of sockets now instead of the SocketName parameter, it is more flexible and user controllable (GetSocketTransform - pass in as relative grip transform). It also lets the user directly make use of my new controller profiles system to alter socket grip transforms per controller type. Rather than adding the SocketName parameter to a new location, I would favor removing it from its current locations instead.

The example template never uses the socketname parameter anymore, it only passes in transforms.**

GripMotionControllerComponent::AddSecondaryAttachmentPoint

I create a BP that inherits a grippable static mesh. The secondary grip event wasn’t being fired. In other functions you test for the interface on the component and if that fails you try on the Owner. I added that same pattern here. Now works.

**Those secondary cases are for looking for the interface, then it switches to an actor / component grip based on that. If your “actor” wasn’t receiving the secondary grip event it was because the “child” grippable is the one being gripped and it was the one that received the event (as it should).

The plugin grips both actors and components, and components have priority so you can separately grip components in a grippable actor. The correct way of receiving your secondary attachment notice in the actor would have been to add an “OnChildSecondaryAttachment” event and fire it off on the owner / parent component as well. However generally two handed interactions are done with actors and you can subclass a grippable component and pass the event up to your custom actor anyway so I don’t feel like it is worth the interface bloat to add another event case for .**

Replies in quote above.

Suggestions and ideas are always welcome, no matter my response above, thanks for suggesting!