Jasima/lvra.gitlab.io
1
0
Fork 0
mirror of https://gitlab.com/lvra/lvra.gitlab.io.git synced 2025-05-03 20:54:24 +02:00
Code Issues Projects Releases Packages Wiki Activity

fix: trailing spaces and markdown good practices

Browse source
This commit is contained in:
Gabriele Musco 2024-04-16 07:34:07 +02:00
parent 13360a21f0
commit ccad3211cd
No known key found for this signature in database
GPG key ID: 1068D795C80E51DE
7 changed files with 24 additions and 14 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/docs/steamvr/quick-start.md
View file

@ -14,7 +14,7 @@ title: Quick Start
- AMD+AMD laptop or desktop: Amazing choice, you have nothing to do.
- Desktop with iGPU and dGPU of different brands: Disable your iGPU in BIOS.
- Laptop with Nvidia dGPU:
- Laptop with Nvidia dGPU:
- **Option 1 (Ubuntu-only)**: Try the official Ubuntu solution `prime-select nvidia`.
- **Option 2**: Use `optimus-manager-qt` and switch to Nvidia.
- **Option 3**: Launch steam, steamvr and all games with `prime-run` (Launch options: `prime-run %command%`)
@ -66,6 +66,7 @@ The `startvr` script [here](https://gist.github.com/galister/a85135f4a3aca5208ba
It can be used with both ALVR and wired headsets.
What it does:
- Whitelist drivers for SpaceCal and ALVR so these will never get blocked
- Apply bindings spam patch by Plyshka
- Setcap the compositor after a SteamVR update
@ -73,6 +74,7 @@ What it does:
- Prevent SteamVR processes from getting stuck and putting SteamVR in an inconsistent state
Extra steps when using with ALVR:
- Under `Installation` tab, register the ALVR driver
- Under `Settings`, `Steamvr Launcher` section, set `Driver launch action` to `No action`.
@ -80,7 +82,7 @@ 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, Ctrl-C the script, open ALVR dashboard and launch SteamVR from there once. You then don't have to open ALVR until there's a SteamVR update.