LinuxVR_Adventure/lvra.gitlab.io
1
0
Fork 0
Code Issues 3 Pull Requests 10 Actions Packages Projects Releases Wiki Activity

Edit _index.md

Browse Source
This commit is contained in:
WMan Twentytwo
2025-08-03 18:15:04 +00:00
committed by hypevhs
parent 0c33833f3f
commit e8993b5ece
1 changed files with 12 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
content/docs/fossvr/monado/_index.md
View File

@@ -45,6 +45,7 @@ You can add "OXR_PARALLEL_VIEWS=1 %command%" to the launch options to fix this.
# Troubleshooting # Troubleshooting
## [NVIDIA-specific] "NVIDIA: No allowlisted displays found!" ## [NVIDIA-specific] "NVIDIA: No allowlisted displays found!"
This may be caused by a few different issues: This may be caused by a few different issues:
@@ -52,5 +53,15 @@ This may be caused by a few different issues:
This can be worked around by setting the environment variable `XRT_COMPOSITOR_FORCE_NVIDIA_DISPLAY="NVIDIA"`. This can be worked around by setting the environment variable `XRT_COMPOSITOR_FORCE_NVIDIA_DISPLAY="NVIDIA"`.
- HMD display completely missing from the list: Try unplugging and replugging the power adapter. - HMD display completely missing from the list: Try unplugging and replugging the power adapter.
## [NVIDIA-Specific] "I'm getting screen tearing inside of my VR headset!"
This is caused by having a monitor with VRR enabled. Turning it off in KDE Plasma's display settings may not fix it.
- Step 1: Open your terminal and type `sudo nano /etc/default/grub`
- Step 2: Add `nvidia-modeset.conceal_vrr_caps=1` inside the parameters of `GRUB_CMDLINE_LINUX_DEFAULT=`
- Step 3: Close nano after saving the changes to the text file and update your grub config by typing `sudo grub-mkconfig -o /boot/grub/grub.cfg`
- Step 4: Restart your PC.
## "vkAcquireXlibDisplayEXT: VK_ERROR_UNKNOWN (0x000058b7a0764a80)" ## "vkAcquireXlibDisplayEXT: VK_ERROR_UNKNOWN (0x000058b7a0764a80)"
Try unplugging and replugging the power adapter. If the issue still occurs and you are on a Wayland session, try setting the environment variable `XRT_COMPOSITOR_FORCE_WAYLAND_DIRECT=1`. Try unplugging and replugging the power adapter. If the issue still occurs and you are on a Wayland session, try setting the environment variable `XRT_COMPOSITOR_FORCE_WAYLAND_DIRECT=1`.