Jayden/wayvr
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: troubleshooting details

Browse Source
This commit is contained in:
galister
2024-10-25 08:39:25 +00:00
committed by GitHub
parent 0b1a7e8bc8
commit 7cb8e4a9d2
1 changed files with 18 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@@ -115,6 +115,10 @@ We would like to work with you and include additional bindings.
## Troubleshooting ## Troubleshooting
When an error is detected, we often print tips for fixing into the log file.
Logs will be at `/tmp/wlx.log` for most distros.
Check [here](https://github.com/galister/wlx-overlay-s/wiki/Troubleshooting) for tips. Check [here](https://github.com/galister/wlx-overlay-s/wiki/Troubleshooting) for tips.
## Known Issues ## Known Issues
@@ -125,8 +129,22 @@ Hyprland users: Hyprland v0.41.0 changed their absolute input implementation to
Niri users: use on Niri 0.1.7 or later. Niri users: use on Niri 0.1.7 or later.
X11 users might be dealing with a [Phantom Monitor](https://wiki.archlinux.org/title/Xrandr#Disabling_phantom_monitor).
Other desktops: The screens may have been selected in the wrong order, see [First Start](#first-start). Other desktops: The screens may have been selected in the wrong order, see [First Start](#first-start).
### Crashes, blank screens
There are some driver-desktop combinations that don't play nice with DMA-buf capture.
Disabling DMA-buf capture is a good first step to try when encountering an app crash or gpu driver reset.
```bash
echo 'capture_method: pw_fallback' > ~/.config/wlxoverlay/conf.d/pw_fallback.yaml
```
Without DMA-buf capture, capturing screens takes CPU power, so let's try and not show too many screens at the same time.
### Space-drag crashes SteamVR ### Space-drag crashes SteamVR
This has been idenfitied as an issue with SteamVR versions 2.5.5 and above (latest tested 2.7.2). One way to avoid the crash is by switching to the `temp-v1.27.5` branch of SteamVR (via beta selection) and selecting [Steam-Play-None](https://github.com/Scrumplex/Steam-Play-None) under the compatibility tab. This has been idenfitied as an issue with SteamVR versions 2.5.5 and above (latest tested 2.7.2). One way to avoid the crash is by switching to the `temp-v1.27.5` branch of SteamVR (via beta selection) and selecting [Steam-Play-None](https://github.com/Scrumplex/Steam-Play-None) under the compatibility tab.