Do navigation on rails gestures not work very well when the headset is rotated?

Flarb

So I've been messing around with a project where you use rails navigation gestures to move a drone around the room. There's a video of it here:

https://youtu.be/KF75GUse8SM

One thing you might notice is that when my head is oriented up or down, the gestures don't seem to work very well--or sometimes get mistook for a different direction. Do navigation gestures not work reliably if your head is tilted up or down? Is this something that is still being refined in the SDK? Or am I doing something wrong?

HoloSheep

Cool demo @flab,

to add to @CarSunKey 's point part of what you are experiencing may be due to the fact that the Gesture frame is separate and different from the view frame.

Note the docs describe it this way:

HoloLens looks for hand input within a cone in front of the device, known as the gesture frame, which extends above, below, left and right of the display frame where holograms appear. This lets you keep your elbow comfortably at your side while providing hand input. When using the HoloLens Clicker, your hands do not need to be within the gesture frame.

So it sounds like the placement and optimization of the sensors involved with gesture detection may be targeted at the facing forward (arms at your side) scenario.

As @CarSunKey points out, when you look say straight up , the cone (frustum) becomes mostly out of the reach of people with typical length arms.

You might also want to experiment with the clicker as it has gyros that handle scrolling and movement. The May update release notes also mention that some of that functionality has been improved through the software update:

The clicker has been fine tuned to enable resizing & moving holograms with a clicker.

CarSunKey

One thought may be that when looking up, and therefore moving the sensor fov up, your hands are out of the Hololens sensors range/frustum.

HoloSheep

Cool demo @flab,

to add to @CarSunKey 's point part of what you are experiencing may be due to the fact that the Gesture frame is separate and different from the view frame.

Note the docs describe it this way:

HoloLens looks for hand input within a cone in front of the device, known as the gesture frame, which extends above, below, left and right of the display frame where holograms appear. This lets you keep your elbow comfortably at your side while providing hand input. When using the HoloLens Clicker, your hands do not need to be within the gesture frame.

So it sounds like the placement and optimization of the sensors involved with gesture detection may be targeted at the facing forward (arms at your side) scenario.

As @CarSunKey points out, when you look say straight up , the cone (frustum) becomes mostly out of the reach of people with typical length arms.

You might also want to experiment with the clicker as it has gyros that handle scrolling and movement. The May update release notes also mention that some of that functionality has been improved through the software update:

The clicker has been fine tuned to enable resizing & moving holograms with a clicker.

neerajwadhwa

@Flarb Navigation gesture is recommended for scenarios like scrolling large amounts of data or rotating objects aka continuous movements.

Manipulation gesture is recommended for more fine grained scenarios like moving holograms or resizing windows.

You can look at the Holograms 211 Gestures academy for examples of both these gestures. I believe manipulation will work better for your scenario. HTH!