When playing the VR template in 4.14 preview 3 with the HTC (cannot test w/ other devices), the player is spawned at 0,0,0 facing 0 yaw instead of the “Current Camera Location” or the “Default Player Start” no matter which is chosen.
Steps to reproduce:
- Create a new project using the blueprint VR template.
- Open the MotionControllerMap.
- Move camera to position on map other
than 0,0,0.
- Play the level in VR using the VR
Preview.
- Observe start location.
- Place Player Start in the map at
location other than 0,0,0.
- Change selection to spawn player at
“Default Player Start”.
- Repeat steps 4-5.
Hello Cameron Abt,
I was unable to reproduce this issue on our end in the latest release (4.14). I have a few questions for you that will help narrow down what issue it is that you are experiencing.
- Can you reproduce this issue in a clean project?
- If so, could you provide a detailed list of steps to reproduce this issue on our end (including any small steps that may have been missed in the original thread)?
- Could you provide screen shots of the issue and/or any settings that may have been altered?
I can confirm that this still happens in the blueprint Virtual Reality template in 4.14.0.
- Yes
- Please follow the steps in my
original post.
- Not sure that screenshots will help prove my point. Setting up the camera in the editor at the corner of the level, and then playing the VR preview from the camera location will spawn the player at 0,0,0, NOT at the camera location as it is supposed to.
I am still unable to reproduce this issue on our end. Has the project that you are using been upgraded form an older version of the engine? If so, could you provide the engine version(s) it was upgraded from?
Very interesting. No upgrade, completely new project, created as a blueprint project, in both my custom compiled 4.14.0 and binary 4.14.0 versions.
Perhaps it has to do with the fact that my system is currently setup as standing room only?
I tested this issue on our end using standing room only and it did not reproduce this issue on our end. Does this issue occur in other maps (other than the VR preview map)?
Hello Cameron Abt,
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 follow up.
Thanks,
If you can’t get the same result, than we’ll just chalk it up to my setup. It’s not a show stopper by any stretch and probably not worth any more of your time. But thanks for checking it out for me.
Thanks,
Cameron
I will be converting your last comment to an answer. If at anytime you would like to reopen this issue, please feel free to do so by providing any additional information you may have on the issue and I will be happy to assist you further.