VR Expansion Plugin

[mordentral]

@Tomo Kunagisa

Thank you very much for your quick response!

It breaks was perhaps the wrong way to put it. When I added a gamemode and had the player spawn off of a VRPlayer Start, the mesh became offset, the camera was looking out of approximately the center of the mesh, and the arms were no longer moving around with the motion controller properly. I believe it has something to do with where my mesh is placed relative to the HMD’s position. Is there a specific way I should be attaching it to the ParentRelativeComponent? Or will I need to find the offset myself when adding the mesh to the character?

The strange thing is that when there is no gamemode, the HMD and motion controllers move the character properly and the hands move to the proper side of the character. When the gamemode is added, even a BaseGamemode that’s been extended and uses the right pawn (I think), the arms no longer translate properly with movement. The head still follows the proper rotation. I think means that the HMD is in a different position relative to where it originally was?

Is there an example character in the template that uses a single skeletal mesh with a VRCharacter I could take a look at? Apologies for the rambling question.

You aren’t using the correct pawn if the camera is waist height to begin with / you haven’t started up VR mode correctly. If you want head locked VR you need to change the cameras position (change NetSmoother height), if you want roomscale you need to set the VR mode to roomscale and then that simple character should just work.

Sounds like you have the VR mode set to Eye Level to be honest which none of my default setup is made for, its easily possible to use that mode, but there is less reason to since the main point of the characters are the room scale movement being tied into their actions.

Edit I guess you could argue that the networked snap turning and climbing are reason enough to use a non standard character for head locked VR.

Regardless, when you changed game mode you were no longer initializing VR correctly.

As for the Parent Relative Attachment, it is by default locked to the head position for chests and inventories and waists and the like, you can set a bool on it to lock to the foot position instead which is generally better for being the parent of a SkeletalMesh body.

Also no, I don’t have a full IK example in the template, to do it “correctly” would involve forcing a third party plugin or coding custom IK, neither of which I am willing to do for it. The default in engine IK setup is not good enough for a decent full body rig in VR, there are many third party solutions now that perform well so I point people to them when asked instead (leave that up to the specialists).