From dd5a19ac80a71e7bb6a15dece055ed96f4f68e9c Mon Sep 17 00:00:00 2001 From: bredo Date: Fri, 22 Aug 2025 08:19:05 +1200 Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s) Co-authored-by: hypevhs <4498312-hypevhs@users.noreply.gitlab.com> --- content/docs/resonite/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/docs/resonite/_index.md b/content/docs/resonite/_index.md index c97d996..0443f42 100644 --- a/content/docs/resonite/_index.md +++ b/content/docs/resonite/_index.md @@ -20,7 +20,7 @@ To solve this, prepend `OXR_PARALLEL_VIEWS=1` to Resonite's launch options. In August 2025, Resonite updated to run FrooxEngine as a native Linux process, with the renderer being run through Proton. -In larger sessions Resonite is typically CPU-bound, there isn't much that can be done besides upgrading your CPU. In situations where the GPU is a bottleneck, lowering the resolution (either in the OpenXR runtime or through OpenComposite) may help dramatically. +Resonite is typically GPU-bottlenecked. Lowering the resolution may help. This can be easily done by prepending `OXR_VIEWPORT_SCALE_PERCENTAGE=75` to Resonite's launch options. Experiment with different values to find your preferred balance between performance and quality. ## Visemes