From 29425dad76b18af01fca446684d7af9a5a060cf4 Mon Sep 17 00:00:00 2001
From: galister <3123227-galister@users.noreply.gitlab.com>
Date: Fri, 16 Feb 2024 13:34:13 +0000
Subject: [PATCH] alvr blackout after steamvr update

---
 content/docs/steamvr/quick-start.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/steamvr/quick-start.md b/content/docs/steamvr/quick-start.md
index 6be881e..5883639 100644
--- a/content/docs/steamvr/quick-start.md
+++ b/content/docs/steamvr/quick-start.md
@@ -77,6 +77,6 @@ None: Cloud sync can get stuck and prevent SteamVR from launching. I recommend d
 
 If you've installed Steam in a non-standard location, change the variable on the top of the script.
 
-To use the script, simply launch it from a terminal. It will ask for sudo password in case your SteamVR has been freshly installed or updated and it needs to `setcap` the compositor.
+To use the script, simply launch it from a terminal. It will ask for sudo password in case your SteamVR has been freshly installed or updated and it needs to `setcap` the compositor. ALVR-only: If you get a SteamVR error after this, open ALVR dashboard and launch SteamVR from there once.
 
 If you need to restart SteamVR, simply exit it using your overlay and it'll be restarted for you. To really exit SteamVR, first Ctrl-C the script.