SteamVR 2.0 Beta: Vorschau bringt (Sprach-)Chat und nähert sich Steam (Deck)
Valve hat eine erste Beta von SteamVR 2.0 veröffentlicht. Zu den größten Neuerungen gehören die Annäherung an aktuelle Steam- und Steam-Deck-Funktionen, die Integration von Steam (Voice) Chat sowie neue Tastatursprachen.
Zudem soll der neue Store neuen und beliebten VR-Veröffentlichungen eine größere Bühne bieten. Noch sind einige Details offen, z.B. welche Features von Steam oder Steam Deck konkret integriert worden sind. Grundsätzlich kündigt Valve an, dass in den kommenden Wochen und Monaten weitere Neuigkeiten für das Tool für Virtual Reality geteilt werden, sobald Rückmeldungen zu den jetzt eingeführten Funktionen vorliegen.
Um an der Beta von SteamVR 2.0 teilzunehmen, ist eine explizite Einwilligung erforderlich. Zudem ist die Teilnahme an der Beta für den Steam Client Voraussetzung.
Weitere Änderungen lassen sich dem Changelog entnehmen
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.
Changelog SteamVR 2.0 Beta