You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Due to the common well documented side-effect of moving around in VR causing motion sickness many VR applications implement movement across a 3D space using teleport controls.
Teleport controls allow an end user to use one of their motion controllers to point to a location using a visual interface of a highlighted circle to choose to a location where the camera will be relocated to.
This involves having a button or joystick on one controller (typically the right controller) trigger the highlight circle being shown, and susequent motion from the controller moving the spot around, followed by the inverse action of either releasing the joystick or button that was initially pressed for the camera relocation to be triggered and the user now seeing the world from the perspective of the new location.
Due to the change in location being instantaneous the end user doesn't experience any "motion", hence this method of navigating a VR application being most preferential in avoiding motion sickness and tending to be the most commonly utilised method of moving around in a VR world excluding natural movement of motion controls and HMD.
Vue already has an built-in unrelated component named and with teleport controls mainly used in VR applications as opposed to AR applications, it would seem most beneficial to create a component called
This component will allow users to teleport using a single motion controller, defaulting to the right handed controller with the joystick being used to trigger the aiming interface. Most application 3D or VR use the right joystick for movement, and if using teleport controls it makes the most sense to use this as the default trigger under the expectancy developers are more likely to use the other buttons on the controller for purposes differing from movement.
The text was updated successfully, but these errors were encountered:
Due to the common well documented side-effect of moving around in VR causing motion sickness many VR applications implement movement across a 3D space using teleport controls.
Teleport controls allow an end user to use one of their motion controllers to point to a location using a visual interface of a highlighted circle to choose to a location where the camera will be relocated to.
This involves having a button or joystick on one controller (typically the right controller) trigger the highlight circle being shown, and susequent motion from the controller moving the spot around, followed by the inverse action of either releasing the joystick or button that was initially pressed for the camera relocation to be triggered and the user now seeing the world from the perspective of the new location.
Due to the change in location being instantaneous the end user doesn't experience any "motion", hence this method of navigating a VR application being most preferential in avoiding motion sickness and tending to be the most commonly utilised method of moving around in a VR world excluding natural movement of motion controls and HMD.
Vue already has an built-in unrelated component named and with teleport controls mainly used in VR applications as opposed to AR applications, it would seem most beneficial to create a component called
This component will allow users to teleport using a single motion controller, defaulting to the right handed controller with the joystick being used to trigger the aiming interface. Most application 3D or VR use the right joystick for movement, and if using teleport controls it makes the most sense to use this as the default trigger under the expectancy developers are more likely to use the other buttons on the controller for purposes differing from movement.
The text was updated successfully, but these errors were encountered: