Release notes
Every vrOS release gets notes. They are written once and published in two places: as an announcement on the Steam page, and here, newest version first. The Steam announcement goes out in all nine app languages; this page is English.
Each entry is one version, headed by its version number and the date it went out, newest at the top. Within a version the changes are grouped, and only the groups that have something in them appear:
- New features — things that were not there before.
- Fixes — things that were broken.
- Improvements — things that got faster, quieter, or less annoying.
- Known issues — what is known to be still wrong at the time of the release. This group exists so that it gets used.
Bullets are written for the person wearing the headset, not for the person reading the commit log. Where a change lands on a setting, the note names the setting’s path so you can go and look at it.
Version numbers are semantic: the patch digit moves for fixes, the minor digit for new features that break nothing, and the major digit for changes that do. Pre-release builds carry a suffix — 2.0.0-beta.1 and so on — until the version they lead to ships.
Not yet released. The notes for the first stable version land here on release day.
Until then, What vrOS is describes what 2.0.0 contains, and the FAQ is honest about what it does not: 2.0.0 ships the foundation — overlays, the VR keyboard, input authority, performance, playspace, audio — and creator features return incrementally as extensions.
Older versions
Section titled “Older versions”vrOS 1 was a different application with a different architecture, and its release history is not carried over here. This page starts at 2.0.0.
If something changed in a way you did not expect, Troubleshooting is usually faster than a changelog, and Discord is faster than both.