1. SteamVR
  2. News

SteamVR News

SteamVR Beta Updated - 2.0.4

If you encounter issues with this update, please post in the SteamVR Bug Report forum. If possible, please include a 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.

In order to get all of these changes, make sure you're opted into both the Steam Client Beta and SteamVR Beta.

Desktop View:
  • Restored ability to add an individual desktop window, using a button directly on the dashboard.
  • Desktop windows now show their actual icon in addition to their name.
General:
  • Fixed cases where binding callouts would stay up even when they should be dismissed.
Index Controller Firmware
  • Fixed a bug where haptics could stop responding after playing certain repeated haptics events.


SteamVR Beta Updated - 2.0.3

If you encounter issues with this update, please post in the SteamVR Bug Report forum. If possible, please include a 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.

SteamVR:
  • Show Multitasking View button on Desktop windows.
  • Fixed scaling issues with floating dashboard overlays.
  • Fix for SetSkyboxOverride always showing only the last texture.
  • Speed up initial load of all web views (settings, etc.)
  • Fix issues caused by running vrstartup from a different SteamVR install when SteamVR is already running.
  • Further laser pointer double-click refinements.
  • Laser pointer no longer jumps when you switch input devices.
  • Laser pointer is more consistent when dragging outside of overlays.
  • Typing emojis works in Desktop view.
  • Move Dashboard slightly further away.


Linux:
  • Fix new VR gamepad UI rendering with a flipped Y-axis.
  • Fix runtime configuration to launch in Steam Linux Runtime 3.0 (sniper), addressing startup issues on some systems.
  • Fix vrcompositor to launch under legacy scout runtime, addressing startup issues on some systems.
  • Fix SteamVR Home to launch under legacy scout runtime.

VR Changes in Steam Client Beta - October 3rd

Today's Steam Client Beta includes the following VR-specific changes. In order to get all of these changes, make sure you're opted into both the Steam Client Beta and SteamVR Beta.

If you encounter issues with this update, please post in the SteamVR Bug Report forum. If possible, please include a 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.

General:
  • Support for multi-gpu system (e.g. laptops) which was causing the new Steam UI to not show up.
Steam Dashboard overlay:
  • Filtered out vr overlay apps from recent games list.
  • Fixed auto switching to game details page on launch.
  • Never auto switch to app details page on launch for vr overlay apps.
Dashboard:
  • Restored the dashboard button to exit VR. It's now safe to take off your headset.

SteamVR Beta Updated - 2.0.2

If you encounter issues with this update, please post in the SteamVR Bug Report forum. If possible, please include a 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.

SteamVR:
  • Improved double click reliability in desktop view.
  • Added a button to toggle multitasking view for desktop overlays (Windows 10 and 11 only).


Meta:
  • Meta controller dashboard default bindings: B and Y navigate 'Back' through Steam UI, and right clicking in desktop view has been moved to thumbstick click.

SteamVR Beta Updated - 2.0.1

Greetings! Today we are shipping SteamVR 2.0 in beta. We see this is as the first major step toward our goal of bringing all of what's new on the Steam platform into VR. In order to use all the features in this beta, you must also opt into the Steam Client Beta (see instructions below).



Users who opt into this beta will notice a new UI with lots of added features:
  • Most of the current features of Steam and Steam Deck are now part of SteamVR
  • Updated keyboard with support for new languages, emojis, and themes
  • Integration of Steam Chat and Voice Chat
  • Improved Store that puts new and popular VR releases front and center




This is just the beginning of SteamVR 2.0’s journey, and we’ll have more to share in the coming weeks and months as we collect feedback and work on the features mentioned above. This beta will give us a chance to work out the kinks as more and more people try it out. As with all betas, this means SteamVR 2.0 will get better and better as we prepare it for its eventual full public launch.

To opt into the SteamVR Beta, follow the instructions in this article.

To opt into the Steam Client Beta, follow the instructions in this article.

If you encounter issues with this update, please post in the SteamVR Bug Report forum. If possible, please include a 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.

In addition to the new dashboard interface, this beta brings the following changes:

SteamVR:
  • Floating overlay windows can now be interacted with while the dashboard is hidden.
  • Fixed crash on exit for some Unity titles.
  • Increased the system layer resolution limit. This was previously 1.5x the recommended render target scale, but is now applied to width and height independently.
  • Fix a case where controller configuration would not be localized in the user’s preferred language (as configured in Steam).
  • Added a prompt to install the Bigscreen Beyond Driver when the headset is detected.
Meta:
  • Hide the SteamVR IPD slider since Meta already shows one.
Linux:
  • Transition to the Steam Linux Runtime 3.0 (sniper) for improved compatibility.
Drivers:
  • For drivers which provide a manifest but don’t specify “resourceOnly”, default to true if there is no bin directory.
  • Add a manifest entry "showEnableInSettings" which can be set to force a driver to appear in the “addons” settings even if default rules would hide it.
  • When a specific driver is forced with the "forcedDriver" setting or the VR_FORCE_TEST_DRIVER, load it even if it is disabled.
  • When a specific driver is forced with the "forcedDriver" setting or the VR_FORCE_TEST_DRIVER, only allow an HMD to activate from that driver (even if other drivers are loaded due to “activateMultipleDrivers” and they activate an HMD first). The forced driver always had the first opportunity to activate an HMD before, but now we will wait for it to hotplug an HMD rather than letting another available HMD win.
  • The “LastKnown” section in settings (which updates with the manufacturer and model of the last used HMD) now also keeps track of the “ActualHMDDriver” (e.g. “lighthouse”) that provided the HMD.