#Windows 7 reset keyboard mapping windows#
Using a Windows Mixed Reality immersive headset and motion controllers with the HoloLens 2 Emulator Shoulder + trigger + right thumbstick up / down H (on Keyboard) + right thumbstick left / rightĪlt + right mouse button + drag mouse up / down The following set of controls is suggested for day-to-day use: Operation Hand/controller (Hold Alt, hold gamepad shoulder button, or toggle UI pushpin) The following table shows how each target modifier maps each of the core movement input concepts Input The following table describes the options for targeting, and the way to activate each of them. In some cases, it's also possible to specify with the xbox controller directly. In all cases, it's possible to specify through the UI or through keyboard presses, which object to target. We have introduced ways for you to specify which intended target your command should be applied to. The remaining concepts can be applied to one of multiple targets. Action, Bloom/System, Reset, and Tracking are complete concepts, don't need, and are not affected by, any additional modifiers for targeting. Some of the above input concepts stand on their own. Note: The controller buttons can be targeted to one hand/controller or the other using the hand targeting modifiers. You can find more information on input control modes later in this document. Each type has a different mapping depending on the input control mode. The following table shows how each type of input maps to the keyboard, mouse, and Xbox controller.
Positional: Forces Positional tracking, no matter the system requests. Orientation: Forces Orientation-only tracking, no matter the system requests. Default: The OS chooses the best tracking mode based upon the requests made of the system. Tracking: Cycles through the positional tracking modes, including:. Engage the desired hand(s) using the modifier key(s) or button(s) (Left and/or Right Alt, or the left and/or right bumper on the gamepad). Starting with the HoloLens 2 Emulator, a reset can be scoped to one or both hands. Reset: Returns all simulated sensors to their default values. You can also control the state of simulated sensor input: We have a set of useful representative poses that the emulator allows you to toggle between. We don't currently expose direct control of individual joint positions through the emulator, but you can set them through the simulation API. Pose: A complete collection of all of the Joints in a tracked hand, 26 Joints in all. Joint: One of 20 tracked positions for a given tracked hand with an associated point in 3d space. The skeleton model has 26 tracked points on each hand. In addition to being tracked/not tracked and usable for driving gestures, hands now have an articulated skeleton model fit to them and exposed to the developer. 
Hands have a rich representation in HoloLens 2.
Bloom/System gesture or Home: The HoloLens bloom/system gesture or a controller's Home button is used to return to the shell and to fire system actions. For example, the Action input can be used to simulate the air-tap gesture, to scroll through content, and to press-and-hold. Action: Simulates the action of pressing the forefinger to the thumb or pulling the action button on a controller. Gesture and motion controller input are mapped closely to physical devices: For a targeted controllable object, motion is controlled with both rotation and translation (movement) along three axes. Motion refers to controlling and changing the position and orientation of something in the scene. To get started controlling the virtual input to the HoloLens Emulator and Windows Mixed Reality simulator, you should first understand a few concepts. The details below are for advanced users who have found a need to simulate more complex types of input. Most emulator users will only need to use the basic input controls for the HoloLens Emulator or the Windows Mixed Reality simulator.
0 kommentar(er)
