VR Expansion Plugin

[McFlyTechGuy]

is unrelated to the plugin, and is base engine setup stuff. The plugins character offsets the hmd from its netsmoother root which is at actor 0,0,0. The behavior you are having would be the same with a normal pawn setup like in Epics documentation.

Quest setup as far as actors and components is no different than any other VR hardware in engine, its compiling out to it and its limited resources where it differs.

I haven’t heard of an issue like you describe besides from people using the ResetOrientationAndPosition nodes in 4.24 which are broken and don’t reset the controllers (though I thought that was a steamVR specific issue in 4.24). Setting floor level tracking makes the 0,0,0 point of your HMD and controllers root component be the center of your tracked space. Have you set up a valid room boundry in your quest?

Thanks for the tips modentral! Yeah I’ve tried redoing the boundaries with the quest guardian set up a few times to no avail. I’m thinking I’ll start messing around with the VR unreal template and work backwards and then add the plugin in there for testing after I test it with a few basic pawns. Based on what you’re saying I must be overlooking something simple here. I’ll report back here if I do eventually figure it out in case any other newcomers run into issue.

BTW I loved the new update video and I’m excited for the future with plugin!

Thanks Again!