cragsand, 
New SteamVR update!
https://steamcommunity.com/games/250820/announcements/detail/3666547477701338588Before opting in to the beta, you may want to wait for playspace moving utilities like "OVR Advanced Settings" to update.
https://store.steampowered.com/app/1009850/OVR_Advanced_Settings/
- If you tried it, does playspace moving still work for you?
- Did you encounter any unexpected issues?
- Are VTubing applications still working or did they break for you?
#steamvr #steam #vr #vrchat #virtualreality #playspace #pc #pcgaming
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.
Add comment