Support
Get help with vrOS.
Four ways out of a problem. Pick the one that matches what you need — and if none of them fits, ask on Discord and someone will point you at the right one.
Something is broken
File a bug you can reproduce: what you did, what you expected, and what happened instead. The report becomes an issue you can follow.
Report a bugCheckYou want to know if it is already known
Every report lands in the same tracker. Search it before you file — if your bug is already there, adding what you know is worth more than a second issue.
Browse issuesAskYou want to ask a person
Discord is the fastest way to reach a human. Install trouble, a setting you cannot find, or a question that is not quite a bug yet.
Open DiscordLearnYou want to know how something works
The guide covers install, first run, the Dash, and the extensions that ship with vrOS. Troubleshooting and the release notes live there too.
Read the docsvrOS has no telemetry and sends no crash reports, so a bug nobody reports is a bug nobody is fixing.
Bug reports are public.
Filing a bug opens an issue on the tracker, and every issue on it is mirrored on this site for anyone to read. Everything you write goes with it — the title, the description, the steps. Leave out account names, keys, and anything else you would not post in a public thread.
If the problem involves something you cannot share publicly, ask onDiscord first.
Where vrOS runs
| Platform | Status |
|---|---|
| Windows 10 / 11 | Supported |
| Linux x86-64 — desktop and SteamOS | In development |
| Steam Frame — SteamOS, ARM64 | In development |
A Steam Frame streaming from a Windows PC runs the PC build, and that is supported. Running vrOS natively on the Frame itself is the part still in development.