Weirdly, the introduction of "predictive bypass" in Mir 0.15 seems to have provided a workaround. To get the bug back, just disable predictive bypass: --composite-delay=0
Weirdly, the introduction of "predictive bypass" in Mir 0.15 seems to have provided a workaround. To get the bug back, just disable predictive bypass: --composite-delay=0