4.11 SteamVR breaks on Blueprints with ActorComponents

Hello,
i was building a VR Controller using MotionControllers utilizing Blueprints. At some point i wanted to sort the Blueprint and decided to put the mesh and some code into an addition actor blueprint that i would attach as a child under the MotionController.

Once you a blueprint as a child in your Pawn Blueprint it will break SteamVR - meaning your controllers will no longer show up in the game-world and your Head Position is actually under the ground. It appears something seems to be breaking code once a Pawn has child actors.

Hello Burnz,

I have a few questions for you that will help narrow down what issue it is that you are experiencing.

Quick questions:

  1. Can you reproduce this issue in clean project?
  2. If so, could you provide a detailed set of steps to reproduce this issue on our end?
  3. Could you provide screen shots of any blueprints that may be involved with this issue?

Hello Burnz,

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will offer further assistance.

Thank you.

Hello ,

Could you answer the questions that were given to Burnz in my original post? This will help narrow down what issue it is that you are experiencing.

We also met the same problem, when we use HTC , the default camera height corresponding is HTC ground.
This leads to the height of the camera is too high.
When we are watching the Showdown VR Demo, our viewpoint is so high.

Hi Ludy

our problem is that we are standing on the air when we launch the Showdown VR Demo in UE 4.11. however, when we launch the Showdown VR Demo in UE 4.10, we are standing on the ground in which the position is correct. Could you help us to get correct position of Showdown VR Demo in UE4.11 instead of standing on the air.

Hello ,

I was able to reproduce this issue on our end using the show down demo. I have written up a report ( UE-30377) and I have submitted to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. I do not have a workaround for this issue at this time.Thank you for your time and information.

Make it a great day