aboutsummaryrefslogtreecommitdiff
path: root/wiki
diff options
context:
space:
mode:
authorIvan Molodetskikh <yalterz@gmail.com>2025-07-16 11:57:37 +0300
committerIvan Molodetskikh <yalterz@gmail.com>2025-07-16 11:57:55 +0300
commit7b065f8618f63b7cf761ebe05a2cebd556113a6c (patch)
treec2a5535f8b456d58d4ca4cc23ee2af08a263ef2c /wiki
parent60fbcd23299364667865856155978c8c6b888667 (diff)
downloadniri-7b065f8618f63b7cf761ebe05a2cebd556113a6c.tar.gz
niri-7b065f8618f63b7cf761ebe05a2cebd556113a6c.tar.bz2
niri-7b065f8618f63b7cf761ebe05a2cebd556113a6c.zip
wiki/Nvidia: Mention screencast flickering fix
Diffstat (limited to 'wiki')
-rw-r--r--wiki/Nvidia.md12
1 files changed, 12 insertions, 0 deletions
diff --git a/wiki/Nvidia.md b/wiki/Nvidia.md
index 86c16319..13b551d8 100644
--- a/wiki/Nvidia.md
+++ b/wiki/Nvidia.md
@@ -39,3 +39,15 @@ Restart niri after writing the config file to apply the change.
The upstream issue that this solution was pulled from is [here](https://github.com/NVIDIA/egl-wayland/issues/126#issuecomment-2379945259). There is a (slim) chance that NVIDIA updates their built-in application profiles to apply this to niri automatically; it is unlikely that the underlying heuristic will see a proper fix.
The fix shipped in the driver at the time of writing uses a value of 0, while the initial config posted by an Nvidia engineer approximately a year prior used a value of 1.
+
+### Screencast flickering fix
+
+If you have screencast glitches or flickering on NVIDIA, set this in the niri config:
+
+```kdl
+debug {
+ wait-for-frame-completion-in-pipewire
+}
+```
+
+This will become unnecessary once niri supports explicit sync for PipeWire screencasts: https://github.com/YaLTeR/niri/issues/1432