VR Add-on: Unintended navigation when using Valve Index #93509
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#93509
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Apparently the (grip?) sensors on the Index controllers trigger navigation even when the user is not meaning to activate them (i.e. the hand is in a relaxed position).
This may be because the input threshold for the sensors is too low and/or a different input binding should be used for the navigation action (i.e.
/input/squeeze/force
instead of/input/squeeze/value
).The issue should be resolvable by simply modifying the bindings in the VR Scene Inspection add-on. The following two patches offer potential solutions to be tested: P2626, P2627.
Added subscribers: @muxed-reality, @dr.sybren
Patches P2626 and P2627 have the same content, so I'll just test P2626.
Master branch @
5cad004d71
+ patch is a huge improvement over what I saw with 3.0 alpha/beta (don't know which version I tried exactly, sorry). It's much more usable this way. I still don't like the "grab the controllers to grab the world" approach, though. It's really nice when you're actually using it, but when you don't use that style of navigation, it requires you to open your hands and let go of the controllers all the time. For a moment I couldn't find out why the sticks didn't work, only to realise they were fighting the "squeeze" controls.As a final usability remark, it would be super nice if somehow the "Auto Depth" functionality of mouse navigation was to be incorporated into the VR controllers. It would be super nice to have the joysticks speed up & slow down depending on how close you are to your model. Just a thought though -- the above "hands must always be open" issue is way more important to me.
UPDATE: I changed
/input/squeeze/value
to/input/squeeze/force
and that made all the difference. It makes it possible to hold the controllers normally and still use the other controls, solving the issue I described above. Lowering the threshold from0.8
to0.5
makes it even nicer, as you can then use a more subtle squeeze.@dr.sybren Thanks for testing!
Great that
/input/squeeze/force
with a threshold of0.5
works (actually P2627 did this, but with a threshold of0.8
).I'll commit a fix and add it to the 3.0.1 candidates (#93479).
Regarding the "Auto Depth" functionality, that would be a nice option and can be added in the future.
This issue was referenced by blender/blender-addons@183f92c7d5
This issue was referenced by blender/blender-addons@c60fef3817
Changed status from 'Needs Triage' to: 'Resolved'
Ah yes, I overlooked that difference -- we need diff diffing :P
Thanks for the fix!