VOS scans your PC, diagnoses every VR bottleneck in plain English, and applies a small set of reversible, app-scoped fixes with one click. Like having a VR-tuning expert sit at your PC, tell you exactly why you're getting lag in VRChat, and fix the parts that are genuinely safe to fix while you watch.
Latest release · Windows 10 / 11A diagnostic scanner, a fixer, a session recorder, and a driver-aware advisor — all running locally, with the source on GitHub.
"Tell me why my VR is choppy." VOS probes CPU, GPU, RAM, storage, Wi-Fi, drivers, services, running processes, event log errors, and headset state, then explains every finding in plain English.
Preview every change before it runs. Per-fix undo records exactly what each value was before applying, so reverting puts it back the way it was. v0.2.9 narrowed this to a small set of app-scoped, reversible changes — no HKLM writes, no service stops.
Off by default; opt-in via a pre-enable disclosure modal. Auto-detects when a VR runtime starts and lowers the priority of background processes via os.setPriority. Hardcoded never-touch list (System processes, anti-cheat, headset runtimes, System32). Restores state on exit; survives a crash via the recovery state file.
Every VR session is recorded at 1 Hz with CPU, GPU, RAM, temps, and power. Timeline view lets you scrub back to "what was happening when I started getting frame drops?"
VOS keeps a curated list of which NVIDIA / AMD GPU drivers ship with VR-relevant regressions. If you're running a known-bad version, it tells you and links to a known-good one.
Includes the X3D V-Cache CCD pinning trick on supported AMD CPUs — a real measurable win in crowded VRChat instances. Plus per-game profiles for MSFS, DCS, Beat Saber, Bonelab, and more.
VOS knows your specific CPU model, GPU, and headset. Recommendations are tailored: a 5800X3D + Quest 3 user gets different advice than a 14700K + Index user.
Transparent 320×120 always-on-top window shows CPU, RAM, GPU temp, and GPU power with color-coded thresholds. Stays visible during fullscreen VR.
MIT-licensed. Every line of code is on GitHub. The app doesn't phone home, send analytics, or load anything off a server at runtime. If you'd rather not trust the binary, build from source.
Install, scan, fix. In under five minutes.
6-question first-run wizard asks your headset, connection method, and main complaint. Every answer biases the recommendations.
Full system probe runs locally. CPU, GPU, RAM, Wi-Fi, drivers, services, processes, event logs, headset state — all collected in under a minute.
Review prioritized action plan, preview each change, hit one button. Fixes apply in sequence with live progress and per-fix undo.
v0.2.9 cut the auto-fix surface down to the changes that are genuinely safe to apply automatically. Every fix is preview-before-apply, every fix has a one-click undo, and the diagnostic side still surfaces everything we no longer auto-apply — you just make those changes yourself if you want them.
/affinity maskPer-headset recommendations, per-game tuning tips, and a hardware knowledge base covering 80+ CPUs and 200+ GPUs.
Probably, the first time. Here's why, and how to verify the binary if you'd rather not take my word for it.
VOS is unsigned. I'm one person, not a company with a code-signing budget. The first time you run the installer Windows SmartScreen will show an "Unknown publisher" warning. Click More info, then Run anyway.
A small minority of heuristic AV engines may also flag the installer because system-tuning tools and credential-stealing malware do many of the same low-level things: enumerate processes, query hardware, make HTTPS requests. The full transparency page walks through every read, every write, and every network call VOS makes, and why.
Want to verify before you run it? Every release posts a SHA-256 in its notes. Drop the installer on VirusTotal and check it yourself. Detection ratio is typically 0 or 1 out of 67 vendors. Or skip the binary entirely and build from source.
VOS is free, MIT-licensed, and built by one person. Patreon is the easiest way to keep that going. It funds dev time, hardware testing, and hosting, which means more fixes shipping for everyone.
If VOS saves your VR sessions from stutter, the most direct way to say thanks is Patreon. It pays for the time it takes to research new fixes, expand the GPU driver and headset databases, and keep the project running. The license is MIT and won't change. There's no paid tier on the app itself.
No subscription required to use VOS. All features are permanently free and the source is on GitHub. Bug reports go to Issues.
Short answers to the questions people ask before downloading.
Yes — MIT-licensed, full source on GitHub. You can audit every line, fork it, redistribute it, and modify it. If you don't trust our binaries, you can build it yourself from source.
Possibly. The installer is unsigned (we don't have a code-signing certificate) so Windows SmartScreen will warn you the first time. A small minority of heuristic AV engines also occasionally flag system-tuning tools as generic info-stealers because the low-level APIs overlap. TRANSPARENCY.md documents every syscall the app makes. Every release publishes a SHA-256 you can check on VirusTotal.
Scans run entirely on your PC. No analytics, no telemetry, no remote-loaded code. Bug reports are opt-in and you choose which attachments to include. Forum-shareable scan exports redact Wi-Fi SSID/BSSID, user paths, MAC addresses, and emails. Full inventory in PRIVACY.md.
Every fix is reversible. v0.2.9 narrowed the auto-fix surface to a small set of app-scoped changes (game configs, Steam launch options, live process priorities) — no HKLM writes from the fix engine, no service stops. You preview every change before applying, and per-fix undo records exactly what each value was before, so reverting puts it back the way it was. Earlier versions also created a Windows System Restore Point automatically; v0.2.9 dropped that alongside the PowerShell removal (the only Win32 path to SRClient was via Checkpoint-Computer). If you want belt-and-braces, take a Restore Point yourself before installing.
Probably. The setup wizard tailors recommendations to your headset, connection method, and primary use case. The diagnostic engine knows about 15 VR titles (VRChat, MSFS, DCS, Beat Saber, Bonelab, iRacing, and more) and 18+ headset profiles with per-model known issues.
Yes. VOS detects all four wireless PC-VR streaming methods plus wired Link and DisplayPort, and tunes accordingly. Wireless-specific fixes (Nagle, QoS, Wi-Fi band, encoder bitrate sanity) only appear when they're relevant to your setup.
No. As of v0.2.9 the installer and the app run as the standard user — admin elevation isn't required to install or to use VOS. The fixes that did need admin in earlier versions (HKLM writes, service stops) were either removed entirely or demoted to detection-only.
The in-app updater polls GitHub Releases periodically. Installers are SHA-512 verified before applying. A pill appears in the titlebar when an update is available, and you can also check manually in Settings or just download the latest from GitHub.
Latest installer ships from GitHub Releases. Each release publishes a SHA-512 (the hash electron-builder writes into latest.yml) and a SHA-256 for VirusTotal-style lookups.
VOS is a solo project. One person designs the diagnostic rules, picks which fixes are worth shipping, tests them on real VR hardware, reviews every line that goes into a release, and is on the hook when something breaks. That person is me.
I use Claude (an AI model from Anthropic) to help write code and most of the prose, including parts of this site. The VR-domain knowledge, the rule design, the choice of which fixes are worth shipping, and the responsibility for bugs are all mine. The model just helps me articulate it faster than I could alone.
If that bothers you, fair. The whole project is open-source under the MIT license, so you can audit every line, build from source, fork it, or skip it. If it doesn't bother you, the door's open the same way.
Transparency page · Source on GitHub · MIT license · Trademark notes · File an issue