This release includes a variety of bug fixes and quality of life improvements for SteamVR.
We continue to focus on OpenXR as our preferred API for new games and applications. SteamVR’s official OpenXR subforum is
here and we’d love to hear your feedback, as well as suggestions for new features.
SteamVR:
- Bindings can now have "Controller Offsets" (found in Options) that will apply to controller orientation across all input types (Legacy, SteamVR Input, OpenXR). This is in addition to individual "Pose Offsets" which will apply only to the specific pose you've selected. To add offsets to poses in the Controller Binding UI, click the gear icon next to a pose.
- Slight reduction in dashboard startup time.
- Fixed an issue with the Binding UI not being able to save bindings.
- Minor SteamVR Input speed optimizations.
- Made the Controller Binding UI smaller to improve usability in headset.
- Added Pico Controller to the list of controller types you can simulate.
- Fixed a bug with bindings that caused returnBindingsWith* options to be ignored.
- Fix controller SVGs not rendering in the controller test UI.
- Fixed some scenarios where the keyboard didn't work in the Binding UI.
- Fixed an issue with modified bindings not working while Steam was offline.
- Fixed always showing the "multitasking mode" button for all overlays, not just Desktop overlays.
- Fixed sometimes showing the "show keyboard" button for overlays that don't support keyboard input.
- Fixed initially showing double overlay control bars the moment you float a window in the world.
- Fixed the overlay control bar not being visible at all in the Legacy dashboard.
Steam Link:
- Slight reduction in startup time for Steam Link VR.
- Reduced CPU utilization when streaming with Steam Link.
- Fixed some minor performances hitches.
- Resolved multiple crashes.
OpenXR:
- XR_EXT_dpad_binding now correctly works on all appropriate controller types.
- Fixed a bug where certain poses would not show up in the Binding UI when simulating controllers.
Developers:
- When a user is using Steam Link, app developers can now retrieve the correct HMD type via Prop_ModelNumber_String, rather than it being misreported as a Quest 2.
OpenXR Developers:
- Add support for XR_EXT_render_model and XR_EXT_interaction_render_model.
- Return more realistic joint radii in xrLocateHandJointsEXT.
- Fix render model UUIDs not generating correctly on Linux.
- Fixed a bug where the valid and tracked flags were set on hand joints when the joint data were actually invalid.
- Fixed a bug where hand tracking could return a XR_RUNTIME_FAILURE when it should have only been invalid poses.
- Fixed wrist joint alignment not matching OpenXR spec requirements. Corrected palm joint placement.
- Removed palm_ext/pose from vive_trackers to match specification.
- Runtime now returns XR_ERROR_GRAPHICS_REQUIREMENT_CALL_MISSING instead of XR_VALIDATION_FAILURE if an app tries to create a session without first calling xr*GetGraphicsRequirement.
- Added support for XR_SWAPCHAIN_USAGE_UNORDERED_ACCESS_BIT to the D3D11 path, which was previously ignored.
- Minor input speed optimizations.
- Fix SteamVR not returning XR_ERROR_EXTENSION_NOT_PRESENT when an OpenXR layer requests an unavailable extension.
- Fix xrCreateActionSpace returning XR_ERROR_PATH_UNSUPPORTED when using Vive trackers
As always, if you are interested, we encourage enrolling into SteamVR Beta by right-clicking on SteamVR in your Steam library, clicking on "Properties" and selecting "Betas" from the list on the left hand side and then clicking "Beta" under Beta Participation. Additionally, if you use Steam Link for Meta Quest, you can opt into the beta
here or in-headset by going to your library, clicking the "..." on Steam Link, selecting Settings and clicking the button to the right of "Installed Version Information."
[h3]
Help & Information:[/h3]
The Steam Link for Meta Quest FAQ page is available
here.If you encounter issues with this update, please post in the
SteamVR Bug Report forum. If possible, please include a SteamVR System Report to aid in tracking down your issue.
Replies to this post are not tracked for bug reporting purposes. Please use the forum linked above to report issues.