The expectation would be that after the rotation is set on the MixedRealityPlayspace, the camera's rotation would be 0, 0, 0 (facing the same orientation as the playspace). it doesn't seem to alter the camera's rotation as expected. I'm able to move and rotate the MixedRealityPlayspace Game Object and this does change the camera's position, however.

You would then alter the position of the camera to move the player up to another floor in the environment.Īnother reason would be if you wanted to move the user a large distance (horizontally), teleporting them to another part of a level without having to load a new So, I sort of spoke too soon. Typically, you can't see where the teleportation cursor is landing.Īn example use-case: the player uses the teleportation system to enter an elevator. When you need the player to be able to move up or down multiple floors in the environment, the hand gesture teleportation is not ideal. Movement via the teleportation system works great in single-floor virtual environments. It's understandable why the camera position is something that you wouldn't want to alter when the application is designed for augmented reality (HoloLens in particular), but for virtual reality, there are a few valid reasons to have this capability. On a device like Oculus Quest 2, this is not performant. This prevents you from having shadows via baked lighting essentially requiring real time lighting for shadows. The problem with this alternative is that it requires that you leave everything in the scene as a dynamic object rather than static. Describe alternatives you've consideredĪs a work around, I've implemented a system where the entire environment is repositioned and rotated to give the illusion that you've walked up a set of stairs and turned to face the direction you would be facing had you walked up the stairs in real life.

This could be a setting that could be enabled/disabled in the MRTK camera profile. Specifically, the ability to set the position of the transform on the main camera to a new Vector3. The MRTK camera profile being used is: DefaultXRSDKCameraProfile and at runtime the device being used is an Oculus Quest 2. It's possible when running in the editor, but not in the player. Using MRTK 2.6.1 and Unity 2019.4.25f1 LTS, it's not possible to change the camera position (via code) at runtime.

Reset playspace mover position