21
edits
Changes
Jump to navigation
Jump to search
no edit summary
== Sway ==
On Sway, this is controlled by the <code>max_render_time</code> setting. The <code>max_render_time</code> setting on the output controls how many millisecond the compositor renders before the vblank. Setting <code>max_render_time</code> on the window controls how many milliseconds the compositor tells windows to render. Both must be set for optimal latency.
=== Screen latency tuning ===
We start by running <code>swaymsg output DP-1 max_render_time 1</code>. If there is frame dropping, increase the value of <code>max_render_time</code> by 1 and try again until frame dropping stops. This is the optimal setting for <code>max_render_time</code>. Once you find this value, open up your sway config file (usually <code>~/.config/sway/config</code>), and add the line <code>output DP-1 max_render_time t</code>, with <code>t</code> replaced by the optimal value obtained previously.
=== Looking Glass latency tuning (B5-only) ===
Tuning the latency for Looking Glass follows a very similar process:
1. Close the Looking Glass client.
2. Run <code>swaymsg 'for_window [app_id="looking-glass-client"] max_render_time 1'</code>.
3. Run the Looking Glass client with the <code>win:showFPS win:jitRender</code> option. If you have multiple monitors, you want to move to window to the monitor with the highest resolution.
4. If the FPS value displayed is lower than the screen refresh rate, close the client and restart from step 2, but increment the value of <code>max_render_time</code> by 1.
5. Once this is done, open up your sway config file (usually <code>~/.config/sway/config</code>), and add the line <code>for_window [app_id="looking-glass-client"] max_render_time t</code>, with <code>t</code> replaced by the optimal value obtained previously.
