| Age | Commit message (Collapse) | Author |
|---|
|
|
|
Part of T80730
|
|
|
|
This is no longer necessary, see: T98554.
|
|
|
|
Also refactor the "blender_default_tracker" action map to have separate
pose actions for each tracker role (instead of a single pose action with
subaction paths for each role) and add controller pose actions.
|
|
See D14220.
|
|
|
|
Creates a new camera and "Custom Object"-type landmark from the VR
headset pose.
In contrast to the existing "Landmark from Session" operator that only
saves the headset rotation around the global z-axis, this preserves the
exact rotation of the headset by assigning it to the newly-created
camera (although the landmark itself still only inherits the z-rotation
component).
|
|
|
|
|
|
|
|
|
|
Intended for use with motion capture objects. Currently only supported
by the SteamVR runtime (1.21) and requires the "HTC Vive Tracker"
extension to be enabled via the "Extensions" panel.
|
|
From xr-controller-support branch.
|
|
https://developer.blender.org/D13102
|
|
https://developer.blender.org/D13421
|
|
Although the HTC Vive Focus 3 controller extension is currently not
supported by any OpenXR runtimes (save for the dedicated Focus 3
runtime in developer early-access), the bindings are still useful to
have for the future.
|
|
XR actions API was changed in rB6a8709ba136e.
|
|
Some files needed to be changed manually.
|
|
See T95597
|
|
The input bindings for "grab" navigation on the Valve Index controllers
could previously trigger the action even when the user did not intend
to do so (i.e. their hand was not actively gripping the sensor). This
was resolved by changing the bindings from "/input/squeeze/value" to
"/input/squeeze/force" and increasing the input threshold from 0.3 to
0.5.
Thanks to sybren for testing.
|
|
|
|
|
|
This updates the VR Scene Inspection add-on with functionality for
loading and using default controller actions, including controller
poses and haptics, and visualizing VR controllers both in-headset and
in the regular 3D viewport.
In other words, users can finally view their VR controllers and use
them to navigate their scene in VR.
Controller actions (enabled by default) are available as an option in
the "VR Session" panel. For controller bindings that require OpenXR
extensions (Reverb G2, Vive Cosmos, Huawei), there is a new
"Action Maps" panel where users can toggle these bindings. Bindings
that require extensions are disabled by default since not all OpenXR
runtimes may support them, which will lead to an error during action
creation at session start.
There is also an option in the "Action Maps" panel to use a
gamepad (Xbox Controller) instead of motion controllers for VR
actions/viewport navigation.
In addition to default actions, this update adds new options for VR
controller visualization. For in-headset (VR) visualization, controller
visibility as well as style (dark/light, ray/no ray) can be set via the
"View" panel. For visualization in the regular 3D viewport, there is a
new option in the "Viewport Feedback" panel to draw controllers as
gizmos, similar to the existing option for the VR camera (headset).
Finally, this update also changes the VR Landmark "Custom Camera" type
to "Custom Object", so users can specify any object (not just cameras)
as a base pose reference, and adds a base scale option for custom
object and custom pose-type landmarks.
Reviewed By: Severin
Differential Revision: https://developer.blender.org/D11271
|
